Sorry--I meant it's running as the 'default': Local System Account. I tried running as administrator, but it had no effect. Here's my log snippets:
+ Normal backup using Daily Backup--Even Weeks at 5/22/2003 12:59 AM (Execution unit 1)
To Backup Set EvenTapeSet...
Can't use Open File Backup option for Drive C (C:), error -1019 (not enough resources)
- 5/22/2003 12:59:00 AM: Copying Drive C (C:)
File "C:\WINNT\system32\Perflib_Perfdata_4d4.dat": can't read, error -1020 (sharing violation)
File "C:\WINNT\system32\wins\j50.log": can't read, error -1020 (sharing violation)
File "C:\WINNT\system32\wins\wins.mdb": can't read, error -1020 (sharing violation)
File "C:\WINNT\system32\wins\winstmp.mdb": can't read, error -1020 (sharing violation)
File "C:\WINNT\Temp\VxsvcError.log.tmp": can't read, error -1020 (sharing violation)
5/22/2003 1:17:27 AM: Snapshot stored, 51.1 MB
5/22/2003 1:17:30 AM: 5 execution errors
Remaining: 5 files, 4,168 KB
Completed: 14 files, 10.2 MB
Performance: 303.4 MB/minute
Duration: 00:17:52 (00:10:20 idle/loading/preparing)
(it does this for every server drive. It does this for volumes that don't have any open files, as well):
Can't use Open File Backup option for BigMama (M:), error -1019 (not enough resources)
- 5/22/2003 1:18:11 AM: Copying BigMama (M:)
5/22/2003 2:34:19 AM: Snapshot stored, 37.1 MB
5/22/2003 2:34:22 AM: Execution completed successfully
Completed: 1 files, 65.9 GB
Performance: 1074.2 MB/minute
Duration: 01:16:46 (00:01:02 idle/loading/preparing)
The clients do not report that they are using the Open File Backup option, but the only errors I seem to be getting on the clients are other weird ones (like 'improper seek'), which I think are just disc corruption on the client.
The hardware (should it matter) is a Dell Poweredge 2650. Discs are all SCSI volumes. There's this 'Storage Manager' software Dell ships on these systems to manage the arrays--this wouldn't be causing a problem, right? I guess I'm not quite sure what the 'open file backup' option in Restrospect does in order to function.
While I'm listing my problems with Retrospect, it also appears that the 'Execution Performance Threshold' doesn't have the expected behavior: You'd think it would keep going if a client dropped below the threshold set, but instead the entire backup operation aborts if one client drops below that threshold.