02-28-07 06:13 PM
"mr.petex" <mr.petex@gmail.com> wrote in message
news:1170855909.479526.140720@v45g2000cwv.googlegroups.com...
>
> We are using V2I protector 2.02 as our main backup method. We have
> several errors that i cannot find resolutions for and i am hoping
> that one of you intellegent engineers has already solved these issues
> and can pass on your hard earned knowledge............
>
> Error1: Windows 2000 sever
> 2/7/2007 3:00:26 AM
> Notification Type: Error
> Priority: High
> Description: An error occurred during a scheduled backup of drive C:\.
> Error EC8F000E: Cannot create a Virtual Volume Image of the requested
> volumes. Error EC8F000D: The Virtual Volume Image driver cannot
> complete the IOCTL_VSNAP_SET_COMMIT command. Error 000005AA:
> Insufficient system resources exist to complete the requested service.
> Details: Unspecified error
>
> Error2: windows 2003 server
> Date: 2/7/2007 3:00:18 AM
> Notification Type: Error
> Priority: High
> Description: An error occurred during a scheduled backup of drive E:\.
> Error EC8F0010: Cannot track changes to drive E:\. Error 000003ED: The
> volume does not contain a recognized file system.
> Please make sure that all required file system drivers are loaded and
> that the volume is not corrupted.
> Details: Unspecified error
>
>
>
> Error4: similar to error1
> Date: 2/7/2007 1:00:16 AM
> Notification Type: Error
> Priority: High
> Description: An error occurred during a scheduled backup of drive E:\.
> Error EC8F0007: Cannot create a Virtual Volume Image of E:\. Error
> 000005AA: Insufficient system resources exist to complete the
> requested service.
> Details: Unspecified error
>
> The machines in question are Windows 2000 and 2003 servers with
> hardware raids up to 220GB. They contain a large volume of small
> files........ The machines have been reinstalled(v2I) rebooted and
> degfraged.......
> Please help if you can....I've spent long hours on symantec's site and
> googled till the cows come home but no luck.
> Peter
Not sure if this will help, but try clearing V2i's backup event log. I know
when I was using V2i version 2, after some months of daily backups, it took
an incredibly long time to load the tab to view the backup event history.
IIRC, this was solved with version 3 (LiveState Recovery)
Every time I've seen an "insufficient resources" error with V2i, a reboot
usually solves it, but sounds like it did not in your case.
Error 2 sounds like forcing a CHKDSK run might be a good idea...
-- Paul
[ Post a follow-up to this message ]
| 
