Highlighted

Cannot duplicate images using SLP. Image replicated using AIR

Cannot duplicate images with are replicated using AIR.

I get this error:


Feb 19, 2019 3:06:33 PM - Error bptm (pid=4047) cannot add fragment to image database, error = no entity was found
Feb 19, 2019 3:07:10 PM - Info bptm (pid=4047) EXITING with status 227 <----------
Feb 19, 2019 3:09:39 PM - Error bptm (pid=31177) cannot connect to the writing side process for TIR duplication, Success
Feb 19, 2019 3:09:42 PM - Error bptm (pid=31177) media manager terminated by parent process
Feb 19, 2019 3:09:42 PM - Error bpduplicate (pid=1948) host sivls106 backup id HQSQL2K16_1518700652 read failed, media manager killed by signal (82).
Feb 19, 2019 3:09:42 PM - Error bpduplicate (pid=1948) host sivls105 backupid HQSQL2K16_1518700652 write failed, no entity was found (227).
Feb 19, 2019 3:09:42 PM - Error bpduplicate (pid=1948) Duplicate of backupid HQSQL2K16_1518700652 failed, no entity was found (227).
Feb 19, 2019 3:09:42 PM - Error bpduplicate (pid=1948) Status = no images were successfully processed.
Feb 19, 2019 3:09:42 PM - end Duplicate; elapsed time 0:28:06
no images were successfully processed  (191)

Tags (2)
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Cannot duplicate images using SLP. Image replicated using AIR

Ngarart

What I can tell you ... I had the same issue. VM backup at source with ASC, replicated to remote domain and than duplicated to tape... last part of SLP was failing... here is what I did recieve from VRTS CE:
"DIAGNOSTIC STEPS/CAUSE:   
When application protected backup is being taken it creates a placeholder entry in dbm_main.dbm_image table but if the ASC job does not find application installed on client VM the placeholder entry is not cleaned up and this entry exists as a dependent of VM client backup image in the NBDB image database.

In AIR setup when this image is replicated to Target Master Server, the VM client backup image gets imported successfully at Target Master but the dependent image entry of image table is not imported as it is not a valid backup. At the time of duplication (on tape) at Target Master it checks for the dependent image as the VM backup image record having “hasdependents” set to 1 but it does not find any entry in dbm_main.dbm_imagedependency table, so duplication fails.

RESOLUTION SUMMARY:  
Issue fixed in 8.1, as the DR master is lower version then source master server which is not recommended.

"

View solution in original post

9 Replies
Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

Netbackup Version: 8.1.1

OS: SLES 12 SP1

I am duplicating images from Quantum disk to Tape.

Tags (2)
Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

More info, please...

Is the duplication included in the SLP that is doing the AIR import? 

Is this a 'regular' duplication config or are you doing Quantum 'direct to tape' duplication? 
Have you tested a backup to tape to ensure that all is working fine with tape STU config? 

