Thanks, Alain!
For the CIFS case, it looks like I was missing the "net use" step; doing
that first made the backup work (we already had the NetApp configured
with a user with correct capabilities and the password for that user was
already set on the TSM client side).
I'm still having no luck with snapdiff of NFS from a Linux client. The
share is mounted (exported read/write with root access), I'm using the
same NetApp account for the API connection (and the password is set at
the client), but the backup fails with the same errors as I originally
described. I was missing the TIVsm-BAhdw RPM at first, but correcting
that made no difference.
(My NFS testing is on a filer running 7.3.2, but I'm not worried about
Unicode support at this point; I just want to get snapdiff to work at
all. Neither the SNAPDIFFNAMEFILTEROFF nor SNAPDIFFONTAPFAP testflags
had any effect on the attempts, either.)
=Dave
Alain Richard wrote:
>
> We are using snapdiff for almost a year. We use some trick's found in
> the forum.
>
> First, mount your share before starting the backup " net use \\dffdg\fgdgj"
> Second, If you talking to a NAS like a Netapp, you need to have http
> access For TSM : httpd.admin.enable on, and use command tsm> "set
> password -type=filer sdfggd $logname".
>
> Be sure to have at least tsm6.2.2 client and Ontap 7.3.3 if you want
> the Unicode work!
> Don't forget to do full scan at least once a month just in case it
> misses some files.
>
> Alain
>
> -----Message d'origine-----
> De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part
> de David Bronder
> Envoyé : 27 juin 2011 16:24
> À : ADSM-L AT VM.MARIST DOT EDU
> Objet : [ADSM-L] 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
|
