cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

BE2010R3 - Failed to mount image when attempting GRT restore

shelzmike
Level 2

I am having the most frustrating time trying to correct this issue and find any decent information on the subject. I have a daily incremental/full weekly policy running on our main data share using BE 2010 R3 (fully patched - agents deployed) using the VMWare agent. I am backing up via vCenter. Backups run well and are decently fast. Storage is tape.

I need to restore an individual file a user deleted that is fairly important. When I go back to the latest incremental, I see the file in the selection list. However, when trying to restore the file it fails with the following information in the job log:

Job Log: BEX_FPCBES3_13082.xmlJob Log for RW_XLS_stoc495sa 

 

      Completed status: Failed    See error(s) 
      Expand AllCollapse All 

      Job Information
Job server: FPCBES3
Job name: RW_XLS_stoc495sa
Job started: Monday, March 09, 2015 at 10:45:38 PM
Job type: Restore
Job Log: BEX_FPCBES3_13082.xml


      Job Operation - Restore 
            Server - VCB::
V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine VCB::.
The media server will use the local agent to try to complete the operation.
WARNING: Media servers cannot completely protect remote Windows-based servers or workstations unless the Backup Exec Remote Agent is installed and running on each remote Windows-based server or workstation to be protected. Data loss can occur if the Remote Agent is not running while restoring remote Windows-based computers.

Please refer to the documentation or online help for more information.
V-79-57344-33967 - 
V-79-57344-33967 - 
V-79-57344-33967 - 
V-79-57344-33967 - 


            Server - FFS1.hidden.local.domain.com
Drive and media mount requested: 3/9/2015 10:45:50 PM
Drive and media information from media mount: 3/10/2015 12:00:45 AM
Robotic Library Name: DELL 0001
Drive Name: IBM 0001
Slot: 1
Media Label: 000020
Media GUID: {aced460e-2379-41c3-b08c-b0bfcbdc3abc}
Overwrite Protected Until: 3/11/2015 11:52:42 AM
Appendable Until: 12/30/9999 7:00:00 PM

All Media Used
 000020

 000056

Network control connection is established between [::1]:54336 <--> [::1]:10000
Network data connection is established between    [::1]:54340 <--> [::1]:54339
Set Information - 
                  VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1 
                  VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1
                        Restore Set Information
Restoring data to VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1 VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1.

Storage Media #1: " Media created 2/27/2015 1:44:35 PM "
Backup performed on 3/5/2015 at 3:02 AM
Backup set #42: " Daily Incremental Backup "

 

Restore started on 3/10/2015 at 12:01:20 AM.
Restore completed on 3/10/2015 at 12:03:53 AM.
Restore Set Summary
Restored 0 files in 14 directories.
Restored 0 virtual machines
Restored 1 virtual machine disks
Processed 5,039,987,555 bytes in  2 minutes and  33 seconds.
Throughput rate: 1885 MB/min

 

 

Drive and media mount requested: 3/10/2015 12:04:23 AM
Drive and media information from media mount: 3/10/2015 12:05:35 AM
Robotic Library Name: DELL 0001
Drive Name: IBM 0001
Slot: 6
Media Label: 000056
Media GUID: {31e9bcaf-24c7-4fc4-8675-ebdcb050eea9}
Overwrite Protected Until: 3/11/2015 2:24:44 PM
Appendable Until: 12/30/9999 7:00:00 PM
Network control connection is established between [::1]:54354 <--> [::1]:10000
Network data connection is established between    [::1]:54358 <--> [::1]:54357
Set Information - 
                  VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1 
                  VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1
                        Restore Set Information
Restoring data to VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1 VMVCB::\\vCenter\VCGuestVm\(DC)FPC(DC)\vm\SOI\2003\FFS1.

Storage Media #1: " Media created 3/5/2015 3:00:08 AM "
Backup performed on 3/6/2015 at 3:03 AM
Backup set #15: " Daily Incremental Backup "

 

Restore started on 3/10/2015 at 12:06:27 AM.
Restore completed on 3/10/2015 at 12:08:07 AM.
Restore Set Summary
Restored 0 files in 14 directories.
Restored 2 virtual machines
Restored 1 virtual machine disks
Processed 2,224,777,385 bytes in  1 minute and  40 seconds.
Throughput rate: 1273 MB/min

 


