With 6.5.4, there was a EEB we needed to apply for duplicate to tape to
not use the wrong media server as the reader for the second scenario.
We would have a 50/50 chance of the remote media server being used to be
the reader for the image duplicating to tape.
EG: copy 2 in the NJ SLP being duplicated to copy 3.
some times we would have NJ media server copying the NY copy to to the
NY tape library for copy 3. Obviously NOT desirable across the WAN.
I think they rolled the fix into 6.5.5 and its definitely included with
7.0.1, I'm not sure which version you are using, but if it isn't 7.0.1
you may need an EEB fix.
On 3/5/2011 2:39 PM, bob944 wrote:
>> I will start using OST for my primary site (NY) and secondary (NJ)
>> with cross replication. I also want a third copy going to tape,
>> but I want the tape to be created at NY (for all backups, NY and
>> NJ). here is my question...
>>
>> With Storage Lifecycle, for my NJ backups, if I create a copy to
>> tape, then it will read from my primary (NJ), so it will kill my NY-
>> NJ link. Is there a way that I can tell it to use the second copy
>> that is now in NY? Or can I make the NY primary?
> Two SLPs should be all you need to force dups to work the way you
> want.
>
> NY
> backup to NY disk
>duplicate to NJ disk [from NY disk]
>duplicate to NY tape [from NY disk]
>
> NJ
> backup to NJ disk
>duplicate to NY disk [from NJ disk]
> duplicate to NY tape [from NY disk]
>
> See "Adding a hierarchical duplication destination" in the NetBackup
> Admin Guide. The indentation is the visual indicator of which backup,
> copy or duplication will be the source. A duplication at the same
> indentation level as multiple backup copies will use the primary copy.
> There's a good diagram in the guide.
>
>
>
> ___
> Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
