06-20-2014 06:44 AM
Hi all,
We have a duplication (basic disk) schedule that runs daily at 4am which copies data from a DSU to Tape. It's set in the following ways.
Multiple Copies
1 copy goes to Tape (onsite)
1 copy goes to Tape (offsite)
The company I work for will not invest in Vault. Therefore, this is the method I use.
for the most part, this work very well. Today, I ran out of scratch volumes in the offsite pool so, duplication succeeded only to onsite. My question is, is there a simple way (once i load scratch volumes) to ensure that I can get the data to the offsite pool? Will running a manual relocation work? I'm assuming it may not since the data has already moved to onsite pool sucesfully.
Thanks all for your help!
Solved! Go to Solution.
06-20-2014 09:02 AM
Since the local duplication succeeded this indicate to me that the inline setting "For each image if this copy fails" is set to continue and therefor you will properly need to run manual duplication to the images not copied to the offsite pool.
To ensure the data get to both pool you can set "fail all copies" instead of "continue"
Can you please verify the setting
This tech note is not really related but mention the lnline copy setting I mention.
http://www.symantec.com/docs/TECH153222
06-20-2014 09:02 AM
Since the local duplication succeeded this indicate to me that the inline setting "For each image if this copy fails" is set to continue and therefor you will properly need to run manual duplication to the images not copied to the offsite pool.
To ensure the data get to both pool you can set "fail all copies" instead of "continue"
Can you please verify the setting
This tech note is not really related but mention the lnline copy setting I mention.
http://www.symantec.com/docs/TECH153222
06-20-2014 09:38 AM
what Nicolai said
or
what is the output of this:
nbstlutil stlilist -image_incomplete -U
06-20-2014 10:52 AM
I do not get an output when I run tis command.
06-20-2014 10:57 AM
Great technote! Now, i have to determine if I want the entire job to fail, or continue as is. The problem with failing the whole job, is that data will not copy to onsite group, thus, the disk will fill up and in the end, backups will fail as a result of not enough scratch volumes in offsite pool.
Lets assume that I want to keep the setting so that the job continues on error, is there a simple way to rerun the duplication so that the images get copied to offsite pool?
06-20-2014 11:10 AM
06-20-2014 11:18 AM
That's what I was thinking, but, hoping to find an easier way. Thanks very much everyone.,
06-20-2014 11:28 AM
Amol is right - no SLP in use here.
This is a difficult one
I think you can do a bpimagelist for the job. Failed images are those that that does not have 2 copies (field 21 in bpimagelist) AND the primary copy is copy 2 (field 28).
Primary copy being 2 indicate duplicated images (DSSU) and only one copy indicate inline copy failed for those images.
http://www.symantec.com/docs/TECH5584
Is this clear speech ?
06-20-2014 12:59 PM