Hello Experts,
Here, in my infra ..
The first backup copy goes to appliance and then it is duplicated to another Netbackup appliance and post that 3rd copy is replicated for LTR.
what i am see here is backup failed(first copy) but it is still duplicating and replicating..Is this normal process??
Because i think, if the first copy is not completed then the 2nd copy(duplication) and 3rd copy(Replication) is niot started.
Please confirm.
Hi Dav1234
Secondary operations can only start after a successful first operation (i.e. the backup). I suspect what you may be seeing is a SLP backlog or if the "backup" comprises many parts - some part may have succeeded and so will continue to be processed by the SLP.
By a backup of many parts what I am referring to is a multi-streamed backup where only some streams fail which then the overall backup "fails" even though there have beeen successful streams.
SLP operate at the backup image level.
Hope that explains things
David
Hello David,
Understood, lets take example of RMAN backup wherein, 3 streams got failed and rest 8 streams completed successfully but this backup is of no use as i cant recover the database from this partial backup(as 3 streams got failed and parent stream failed)
so, is there any mechanism where 2nd copy(duplication) and 3rd copy(Replication) will only start if backup completed successfully(including parent stream).
Hi Dav1234
I'm not aware of any mechanism to achieve this (it would be nice I agree).
About the only way you could look to do this would be to delay the secondary operations until you have confirmed a successful backup. If the backup fails, you could then expire (force) the bits that did succeed (but are otherwise not very useful). It potentially could be scripted with some thought.
The SLP delay could be achieved by SLP windows, or increase the max size for SLP duplications or increase the time for force interval for small jobs, or even creating an SLP for the job that by default has secondary operations suspended.
Cheers
David
