BMR boot server upgrade to 7.6.0.1 does not clean-up existing Windows PreInstall 2.1 images

Article:TECH215828  |  Created: 2014-03-14  |  Updated: 2014-06-09  |  Article URL http://www.symantec.com/docs/TECH215828
Article Type
Technical Solution


Environment

Subject

Issue



Netbackup 7.6 introduces support for BMR (Bare Metal Restore) WinPE (Windows Preinstallation Environment) 3.0 infrastructure.  In NetBackup 7.6.0.1, the BMR Windows Recovery Environment is upgraded from the MS-WinPE 2.1 version, which was based upon the Windows Server 2008 OS, to the MS-WinPE 3.0 version, which is based upon Windows 2008 R2 (6.1) OS.  This upgrade helps reduce the driver issues that are faced with BMR recovery environment as WinPE 3.0 has in-built most of the latest device drivers.

When the BMR boot server is upgraded from a previous version and especially when there are few existing SRTs (shared resource trees) available, the upgrade process does not automatically clean-up the older MS-WinPE 2.1 images. These need to be cleaned up manually.

If the manual cleanup is not done, there is a risk creating subsequent SRTs which will have the wrong version of MS-WinPE.  This can impact restores.


Environment



Windows BMR boot server version 7.6.0.1, when upgraded from a Netbackup version earlier than 7.6.0.1


Solution



 Follow the procedure listed below to perform a manual clean-up:

1. On the BMR boot server, browse to <Install_Path>\Veritas\Netbackup\BareMetal\Server\Data
 
2. There can be two SRD wim files as seen below:
  • srd_x64.wim (155,672 KB) 
  • srd.wim   (135,898 KB)
 
3. Delete both SRD wim files.
 
4. The newer SRD wim files of MS-WinPE 3.0 will get copied to this location during the next SRT creation event. 
 
Note: When you configure the 64-bit SRT for the first time, you need to specify the source location of SRD. This would be at path
<DVD root>\Addons\x64\BMRBS\srd_x64.wim (177,850 KB)
 
5. Reboot the Boot Server.

Supplemental Materials

SourceETrack
Value3512485


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


Terms of use for this information are found in Legal Notices