This issue has been solved.

does persistent fastresync need drl log?

Created: 24 Apr 2013 • Updated: 10 May 2013
Login to vote
0 0 Votes

hi,according to the documentation persistent fastresync seems to only need dco log. could i confirm that drl is not needed as well to survive a reboot?

regards,

ida 

Quick Look Solution

  DRL (Dirty region

 

DRL (Dirty region logging) is used to synchronize mirrors after a system crash (i.e DRL tracks in flight transactions so you only need to resync those writes that were occuring at the time of the system crash).  

DCO (Fast Mirror resync or persistent fastresync) is used to synchronize mirrors after an array crash (i.e DCO tracks writes that occur on one array while the other is down - or all paths to array are down) or to resync a snapshot

DCO version 2 (as from about 5.0 I think) has DRL functionality included with DCO so DRL is not required

DCO requires and Enterprise license, but DRL is available as part of Standard Licence

Mike

Filed Under

Comments

24
Apr
2013

i understand now my question

i understand now my question was incorrectly put. please ignore

mikebounds's picture
mikebounds
Trusted Advisor
Accredited
24
Apr
2013
SOLUTION

  DRL (Dirty region

 

DRL (Dirty region logging) is used to synchronize mirrors after a system crash (i.e DRL tracks in flight transactions so you only need to resync those writes that were occuring at the time of the system crash).  

DCO (Fast Mirror resync or persistent fastresync) is used to synchronize mirrors after an array crash (i.e DCO tracks writes that occur on one array while the other is down - or all paths to array are down) or to resync a snapshot

DCO version 2 (as from about 5.0 I think) has DRL functionality included with DCO so DRL is not required

DCO requires and Enterprise license, but DRL is available as part of Standard Licence

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has helped you, please vote or mark as solution