As a brief follow-up just in case some other poor sod runs into this same issue, SnapMirror to Tape was updated in ONTAP 8 and no longer accepts a trailing slash. So in summary, /vol/volume/ works in ONTAP 7, but ONTAP 8 requires /vol/volume (no trailing slash).
-Jonathan From: Martin, Jonathan Sent: Thursday, May 12, 2011 12:30 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: NetApp SMTAPE / NDMP on FAS3160 I’m trying to run an SMTAPE backup of a NetApp FAS3160 to a Windows 2003 NBU 6.5.6 Media. I previously had this configuration running on a FAS2040 that worked well, but the FAS3160 errors out with the following error: 5/12/2011 9:21:57 AM - Error ndmpagent(pid=1328) NDMP_LOG_ERROR 0 couldn't find destination 5/12/2011 9:21:57 AM - Error ndmpagent(pid=1328) NDMP backup failed, path = /vol/apps/ 5/12/2011 9:21:57 AM - Error bptm(pid=6956) none of the NDMP backups for client FAS3160 completed successfully 5/12/2011 9:21:58 AM - end writing; write time: 00:00:03 NDMP backup failure(99) If I configure my NDMP policy and change the client to the FAS2040, it runs. If I change the client to the FAS3160 it fails with the error above. If I remove “set type=smtape” from the selection list the backup runs fine as a standard NDMP backup. I’m writing to a DSSU on a media server, but I get similar errors writing to a fiber connected / SSO LTO3 tape drive. We’re also tried using the FQDNs for both the 2040 and 3160 to see if it makes a difference (it does not). NetApp support just asked me if we have the proper tier’d license for this 3160, which we haven’t purchased yet. But should that matter? I’ve got a NDMP license key installed, and I’m not aware that NetBackup has ever enforced individual client tier license keys. Anyone have any ideas? TIA, -Jonathan
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
