So I suggested to EMC that "Or enumerating the folders of E: explicitly,
rather than
using saveset ALL?". They agreed, since it seems that VSS is using the
same drive as AFTD is, and so there's not enough room for the snapshot
*and* the FULL save to AFTD device.
(makes me wonder how this process can work on clients with no large AFTD
drive to write snapshots to ...)
Anyway, I set up one job with a saveset ALL, but a directive to skip
certain named folders on the main storage drive
And an hour later, I will run a job that backs up *only* those named
folders that were skipped earlier in the night.
The combination of the 2 jobs should provide me with a backup of
everything on the server.
That should (hopefully) cut down on snapshot size, and I won't run out of
disk space on the AFTD disk, and the backup (including DISASTER_RECOVERY:
saveset) should complete.
I hope. :-)
--
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel: 215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on
08/12/2011 08:58:31 AM:
> From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Date: 08/12/2011 08:59 AM
> Subject: [Networker] A bit OT: VSS and Win2008 R2 and NW 7.6.2
> Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
>
> I've started getting errors from VSS on a Win2008 R2 server that is a NW
> 7.6.2 storage node. And the last couple nights, it has been partially
> failing (partially meaning that some files weren't backed up, but most
> were).
>
> (I've never changed any settings for VSS, as Networker handles all that)
>
> First thing I see, in SYSTEM log of the client:
> (E: is the main data drive, and X: is the AFTD disk that Networker
writes
> to)
>
> ----------------------
> Event 33, source: volsnap:
> The oldest shadow copy of volume E: was deleted to keep disk space usage
> for shadow copies of volume E: below the user defined limit.
>
> Event 24, source: volsnap:
> There was insufficient disk space on volume X: to grow the shadow copy
> storage for shadow copies of E:. As a result of this failure all shadow
> copies of volume E: are at risk of being deleted.
>
> Event 35, source volsnap:
> The shadow copies of volume E: were aborted because the shadow copy
> storage failed to grow.
> --------------------
>
> And then Networker reports that some files weren't backed up.
>
> E: Used size = 665G
> X: Free space = 609G (this drive keeps 2 days worth of backups)
>
> So I guess what I need to do is for VSS to not use so much space for
it's
> snapshots, so it doesn't run out of room. I don't fully understand how
VSS
> figures into this (yes, I've read the VSS Guide from EMC, no I still
don't
> understand it). It sounds like what's happening is that the snapshot
> doesn't have enough room to grow to the size it wants to be. So do I
need
> to tell VSS to make the snapshots smaller, so it won't need such a big
> block of space at one time for each snapshot?
>
> You can't turn off VSS in Win 2008 R2 backups in Networker, I'm told, so
> that unfortunately is not an option.
>
> Or should I be changing the saveset definitions, to backup C: and E: as
> separate jobs? Or enumerating the folders of E: explicitly, rather than
> using saveset ALL?
>
> I'm confused and lost. Anybody have a guide post to get me back on
track?
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu
> and type "signoff networker" in the body of the email. Please write
> to networker-request AT listserv.temple DOT edu if you have any problems
> with this list. You can access the archives at http://
> listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
