The best way to do this is to create a special snapshot specifically for the backup, then delete it when the backup completes. This avoids the problem of the snapshot being changed out from under you. And this can all be automated with scripts. See Paul Benn's message for a pointer to a description of how to do this.
Mark Muhlestein -- mmm@netapp.com
-----Original Message----- From: Patrick.Day.B@bayer.com Patrick.Day.B@bayer.com To: - (052)toasters(a)mathworks.com toasters@mathworks.com; - (052)tmerrill(a)mathworks.com tmerrill@mathworks.com Date: Monday, March 01, 1999 10:48 AM Subject: Re: nightly.1 busy: snapshot rollovers not happening
I ran across this same problem when i shared the Nightly.0 for backup purposes. When the nightly.0 rolls over to the Nightly.1, the CIFS share
keeps
track and actually keeps the share mapped to nightly.1. (same thing next
night
when it rolls over to nightly.3). I posted the problem a few weeks ago
and the
only "solution" anyone could come up with was running an rsh command to
stop
and recreate the share every time the backup runs. I opted to forget the snapshot directory backup and go with a live backup of the C$\ share.