Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Duplicate Job Fails

Updated: 22 May 2010 | 7 comments
Corey Wilson's picture
0 0 Votes
Login to vote

Duplicate Failure

I am trying to understand why my duplicate job failed this weekend. It dosent really give an error code that would explain it.

I have three policies created each with two templates. The three policies each backup a different set of servers to disk and are scheduled to start at the same time. The templates for each policy are the same. One is the configuration of the job to disk, the second is the duplicate of that disk job to tape once the backup to disk job completes. They are all configured the same way.

The three backup to disk jobs completed correctly, the first duplicate to disk job duplicated fine, the second duplicate job failed at 13gb of 211 gb written to tape but the third duplicate job ran successfully and copied all data like the first duplicate job. The jobs are set to append to tape for 3 days. So each duplicate job will write to the same tape until full and then span to the next.

What I don�t understand is why the first duplicate job completed successfully (98gb duplicated to tape, 98gb originally written to disk), the second duplicate job failed (13gb duplicated to tape but 211gb originally backed up to disk) then the third job started after this one and duplicated successfully (189gb to tape and 189gb written to disk) each job sent to the same tape, so its not a media issue, nor a drive issue as the third job finished just fine. The third job did NOT cause the second job to cancel either because it had failed duplicating to tape before the third job had finished writing to disk.

This is the error:

Job ended: Saturday, January 06, 2007 at 11:16:18 PM Completed status: Failed Final error: 0xe0008105 - Invalid Physical Volume Library Media Identifier. Final error category: Job Errors For additional information regarding this error refer to link V-79-57344-33029


Click an error below to locate it in the job log


Duplicate- Exch
Media mount failed.
Invalid Physical Volume Library Media Identifier.


I read the article but it dosent really relate. First of all I could understand maybe the tape needing to be cataloged if the other jobs failed but how could the first job write successfully, the second configured exactly the same fail after a few minutes and then third job complete successfully to the same media and the same drive?

Your assistance is appreciated since this makes no sense to me!

Thanks

Comments

tejashree Bhate's picture
15
Jan
2007
0 Votes 0
Login to vote

Hello,

Check if the following is useful


Invalid Physical Volume Library Media Identifier" (a0008105 HEX or e00008105 HEX) is reported when a restore job fails

http://support.veritas.com/docs/260761

Thanks

Johan Ahlfeldt's picture
16
Jan
2007
0 Votes 0
Login to vote

I'm seeing the same problem. The link does NOT address the outlined problem.

The problem I'm seeing only applies to duplicate to tape of information stores ...

Anyone else seen/solved this? Tech. support is trying hard ... but does not seem to be able to figure it out either.

Thanks,

- Johan

Johan Ahlfeldt's picture
23
Jan
2007
0 Votes 0
Login to vote

Jobs run fine when disabling GRT. Looks like a BUG. Symantec is investigating ...

- Johan

Will FEATHERSTON's picture
05
Feb
2007
0 Votes 0
Login to vote

I am having the same problem... and I realized it is linked to the Information Store also... I have had GRT enabled... But, knew it wouldn't work on my 64bit server (Symantec working that issue also)... Have disabled GRT for now... Will report if it works... Do you think the D2D will have to be completely rebuit? As all of those backups were completed using GRT...

Gernot Eder's picture
26
Feb
2007
0 Votes 0
Login to vote

Hi!

it is the same with my duplicate jobs. B2D works fine, a direct backup to tape job works fine too, but if i try the copie job (disk to tape) it fails with the same final error. (Windows 2003 Server - 11d)

There are still no solutions to find - i have written to the support mail address, but got no response till now. Any ideas or solutions or settings i can try out to make it work??

cheers,
Gernot

Larry Risser's picture
26
Feb
2007
0 Votes 0
Login to vote

How do you disable GRT? What is GRT?
Anyone get a resolution from Symantec yet?

Will FEATHERSTON's picture
26
Feb
2007
0 Votes 0
Login to vote

GRT = Granular Restore Technology... (The ability to restore individual mail messages and folders from Information Store backups)

Symantec is aware that it does NOT work on Backup Exec 64bit version.
(Backup or Restore)

There are other issues now with it running on 32 bit versions.
(See previous posts)

These problems are all in the 11d release.
(As far as I know, Previous 32 bit versions worked for me)

No resoultion to any of the issues listed yet.

To disable GRT... Uncheck the "Enable the restore of individual mail messages and folders from Information Store backups"

This option is located under the "Microsoft Exchange" Settings in your backup job.

Doing this will force a full restore of your Information Store in case it is needed... No individual mail messages or folders.