Daryl_Kinnaird
15 years agoLevel 4
Phase 2 Import failing
I'm trying to import data with long retention to my 6.5.5 netbakcup. The backups were done in our old 5.1 netbackup. Phase 1 of the improt completes successfully but when the phase 2 step is run I am getting the following in the details for the import.
Master sever is an HP-UX-IA64 11.23
Current netbackup 6.5.5
02/17/2010 06:00:42 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:42 - Error bpimport (pid=19179) from host verstke3, Skipping to next file header...
02/17/2010 06:00:42 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:43 - Error bpimport (pid=19179) Import of policy aix_jupiter1, schedule jupiter1_7yr (jupiter1_1104243138) failed, tar had an unexpected error.
02/17/2010 06:00:43 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:43 - Error bpbrm (pid=25550) could not write BPBRM_READ_FILENAME message to stderr: Broken pipe (32)
02/17/2010 06:00:45 - Error bptm (pid=25578) media manager terminated by parent process
Master sever is an HP-UX-IA64 11.23
Current netbackup 6.5.5
02/17/2010 06:00:42 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:42 - Error bpimport (pid=19179) from host verstke3, Skipping to next file header...
02/17/2010 06:00:42 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:43 - Error bpimport (pid=19179) Import of policy aix_jupiter1, schedule jupiter1_7yr (jupiter1_1104243138) failed, tar had an unexpected error.
02/17/2010 06:00:43 - Error bpbrm (pid=25550) from client verstke3: Skipping to next file header...
02/17/2010 06:00:43 - Error bpbrm (pid=25550) could not write BPBRM_READ_FILENAME message to stderr: Broken pipe (32)
02/17/2010 06:00:45 - Error bptm (pid=25578) media manager terminated by parent process
- The following T/N describes essentially what you are seeing:
Importing or verifying media will fail with Multiple Fragments on NetBackup 5.1 Maintenance Pack 3.
Snippets:
"...
The data on the tape will still be valid. This issue only affects the ability to do a successful phase 2 import or a successful verification of the tape that contains multi-fragmented images written prior to NetBackup 5.1 Maintenance Pack 3.
..."
and
"...
Please contact Symantec Enterprise Technical Support for a workaround to allow the import or verify of images.
..."
So this may be relevant & you may have to speak to Symantec, unless there is yet another workaround.