Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Several of my SMVI backup jobs are listed as "running". They've been like this for a while now. I've deleted the "crashdb" folder as specfied elsewhere, restarted both the virtual centre and the server with SMVI on and they are still there. SMVI seems to have managed to delete it's backups as they were after the retention period however i can't take any more. It seems absolutely crazy that there's no way to just cancel a "running" (but not relaly running) job!
Can somoene out there help me please?
Thanks
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sigh, never mind. As the jobs weren't running I looked around. Seems that the file that stores the backup configuration stores the the status of the job. I hacked the xml file and changed "running" to "success" then restarted the service and everything seems ok. Brilliant...
it lives here: \Program Files\NetApp\Virtual Storage Console\smvi\server\repository\backups.xml
2 REPLIES 2
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sigh, never mind. As the jobs weren't running I looked around. Seems that the file that stores the backup configuration stores the the status of the job. I hacked the xml file and changed "running" to "success" then restarted the service and everything seems ok. Brilliant...
it lives here: \Program Files\NetApp\Virtual Storage Console\smvi\server\repository\backups.xml
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just encounter the same issue after upgrading SMVI to version 4.1.I edited the backups.xml as you suggested and everything appears to be working. Thank you!
