Backup Exec 11d error: Invalid Physical Volume Library Argument

[mikehiland]

We are just getting off the ground with BE 11d. We are creating policies that backup data to a Virtual Tape Library, then we schedule a Duplicate job to copy the media sets to tape.

I have five (5) backup jobs and five (5) duplicate jobs. The backup jobs all complete successfully. The first duplicate job runs for about fifteen minutes (should take an hour) and then throws error 0xe0008101 - Invalid Physical Volume Library Argument.

Nothing else is running when the job fails. The remaining four (4) duplicate jobs all complete successfully after the first one has failed.

Symantec's KB (doc id 280016) says it is probably a device driver issue and I have to go through a process of removing all device drivers and reloading them.

Before I do that, I am wondering if this makes sense? Four of my five jobs are successful, so do I really have a driver issue? Could it be something else?

Anyone have any other thoughts or experience with this?

Thanks in advance for your comments!

 

[DTracy]

Are the backup jobs full or what? And do the duplications run after each backup or what?

David.

 

[mikehiland]

The backups are mostly differentials (one is incremental). We will run the full over the weekend, but are not there yet.

The failing backup job starts at 5:15p and ends at 6:15p. The associated duplicate job starts just after midnight.

We basically run all of our backup jobs between 5:00p and 12:00am. Then, the duplicates start after that.

The same results last night. All backups are successful, then the first duplicate job fails with this error. The remaining four duplicate jobs run successfully.

Maybe I should delete and recreate the policy with the failing duplicate?

 

[DTracy]

The thing that I ran into is that duplication uses backup sets created during the backup job. Sometimes the append and overwrite settings will allow the re-use of a set file and when it's time for duplication to run the backup set doesn't match the actual folder contents. I think that is what is happening to your first backup set, it's being corrupted be successive backups before the duplication process starts. What you might try is to schedule the duplication to run immediately after each backup

Regards,
David.

 

[mikehiland]

With assistance from Symantec Tech Support, we applied build 7170 and SP2 which resolved the issue. The technician suspected the issue was related to a GRT issue usually associated with Exchange (which we do not use). The fix for the other issue was to apply build 7170, so we tried that and it resolved this issue.