How to troubleshoot a Restore Anyware Option (RAO) retargeting issue

Article:TECH53848  |  Created: 2007-01-12  |  Updated: 2013-10-30  |  Article URL http://www.symantec.com/docs/TECH53848
Article Type
Technical Solution


Subject

Issue



How to troubleshoot a Restore Anyware Option (RAO) retargeting issue.


Solution



Introduction:
 
This checklist offers a detailed step-by-step approach for troubleshooting and performing a migration restore using the Symantec Backup Exec System Recovery Restore Anyware option.
 
The checklist is composed of four sections.
 
I. Pre-restore checklist and Considerations
II. Restoration Process
III. Gathering restore wizard logs
IV. Gather Windows mini wizard logs
 
Following this guide will often resolve if not pinpoint the main cause of most migration restore issues.
 
Pre- Restore Checklist

Considerations:
  • Is the original system still up and running?
  • Has the recovery point image file been verified either by assigning the job to verify by using recovery point browser?
  • Is the restore being performed on the same subnet/same domain or different as the source? 
  • Does the new hardware support the operating system that will be restored to it: www.symantec.com/docs/TECH185654
Note:  If the system is a domain controller, see the following technote on how to restore a domain controller:  http://www.symantec.com/docs/TECH87052

Driver Validation:
  • The following technote outlines how to use the driver validation tool to assure all drivers are included in the Symantec Recovery disc for the system that is being restored:  http://www.symantec.com/docs/TECH54855

Note: Drivers can also be loaded manually within the default SRD by using the 'Load a driver' options within the SRD's utilities.

Restoration platform:
  • Virtual guest container (e.g. VMware, Microsoft virtual Server)
  • Is the machine being restored a duplicate of another server on the same domain?   
To change the SID see the following link:   http://seer.entsupport.symantec.com/docs/297353.htm  

Source System Information:
  • System make/model (e.g. Dell Poweredge 1800)
  • System OS & Service pack (e.g. Windows 2003 Enterprise SP2)
  • Mass-storage controller make/mode/ disk setup &/or RAID config (e.g. PERC 4di RAID1)
  • Number of partitions being restored in their order (e.g. C {SYSTEM.EN_US} 30 GB / D {DATASTORE.EN_US} 80GB)
  • Are all these partitions on the same physical volume or across multiple volumes (e.g. Same RAID volume)
  • NIC & its configuration (e.g. Intel Pro 1000/MT teamed) • Services /Application (e.g. Exchange, SQL, Oracle, etc.)
  • Network resolution services (e.g. ADS, DNS, DHCP, WINS)  
  • Was the source system part of a cluster?i. Was the cluster a active-passive or active-active (e.g. AA/AP)
  • Was Citrix Metaframe application server.

Note: Citrix Metaframe application server is no longer a supported environment for BESR.

Destination system information:
  • System make/model (e.g. Dell Poweredge 2650)
  • Mass-storage controller make/mode/ disk setup &/or RAID config (e.g. PERC 5ei RAID5)
  • System memory (e.g. 8 GB) • NIC being used (e.g.  Broadcom Netextreem 57xx) II. Restoration Process
  • Further Pre-Boot Restoration considerations.
  • Is there data on the destination system that needs to be retained after restored attempt, if so, is this data backed up?
  • Booting into the recovery environment using the Symantec Recovery Disk (SRD)
  • Is the storage for the recovery points being restore stored on a local external hard drive or a networked location?
  • Select no when prompted to load network services.
  • If  recovery point is stored on a networked location, select yes.
 
Restoration Process:

DISKPART Utility:
  1.  Click "Analyze", then click "Open Command Shell Window".
  2. At the command prompt, type diskpart and press Enter.
  3. Type list disk*, to learn of the disk number of the internal drive to perform the disk operation upon; and then press Enter.
  4. Type sel disk, enter the disk number of the internal destination drive and then press Enter.
  5. Type CLEAN and then press Enter.
  6. Type EXIT and then press Enter to leave DISKPART.
  7. Type EXIT and then press Enter to leave the command prompt window.
Note: The list disk command will give a listing of the available drives. If the drive is not visible here, it is not being recognized by the Symantec Recovery Disk. If the drive is not present, type Exit and from the main menu using the, 'Load a driver,' menu option to load the VISTA/Windows 2003 mass-storage controller driver may assist in listing the internal drive in the next attempt.

Delete partitions:
 
Unless there is data that needs to be retained, use the 'Partition table operation'  and 'First Track Operation' tool within the SRD utilities.
 
For deleting existing partitions:
Click on Utility option within the SRD.
Click on ' Run support tool, a new popup menu will appear, then click on 'Partition Table Operation'.
Select the destination disk for the restore from the drop down, then select delete, then next then finish.

Wipe first track:
  • On the "Run Support Tools" option menu, select 'First Track Operation'.
  • Select the destination disk for the restore from the drop down, then select wipe, then next and then finished.
  • Reboot.
Reboot back into the SRD:
 
