DonT2
2 Bronze

Timefinder/clone on a source device that is already R1

We have a meta that is setup for SRDF/A replication. They want me to create a local Timefinder/clone session for that same device. Is this possible?
11 Replies
xe2sdc
5 Tungsten

Re: Timefinder/clone on a source device that is already R1

Yes.

I'd say "absolutely" :D
0 Kudos
nicoroy123
2 Iron

Re: Timefinder/clone on a source device that is already R1

Both R1 and R2 can be the source of a TimeFinder/Clone session.
Don't forget to add the -TGT switch when you add the target devices to the SRDF groups...
0 Kudos
DonT2
2 Bronze

Re: Timefinder/clone on a source device that is already R1

[Don't forget to add the -TGT switch when you add the target devices to the SRDF groups...]

Shouldn't I create a new group for the local TF/clone session instead of using the existing RDF1 group used for remote replication?
0 Kudos
xe2sdc
5 Tungsten

Re: Timefinder/clone on a source device that is already R1

You have options.
Default (good old) behaviour of S.E. will forbid sharing the same STD in different DGs.
With recent (6.5.3) S.E. you can change an option and put same STD in different DGs.
DonT2
2 Bronze

Re: Timefinder/clone on a source device that is already R1

So your recommendation is to add the TGT devices to the existing RDF group and run symclone session commands against the local SRC and TGT devices?

Could this affect the SRDF/A replication if we plan to establish the local clone every 15 mins?
0 Kudos
xe2sdc
5 Tungsten

Re: Timefinder/clone on a source device that is already R1

You can choose. The good old way (put everything in a single DG) will work flawless and won't affect your replication. SRDF/A switches cycles regardless of what your host is doing.
A DG is simply a container, a cheap and easy way of telling the storage what devices you are trying to clone (and their corresponding targets, of course).
DonT2
2 Bronze

Re: Timefinder/clone on a source device that is already R1

So then with all TF/clone and RDF devices in one group, could the symrdf commands (such as disable and establish) affect the TF sessions? Or conversely, could the symclone commands the affect the SRDF replication?
0 Kudos
dynamox
7 Thorium

Re: Timefinder/clone on a source device that is already R1

if RDF and TF commands run at the same time they might bump into each other just from symcli perspective, one might get error that symapi is locked or something like that. You can build some logic in your script to sleep for 10 seconds and retry. From RDF and TF functionality i don't see how they could conflict with each other, you are using clones so there should not be any mirror positions issues or anything like that. SRDF performance might suffer if you are RDFing and cloning at the same time. I don't know if one takes precedence over another.
0 Kudos
DonT2
2 Bronze

Re: Timefinder/clone on a source device that is already R1

Thank you all for your expertise.
0 Kudos