BUG REPORT: Imports of VMWare Mapped FullVM Backups (Type 1, Type 2 and Type 3 Full) are imported as VMWare Type 0(File Level).
|Article:TECH63525|||||Created: 2008-01-24|||||Updated: 2012-12-12|||||Article URL http://www.symantec.com/docs/TECH63525|
BUG REPORT: Imports of VMWare Mapped FullVM Backups (Type 1, Type 2 and Type 3 Full) are imported as VMWare Type 0(File Level). When Virtual machine is selected in the restore console vmdk files do not appear.
When using NetBackup for VMWare to perform a Mapped FullVM (Type 1, Type 2 and Type 3 Full) backup with NetBackup version 6.5 to 6.5.5, import operation of those backups will result in only file level (Type 0) data being available for restore. For Type 1 backups, nothing can be restored until the header file is modified. This occurs because the import operations imports the data as a "VM_TYPE 0" backup. The data is still available, however manual steps are needed so NetBackup can safely restore the FullVM backups.
What is affected:
The following versions of NetBackup are affected by this issue, on all supported Windows platforms:
NetBackup Server/Enterprise Server 6.5 GA
NetBackup Server/Enterprise Server 6.5.1
NetBackup Server/Enterprise Server 6.5.2
NetBackup Server/Enterprise Server 6.5.3
NetBackup Server/Enterprise Server 6.5.4
NetBackup Server/Enterprise Server 6.5.5
For Multiplex backups, the issue can be seen in:
NetBackup Server/Enterprise Server 6.5.x
NetBackup Server/Enterprise Server 7.0.x
NetBackup Server/Enterprise Server 7.1.x
NetBackup Server/Enterprise Server 7.5.x
When attempting to import a Mapped FullVM backup performed on any of the above version, it will import as a File Level (Type 0) backup.
How to determine if affected:
This issue will occur if the following conditions are met:
Mapped Full VM backup either Type 2 or Type 3 Full backup was performed.
FullVM (Type 1) backup was performed.
Backups are performed to a disk base storage unit.
Backups are performed to a Tape Storage Unit or Backups are performed to a Tape Storage Unit using Multiplex.
NetBackup 6.x - 7.1 Procedures.
A Review of the Header File located in NetBackup\db\images will show the following VM_TYPE after an import operation:
This should number should reflects a 1 for Type 1 or a 2 for both Type 2 Full backup and Type 3 Full backup.
Since the problem occurs during the backup of the Virtual Machine, Symantec is unable to fix the issue for previous backups. However there is a workaround to restore VM_TYPE 1 and VM_TYPE 2 data from previous backups.
After completing the import, proceed to the NetBackup\db\images\<clientname>\<ctime> open the non .f file and change the following line:
The bold line "VM_TYPE 0" should be the following for a FullVM (Type 1) backup:
Or the following for Mapped FullVM backups (Type 2 Full or Type 3 Full):
NetBackup 7.5.0.x Procedures.
***Because NetBackup 188.8.131.52 and above stores the image headers in the EMM database instead of as flat files extra steps need to be taken to examine the header files and fix them if needed.***
1. Export the image header file(s) for analysis by using the following command:
cat_export -base <full path to export directory> -backupid <backupid>
*The export directory can be any directory you want*
2. A Review of the Header File located in the choosen export directory will contain the line:
This number should be a 2.
1. Change the 0 in the VM_TYPE line in the image header you exported to a 2.
2. Import the image header back into the EMM database by running the following command.
cat_import -base <full path to export directory> -backupid <backupid> -replace_destination
*The export directory should be the same one you used in Diagnosis step 1.*
Imports of VMWare Type 2 Backups are imported as VMWare Type 0. Also, VMDK files don't show up when Virtual Machine is selected in the NetBackup restore console.
Article URL http://www.symantec.com/docs/TECH63525