- VOX
- Data Protection
- Backup Exec
- BE2012 catalog failed V-79-57344-33029
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
BE2012 catalog failed V-79-57344-33029
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2013 01:08 AM
Hello,
We recently moved our files to a new Win2008R2 server and did a fresh install of BE2012. The old server was Win2003R2 with BE12.5.
The backups are written to a storage device wich is connected by netwrok path. The server names are exactly the same.
For BE2012 we created a new networok path \\storage\backup_new
For BE12.5 we imported the old network path \\storage\backup_old and this has become a legacy to disk folder.
When we try to inventory and catalog both locations we get the errors below. We are now unable to restore any data. We have searched the forum for a solution but none worked so far. We have tried to move the old Catalog folder to the new server but this gives the same errors.
Any help is highly appreciated!
Catalog 00017 -- The job failed with the following error: The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation.
V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {B5B1E842-A1E4-4416-AA1E-13C2576F4ABF} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier.
Complete Job log error:
Drive and media mount requested: 11-3-2013 15:51:35 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {B5B1E842-A1E4-4416-AA1E-13C2576F4ABF} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:52:35 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {2F47B2E2-2859-4E5A-A859-A5C756D96540} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:53:35 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {621C6E2F-7E1F-4963-AF00-3964878F800C} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:54:35 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {A1A1D650-C7B6-4D9F-BD2B-48CB1C6DF256} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:55:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {74D77A47-470D-4F62-BF15-178F224C5D93} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:56:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {CCEEE499-6211-4A41-9A57-9B64F5823544} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:57:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {952E27C5-15D7-4B33-AB8A-0FCCE706D449} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:58:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {87004553-340A-490E-90D2-B0C4C6E0102D} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 15:59:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {8349CB28-6879-4FAB-89E1-5A87B89BE29F} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 16:00:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {BD1663A9-8FDE-4A14-BD53-4079085F15B8} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 16:01:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {6E429A33-0D8A-4B87-A432-08A31CA286E8} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier. Drive and media mount requested: 11-3-2013 16:02:36 V-79-57344-33029 - Error - Mount failed. Invalid Physical Volume Library Media Identifier. Media GUID: {F4B99BBC-0FE6-4D30-80B6-62329B23C870} V-79-57344-33029 - Unable to acquire device for the specified pool and media Invalid Physical Volume Library Media Identifier.
| Job Completion Status |
|---|
Job ended: maandag 11 maart 2013 at 16:03:36 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 |
Regards,
Jeroen van Lieshout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2013 07:46 AM
Was the inventory job that you ran successful?
edit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2013 07:49 AM
The inventory was succesfull.The catalog failed.
We are not using tapedrives but backup to disk to a network path (\\storage\map)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2013 01:44 AM
Is there anyone with a suggestion how to fix this issue?
Jeroen
- Problem BackupExec 21 After Crash in Backup Exec
- Duplicating tapes fails: INF - Cannot obtain resources for this job : error [167] in NetBackup
- Catalog job paused in Backup Exec
- Disk storage unit is full, but it's not full (netbackup 10.1.1) in NetBackup
- New Critical MSDP Security Functions Get Multi-Person Authorization (MPA) in NetBackup 10.4 API in NetBackup
