<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">Jonathan,<div><br></div><div>First it must be understood the snap is either at the filesystems or fileset, and more importantly is not an application level backup. This is a huge difference to say Protects many application integrations like exchange, databases, etc.</div><div><br></div><div>With that understood the approach is similar to what others are doing. Just understand the restrictions.<br><br><div id="AppleMailSignature"><div>Lloyd Dean</div><div>IBM</div><div>Software Storage Architect/Specialist</div><div>Communication & CSI Heartland</div><div>Email: <a href="mailto:LloydDean@us.ibm.com">LloydDean@us.ibm.com</a></div><div>Phone: (720) 395-1246</div></div><div><br>On May 8, 2018, at 8:44 AM, Fosburgh,Jonathan <<a href="mailto:jfosburg@mdanderson.org">jfosburg@mdanderson.org</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt">We are looking at standing up some new filesystems and management would like us to investigate alternative options to Scale+Protect. In particular, they are interested in the following:<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt">Replicate to a remote filesystem (I assume this is best done via AFM).<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt">Take periodic (probably daily) snapshots at the remote site.<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt">The thought here is that this gives us the ability to restore data more quickly than we could with tape and also gives us a DR system in the event of a failure at the primary site. Does anyone have experience
with this kind of setup? I know this is a solution that will require a fair amount of scripting and some cron jobs, both of which will introduce a level of human error. Are there any other gotchas we should be aware of?<o:p></o:p></span></p></div><p class="MsoNormal">The information contained in this e-mail message may be
privileged, confidential, and/or protected from disclosure. This e-mail message
may contain protected health information (PHI); dissemination of PHI should
comply with applicable federal and state laws. If you are not the intended recipient,
or an authorized representative of the intended recipient, any further review,
disclosure, use, dissemination, distribution, or copying of this message or any
attachment (or the information contained therein) is strictly prohibited. If
you think that you have received this e-mail message in error, please notify
the sender by return e-mail and delete all references to it and its contents
from your systems.<o:p></o:p></p>
</div></blockquote></div><BR>
</body></html>