Hi Dave,
I can't comment on your error messages, but you asked how I schedule
snapdiff backups.
The schedule invokes a command on the client. Here is a shortened
version of the command file.
echo on
for /f "tokens=2-4 delims=/ " %%a in ('date /t') do (set
date=%%a-%%b-%%c)
echo %date%
net use <share-name>
... 12 more net use statements ...
dsmc i -snapdiff <share-name> -optfile=dsm-unix1.opt >>
c:\backuplogs\xxx\snapdiff-%date%.txt
... 12 more dsmc commands ...
dsmc i c: -optfile=dsm-unix1.opt >>
c:\backuplogs\vscan64\local-%date%.txt
The last line backs up the local file system.
Regards,
Bill Colwell
Draper Lab
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
David Bronder
Sent: Monday, June 27, 2011 4:24 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: snapdiff advice
Hi folks.
I'm trying to get snapdiff backups of our NetApp (OnTAP version 8.0.1P5)
working so I can move away from everybody's favorite NDMP backups...
So far, I'm not having much luck. I don't know whether I'm just Doing
It Wrong (tm) or if something else is going on. In particular, on both
Windows 2008 R2 (6.2.3.0) and RHEL 5.6 (6.2.2.0), I'm getting failures
like the following, depending on the dsmc invocation:
ANS1670E The file specification is not valid. Specify a valid Network
Appliance or N-Series NFS (AIX, Linux) or CIFS (Windows)
volume.
ANS2831E Incremental by snapshot difference cannot be performed on
'volume-name' as it is not a NetApp NFS or CIFS volume.
(These are shares at the root of full volumes, not Q-trees. I'm using a
CIFS share for the Windows client, and an NFS share for the Linux
client,
with the correct respective permission/security styles. TSM server is
still 5.5, but my understanding is that that should be OK.)
For those of you who have snapdiff working, could you share any examples
of how you're actually doing it? E.g., your dsmc invocation, how you're
mounting the share (must a Windows share be mapped to a drive letter?),
or anything relevant in the dsm.opt or dsm.sys (other than the requisite
testflags if using an older OnTAP). Or anything else you think is
useful
that the documentation left out.
(Also of interest would be how you're scheduling your snapdiff backups,
and how you have that coexisting with local filesystems on the client
running the snapdiff backups.)
Thanks,
=Dave
--
Hello World. David Bronder - Systems
Admin
Segmentation Fault ITS-EI, Univ. of
Iowa
Core dumped, disk trashed, quota filled, soda warm.
david-bronder AT uiowa DOT edu
|
