This post is more than 5 years old
1 Rookie
•
12 Posts
0
1732
July 23rd, 2013 22:00
VMax SRDF initial establish
In our environment, we have VMax and DMX4 (and also VNX etc)
Currently, when we receive a storage request requiring SRDF, we do the following (e.g. 1TB required on both sides):
1) Create devices on both sides (1TB each)
2) Run symrdf command to create the pair
3) Establish the SRDF link (this copies 1TB of data across DWDM)
4) Present the device to the host
5) Done
However the copying of the 1TB data during the establish is useless, as the device has not yet been presented to the host, and contains no useful information.
We would like to avoid this initial copy across the DWDM.
Is there any way to "zero" the disk, or some way to say "only copy the changes after SRDF established"? How is the community doing this sort of changes right now?
Thanks,
Kelvin


PedalHarder
4 Apprentice
•
465 Posts
0
July 23rd, 2013 22:00
VMAX has a feature for SRDF initial establish when the track has never been written by a host it will not get copied in the initial sync. You need VMAX at each end of the SRDF link for the feature.
Anonymous User
1 Rookie
•
12 Posts
0
July 23rd, 2013 22:00
Good to know, thanks!
Any solution for the DMX4 also?
sauravrohilla
859 Posts
1
July 23rd, 2013 22:00
As far as I remember 5876 code has this feature that NWBH tracks are not copied to the R2 during first establish.
regards,
Saurabh
Anonymous User
1 Rookie
•
12 Posts
0
July 23rd, 2013 22:00
That was fast, thanks!
Do you have the specific flag or is this automatic?
PedalHarder
4 Apprentice
•
465 Posts
0
July 23rd, 2013 22:00
It's automatic. No host / admin intervention required :-)
A-J1
1 Rookie
•
49 Posts
1
July 24th, 2013 05:00
5876 code marks all unwritten tracks as NWBH (Not written by host), These tracks are not copied during SRDF establish but the R2 vmax just IVTOC'c the track as it know there is no data on these tracks, As pointed out by @Jasonc you need vmax on both sides for this.