05-06-2014 08:23 PM
We run remote NDMP backups to tape with multiplexing setting of 2 to 4. We'd need to duplicate such backups to another pool, and I found that "preserve multiplexing" should not be selected or else the duplication job will fail.
Deselecting "preserve multiplexing" would make the duplication much slower.
Is this expected? We're using NBU 7.1, has this limitation been overcome in newer version?
Solved! Go to Solution.
05-08-2014 03:14 AM
OK - have you aplied any other hotfixes since installing 7.1.0.4
I have just had a look and the EEB to fix this error contains just bptm.exe - if you have applied another hotifx since then perhaps it has brought the bug back
The error is so similar it seems likely to be related - but i would raise a case with support and get them to investigate as i cannot see anything else that relates to this issue
05-06-2014 11:45 PM
What is the error you see when you keep 'preserve multiplexing'? Does bptm crash?
05-07-2014 01:07 AM
2014-05-06 00:02:03 - Error bpduplicate(pid=6732) Duplicate of backupid vfiler01_1399284022 failed, fatal NB media database error (91).
2014-05-06 00:02:03 - Error bpduplicate(pid=6732) host xxx backup id vfiler05_1399284036 read failed, fatal NB media database error (91).
2014-05-06 00:02:03 - Error bpduplicate(pid=6732) host xxx backup id vfiler06_1399284038 read failed, fatal NB media database error (91).
2014-05-06 00:02:03 - Error bpduplicate(pid=6732) host xxx backup id vfiler01_1399284198 read failed, fatal NB media database error (91).
The above error will be seen upon the completion of the first session.
05-07-2014 01:08 AM
I guess you will need to have a look at the verbose bptm log, unless someone has faced this error or is a known issue in 7.1.
05-07-2014 04:44 AM
Sounds very much like this issue: http://www.symantec.com/docs/TECH177264
Bearing in mind that a duplication follows the same process as a restore
Worth patching to 7.1.0.4 if you are not there already?
05-07-2014 06:23 PM
Thx, but we are already at 7.1.0.4.
05-08-2014 03:14 AM
OK - have you aplied any other hotfixes since installing 7.1.0.4
I have just had a look and the EEB to fix this error contains just bptm.exe - if you have applied another hotifx since then perhaps it has brought the bug back
The error is so similar it seems likely to be related - but i would raise a case with support and get them to investigate as i cannot see anything else that relates to this issue