Could you please share all text in Job Details?
And full bptm log (as .txt attachment)?
We need to see info about the read portion of the job (pid=4047) and the write portion ((pid=31177).

 

Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

Hello,

The key part of this failure is "cannot add fragment to image database". Its getting failed while dealing with bpdbm.

Does this duplication part of SLP operation?

Is happening for specific backup images or all are failing?

If this duplication is part of SLP operation and happening for specific images.

We can try the workaround:

Remove that backupid from SLP operation and try manual duplication.

Example:
nbstlutil -cancel -backupid HQSQL2K16_1518700652

 

Regards,

Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

Yes the duplication is included in the SLP that is doing the AIR import.

I noticed that the duplication is not working with the Vmware SQL backup. Duplication of other VM backups is woking fine.

Here is the detailed status of the job thats failing.


Feb 20, 2019 1:35:34 PM - requesting resource  LCM_DXi141M12-tape
Feb 20, 2019 1:35:35 PM - Info nbrb (pid=4668) Limit has been reached for the logical resource LCM_DXi141M12-tape
Feb 20, 2019 2:26:57 PM - granted resource  LCM_DXi141M12-tape
Feb 20, 2019 2:26:57 PM - started process RUNCMD (pid=67692)
Feb 20, 2019 2:26:57 PM - requesting resource  DXi141M12-tape
Feb 20, 2019 2:26:57 PM - requesting resource  @aaaaf
Feb 20, 2019 2:26:57 PM - reserving resource @aaaaf
Feb 20, 2019 2:26:57 PM - begin Duplicate
Feb 20, 2019 2:26:57 PM - awaiting resource DXi141M12-tape. No drives are available.
Feb 20, 2019 2:26:58 PM - ended process 0 (pid=67692)
Feb 20, 2019 2:41:02 PM - Info bpduplicate (pid=67692) Suspend window close behavior is not supported for NDMP or NDMP direct copy
Feb 20, 2019 2:41:02 PM - Info bpduplicate (pid=67692) window close behavior: Continue processing the current image
Feb 20, 2019 2:41:02 PM - resource @aaaaf reserved
Feb 20, 2019 2:41:02 PM - granted resource  PR0033
Feb 20, 2019 2:41:02 PM - granted resource  IBM.ULTRIUM-TD5.006
Feb 20, 2019 2:41:02 PM - granted resource  DXi141M12-tape
Feb 20, 2019 2:41:02 PM - granted resource  MediaID=@aaaaf;DiskVolume=_PhysicalLSU;DiskPool=DXi141M12;Path=_PhysicalLSU;StorageServer=DXi141M12_147.110.195.141;MediaServer=sivls106
Feb 20, 2019 2:41:03 PM - Info bptm (pid=70196) start
Feb 20, 2019 2:41:03 PM - started process bptm (pid=70196)
Feb 20, 2019 2:41:03 PM - Info bptm (pid=70196) using 262144 data buffer size
Feb 20, 2019 2:41:03 PM - Info bptm (pid=70196) start backup
Feb 20, 2019 2:41:03 PM - Info bptm (pid=7346) start
Feb 20, 2019 2:41:03 PM - started process bptm (pid=7346)
Feb 20, 2019 2:41:03 PM - Info bptm (pid=7346) reading backup image
Feb 20, 2019 2:41:03 PM - Info bptm (pid=7346) using 1 data buffers
Feb 20, 2019 2:41:04 PM - begin reading
Feb 20, 2019 2:41:04 PM - Info bptm (pid=70196) INF - NDMP Direct Copy will be used.
Feb 20, 2019 2:41:04 PM - Info bptm (pid=70196) media id PR0033 mounted on drive index 12, drivepath /dev/alias/nst/F00225F049, drivename IBM.ULTRIUM-TD5.006, copy 2
Feb 20, 2019 2:41:04 PM - Info bptm (pid=70196) INF - Waiting for positioning of media id PR0033 on server sivls105 for writing.
Feb 20, 2019 2:54:52 PM - Info bptm (pid=7346) waited for empty buffer 14 times, delayed 31504 times
Feb 20, 2019 2:54:52 PM - end reading; read time: 0:13:48
Feb 20, 2019 2:54:52 PM - Info bptm (pid=70196) waited for full buffer 14 times, delayed 31712 times
Feb 20, 2019 2:55:10 PM - Error bptm (pid=70196) cannot add fragment to image database, error = no entity was found
Feb 20, 2019 2:55:33 PM - Info bptm (pid=70196) EXITING with status 227 <----------
Feb 20, 2019 2:58:02 PM - Error bptm (pid=7346) cannot connect to the writing side process for TIR duplication, Success
Feb 20, 2019 2:58:04 PM - Error bptm (pid=7346) media manager terminated by parent process
Feb 20, 2019 2:58:04 PM - Error bpduplicate (pid=67692) host sivls106 backup id HQSQL2K16_1519040108 read failed, media manager killed by signal (82).
Feb 20, 2019 2:58:04 PM - Error bpduplicate (pid=67692) host sivls105 backupid HQSQL2K16_1519040108 write failed, no entity was found (227).
Feb 20, 2019 2:58:04 PM - Error bpduplicate (pid=67692) Duplicate of backupid HQSQL2K16_1519040108 failed, no entity was found (227).
Feb 20, 2019 2:58:04 PM - Error bpduplicate (pid=67692) Status = no images were successfully processed.
Feb 20, 2019 2:58:04 PM - end Duplicate; elapsed time 0:31:07
no images were successfully processed  (191)

Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

I had similar case when I was AIRing backup images from 8.0 - or even 81 to 8.1.2 version... You need if your source and target domains are not equal in terms of version - that would be the first thing I would have done...

I was provided by VRTS CE with some manual procedure to have this working - but I ended up with upgrading source to match the destination...

Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

Yes duplication is part of the SLP operation.

I am only getting this error on VMWare SQL backups. The other VM snapshots backups are duplicating without issues.

Highlighted

Re: Cannot duplicate images using SLP. Image replicated using AIR

Exaclty the same issue .... I faced... Is your env running the same release?

Re: Cannot duplicate images using SLP. Image replicated using AIR

This could partly be an issue but some other VM backups are duplicating fine. Its only the VM SQL backups that are failing to duplicate. My source is on 7.7.2 and destination or target is on ver 8.1.1
Highlighted
Accepted Solution!

Re: Cannot duplicate images using SLP. Image replicated using AIR

Ngarart

What I can tell you ... I had the same issue. VM backup at source with ASC, replicated to remote domain and than duplicated to tape... last part of SLP was failing... here is what I did recieve from VRTS CE:
"DIAGNOSTIC STEPS/CAUSE:   
When application protected backup is being taken it creates a placeholder entry in dbm_main.dbm_image table but if the ASC job does not find application installed on client VM the placeholder entry is not cleaned up and this entry exists as a dependent of VM client backup image in the NBDB image database.

In AIR setup when this image is replicated to Target Master Server, the VM client backup image gets imported successfully at Target Master but the dependent image entry of image table is not imported as it is not a valid backup. At the time of duplication (on tape) at Target Master it checks for the dependent image as the VM backup image record having “hasdependents” set to 1 but it does not find any entry in dbm_main.dbm_imagedependency table, so duplication fails.

RESOLUTION SUMMARY:  
Issue fixed in 8.1, as the DR master is lower version then source master server which is not recommended.

"

View solution in original post