If the recovery point is stored on a network drive, the storage point will need to be mapped . Use the following technote to map a network drive within the system recovery disc.    http://www.symantec.com/docs/TECH76187

Note: Browsing option does not always work. When entering the UNC path use the IP address instead of the server computer name. Make sure to enter the credentials for a user account that has full admin rights to the share. Using the NET USE command to map a network drive within windows command prompt: 
  • Move the mouse cursor to the upper left corner of the screen near the letter S in Symantec. When the arrow icon changes to a hand icon, left-click to open a command prompt.  
  • In the command prompt window type the following:
  • NET USE Y: <\\COMPUTERNAME\SHARENAME> /USER: COMPUTER_NAME\ADMIN_USER_ACCOUNT PASSWORD <PRESS ENTER>
  • COMPUTERNAME = name of the system where the recovery point images are being stored.
  • SHARENAME = The name of the share on the system where the recovery point images are being stored.
  • ADMIN_USER_ACCOUNT =   a user account that has full admin rights to the share.
  • PASSWORD = the password for the ADMIN_USER_ACCOUNT for external hard disk device:
  • From the main menu choose 'Analyze' then choose 'Explore My computer.
Restore Wizard:
 
  1. Boot into the Symantec Backup Exec System Recovery Disk.  If you followed the last step, you may already be in the recovery environment.

NOTE: If the recovery point set to be recovered is stored on a network location, do the following: From the home tab, select "Map a Network Drive" and "Load a driver" to map to the share; additional network drivers needed be loaded to see the share. To load drivers, from the main menu choose, "Load a driver," option.

  1. From the "Home" tab, select "Recover My computer".

NOTE: Click "Next", you may receive a prompt stating "No recovery points found in any of the recovery point storage locations on this computer. Choose another location to search for recovery points."  If you receive this message click "OK'.  

  1. On the next screen, select the "View by:" drop down menu and select "View by: Filename".  
  2. Do one of the following:

            i. (Restoring a baseline or Independent image): Browse to the location of the *.v2i file that contains the system disk to restore.

WARNING: Restoring the baseline recovery point (i.e. just the .V2i file) of a recovery point set that contains incremental updates will result in a restored drive at the moment of V2i file creation, any changes stored within the incremental updates (i.e. *.iv2i files) would be lost.

           ii. (Restore from a specific incremental update): Browse to the location of *.iv2i file of the system disk to restore; change the file view to, 'Details,' to show the date/time stamp to decide from which point-in-time incremental to choose from.

 

  1. Once you have selected the .v2i or *.iv2i file to restore from.
  2. On the Initialize Disk Partition Structures screen, click the disk number that was wiped using DiskPart, then click "OK" then "Yes".
  3. On the "Drives to Recover" screen, click the appropriate recovery point date to recovery, then select "Edit".  
  4. The Edit Target Drive and Options will show you the destination for the recovery. Select the NTFS partition and click "Delete Drive".
  5. Select the "Unallocated" space.  Below are the correct options for System Drives and Data Drives.
 
System Drive (contains OS):
[x] Resize restored drive.   The size should default to the maximum available space on the target drive. You can use this option to define the size of the partition.
[x] Primary Partition
[  ] Check for file system errors after recovery
[x] Set drive active (for booting OS)
[  ] Restore Original Disk Signature
[x] Restore MBR
[  ] Preserve domain trust token on target drive (recommended),
 
Data Drives:
[  ] Check for file system errors after recovery
[x] Resize restored drive.   The size should default to the maximum available space on the target drive.
[ ] Primary Partition
[ ] Set drive active (for booting OS)
[x] Restore Original Disk Signature
[ ] Restore MBR
[  ] Preserve domain trust token on target drive (recommended),
 
10. Click "OK".  
 
11. Check "Use Restore Anyware to recovery to different hardware" .  
 
NOTE: If a previously restoration failed with a Windows Bluescreen,  hidden Restore Anyware options can may be of assistance.  Holding down the CTRL or SHIFT keys and clicking the "Use Restore Anyware to recovery to different hardware" check-box.  Select the check boxes besides the, 'Delete Existing Drivers', 'Prompt for Drivers,' and, 'Run Windows Mini-Setup'.  If you are experiencing bluescreen issues server running Windows 2008 or Windows SBS 2003 or 2008, un-check "Run Windows Mini-Setup".   Once you have selected the relevant options, click "OK" then click Next.
 
12. On the completion wizard screen, click "Reboot when finished" if only a single drive is being restored or uncheck "Reboot when finished" if there are multiple drives contained in the backup, then select "Finish" to complete the restore.
 

Note: For information and considerations for restoring a domain controllers, see the following technotes:
http://www.symantec.com/docs/TECH60934
http://www.symantec.com/docs/TECH87052
http://www.symantec.com/docs/TECH87092

Note: Below is further explanation of options that may be used during a restore.
 
Verify recovery point before restore:
Verifies whether a recovery point is valid or corrupt. This option CAN significantly increase the time required for the recovery to compile.
 
Restore Anyware:
Use this option if restoring to unlike hardware from which the original recovery point was taken.
 