V-79-57344-38721 - Failed to mount one or more virtual disk images:
 
Set Information - \\FFS1.hidden.local.domain.com\D: DataDrive
                        Restore Set Information
Restoring data to \\FFS1.hidden.local.domain.com\D: DataDrive.

Storage Media #1: "  "
Backup performed on 3/6/2015 at 3:03 AM
Backup set #15: " Daily Incremental Backup "

Restore started on 3/10/2015 at 12:08:33 AM.
Restore completed on 3/10/2015 at 12:08:33 AM.
Restore Set Summary
Restored 0 files in 0 directories.
Processed 0 bytes in  1 second.
Throughput rate: 0.000 MB/min


      Job Completion Status
Job ended: Tuesday, March 10, 2015 at 12:10:17 AM
Completed status: Failed
Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
Final error category: Job Errors

For additional information regarding this error refer to link V-79-57344-33967


      Errors
      Click an error below to locate it in the job log
Restore- VCB::V-79-57344-33967 - 

V-79-57344-33967 - 

V-79-57344-33967 - 

V-79-57344-33967 - 

RestoreV-79-57344-38721 - Failed to mount one or more virtual disk images:

      Exceptions
      Click an exception below to locate it in the job log
Restore- VCB::V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine VCB::.

The media server will use the local agent to try to complete the operation.

 

I am really not sure what is going on here or how to fix this. I am assuming that the major issue here is not being able to mount the Virtual Image, and the resulting "Directory or file not found or could not be accessed" is just being caused by there being no mount.

Have verified that the Remote Agent is indeed running on the FFS1 server (as well vCenter, etc.). Any help would be greatly appreciated. I am starting to get egg on my face here since I cannot get this file restored. I know it is there, just can't get to it.

 

Mike

1 ACCEPTED SOLUTION

Accepted Solutions

shelzmike
Level 2

The solution was actually one that I kept consistently overlooking. Well, the problem was overlooked. The solution was easy once I figured the problem. 

It was the overwrite protection period that was causing the problem. The incrementatal media was protected for only 2 days before it could be overwritten. Now, why it chose to overwrite this tape for more current backups immediately even though we had 10 other clean tapes ready to use in the library I do not know. 

Basically, the catalog had the file listed, but when trying to restore it, it could not find it, and in all honesty, it was trying to tell me that!

I had to go back and restore an entire full backup from the day prior (900GB from tape just for 1 13k file!) and was able to retrieve the data. 

Thanks for all the help. Since this post, we have done away with tape for good and are now using strickly B2D on our 7TB SAN so we are OK now. Restores take less than 1 minutes usually so we are all good there. 

We will still run duplication jobs over to tape on a weekly basis, but no first line backups. Thanks!

 

Mike

View solution in original post

3 REPLIES 3

CraigV
Moderator
Moderator
Partner    VIP    Accredited

..check and see if this is relevant to your issue:

http://www.symantec.com/docs/TECH144501

Thanks!

pkh
Moderator
Moderator
   VIP    Certified

It could be that you have insufficient disk space to stage the backup set.  Duplicate the backup set from tape to disk and then do your restore from the disk backup set.

shelzmike
Level 2

The solution was actually one that I kept consistently overlooking. Well, the problem was overlooked. The solution was easy once I figured the problem. 

It was the overwrite protection period that was causing the problem. The incrementatal media was protected for only 2 days before it could be overwritten. Now, why it chose to overwrite this tape for more current backups immediately even though we had 10 other clean tapes ready to use in the library I do not know. 

Basically, the catalog had the file listed, but when trying to restore it, it could not find it, and in all honesty, it was trying to tell me that!

I had to go back and restore an entire full backup from the day prior (900GB from tape just for 1 13k file!) and was able to retrieve the data. 

Thanks for all the help. Since this post, we have done away with tape for good and are now using strickly B2D on our 7TB SAN so we are OK now. Restores take less than 1 minutes usually so we are all good there. 

We will still run duplication jobs over to tape on a weekly basis, but no first line backups. Thanks!

 

Mike