Video Screencast Help

does persistent fastresync need drl log?

Created: 24 Apr 2013 • Updated: 10 May 2013 | 2 comments
This issue has been solved. See solution.

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?



Operating Systems:
Discussion Filed Under:

Comments 2 CommentsJump to latest comment

IdaWong's picture

i understand now my question was incorrectly put. please ignore

mikebounds's picture

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


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

If this post has answered your question then please click on "Mark as solution" link below