Resize drive after recovery:
Select this option to resize the restore partition to preferred size.
 
Partition Type:
Primary Partition: Because hard disks are limited to four primary partitions, select this type if the drive will have four or less partitions.
Logical Partition: Select this type if more than four partitions. NTFS supports up to 4 primary partitions, plus any number of logical partitions, up to the maximum size of the hard disk.
 
Check for files system errors after recovery:
Checks the restored drive for errors after the recovery point is restored.
 
Set Drive Active ( for booting OS)
Makes the restored drive the active partition. Select this option if the restoration drive contains the operating system.
 
Restore original disk signatures
Restores the original, physical disk signature of the hard drive. Disk signatures are included in Windows Server 2003, Windows 2000 Advanced Server, and Windows NT Server 4.0 Enterprise Edition (SP3 and later)
 
Restore MBR
Restores the master boot record. The master boot record is contained in the first sector of a physical hard disk. The MBR consists of a master boot program and a partition table that describes the disk partitions. The master boot program looks at the partition table of the first physical hard disk to see which primary partition is active. It then starts the boot program from the boot sector of the active partition.
 


Gathering restore wizard log files

If in following this guide, the restore process fails before allowing the system to boot into Windows for the first time on this restore attempt gather the restore wizard logs following the steps listed below.
  1. Return to the main menu.
  2. Click the utilities options from the main menu.
  3. Click Run support tools.
  4. From the sub-menu that appears choose, 'Gather Technical Support Information.'
  5. A warning message stating not to close the application while it is processing gathering the log files. Be sure not click onto any other option while logs are being gathered.
  6. From the 'Browse for folder,' menu click on the Map the network share drive or external drive letter use to store the recovery point images.
  7. Once the drive/sub-folder section has been selected, click the 'Make New Folder' sub-folder option.
  8. In the dialog box that appears, name the folder SUPPORT as the sub-folder to be created to store restore log files into.
  9. Select the SUPPORT sub-folder from the sub-folders list present and have them click the OK button.
  10. On the summary screen that appears click the OK button.
  11. Properly exit out of the recovery environment, disconnect all external drive devices (if present on destination system), and allow the system reboot into windows for the first time. 
  • Close out of any utility windows.
  • Disconnect USB/firewire drives.
  • Choose the Exit link that appears at the bottom right hand corner of the main menu.
  • Once the system reboot choose to NOT to boot from CD and allow the system to attempt booting into windows.
 
Gathering windows setup log files

Once the destination system has attempted to boot into windows, to finish the migration, it will attempt to run the Plug and Play (PnP) and the mini-setup wizards. These Windows process generates log files that could assist in further troubleshooting any issues that arises at this point in the migration restore process. To gather these log follow the steps listed below.
 
1. Properly power down the system.
 
2. Properly plug back the USB or Firewire drive (if present and use in the restore attempt)
 
3. Properly power up the system.
 
4. Reboot back into the recovery environment.
 
5. Map a drive letter if it was use during the restore attempt or determine the drive letter assigned to the USB/Firewire drive now. 
  • From the main menu open a command prompt window.
  • Move the mouse cursor to the upper left corner of the screen near the letter S in Symantec. When the arrow icon changes to a hand icon, left-click to open a command prompt.
  • Navigate  to either the mapped drive letter or the external drive device.
  • Type the drive letter followed by a : and press the Enter key (e.g. F: <enter> )
  • Using the make directory command create the directory sub-folder name SETUP.
  • Type; MD SETUP and press the enter key.• Change to the sub-directory SETUP.
  • Type; CD SETUP and press the enter key.• Change to the Windows sub-directory on the system drive restored.
  • Type; C:\Windows and press the enter key.• Copy the SETUP log files generated from the Windows folder to the SETUP sub-folder.
  • Type; COPY SETUP.* <DRIVE_LETTER_OF_SETUP_FOLDER> and press the Enter key.
  • <DRIVE_LETTER_OF_SETUP_FOLDER> is JUST the drive letter of the mapped or the external drive.
  • Copy the SYSTEM registry hive of the restored system to the SETUP sub-folder.
  • Type; CD system32\config and press the Enter key
  • Type; COPY SYSTEM <DRIVE_LETTER_OF_SETUP_FOLDER> and press the Enter key.
  • Again <DRIVE_LETTER_OF_SETUP_FOLDER> is JUST the drive letter of the mapped or the external drive; not the full path.
  • Verify the contents of the SETUP folder that at least four specific files are present.
  • Type <DRIVE_LETTER_OF_SETUP_FOLDER> and press the Enter key; (e.g. F: <enter> )
  • Type DIR and press the Enter key10. Verify that the folder contains the following four files:
  • setupapi.log
  • setuperror.txt
  • setuplog.txt 
6. On a second system, within Windows:
  • Zip up the Source system log.
  • Zip up the Restore wizard log.
  • Zip up the Windows Setup log.



Legacy ID



291727


Article URL http://www.symantec.com/docs/TECH53848


Terms of use for this information are found in Legal Notices