FlashBackup-Windows or Virtualization restores using the touch file ALT_RESTORE_COPY_NUMBER persists in requesting the original primary copy.
|Article:TECH60998|||||Created: 2008-01-16|||||Updated: 2014-03-31|||||Article URL http://www.symantec.com/docs/TECH60998|
FlashBackup-Windows or Virtualization restores using the touch file ALT_RESTORE_COPY_NUMBER persist in requesting the original primary copy.
Review of the log files will show that everything in the restore appears to be fine until bpdm requests the storage unit information from bpdbm.
The bpdm log file will show the call to bpdbm:
The bpdbm log will show receipt of the call:
The bpdbm process will execute a SQL statement to fetch the storage unit information, but it always returns the original storage unit:
Note that in the output the copy 1 storage unit is returned. in the StorageServiceName information, in this case 'any_stu_copy1'
The bpdm log file then shows the @aaaaa media id versus the actual copy 2 media.
15:22:00.151  <2> read_backup: file @aaaaa, copy 1, fragment 1 (26906763 Kbytes) being considered for read-blockmap
Since the stu/media doesn't exist in this particular example environment, the restore exits with 2067.
15:22:00.393  <4> nbjm_media_request: Error from RequestMultipleResources, Master my_master, error 2067,
This can affect images created by NetBackup FlashBackup-Windows, VMware, and Hyper-V policies. This will also impact the bprestore command when using the -copy option to specify a non-primary copy.
The workaround is to change the primary copy of the backup ID required for a restore to the required copy, normally copy 2. For example, to change copy 2 of just one specific <backupid> to be primary, use either of these from C:\Program Files\VERITAS\NetBackup\bin\Admincmd:
This issue is tentatively scheduled to be addressed in the following release:
- NetBackup 18.104.22.168
As fixes are released, please visit the following link for download and readme information:www.symantec.com/enterprise/support/overview.jsp
Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Single File Restore from Non-Primary image copy of a VMware backup still uses primary copy (will fail if primary copy not available).
Article URL http://www.symantec.com/docs/TECH60998