Did you backup each filespace sequentially or all at once? I.E.
serial backup node nas /fs1 mode=full wait=yes backup node nas /fs2 mode=full wait=yes backup node nas /fs3 mode=full wait=yes backup node nas /fs4 mode=full wait=yes backup node nas /fs5 mode=full wait=yes backup node nas /fs6 mode=full wait=yes backup node nas /fs7 mode=full wait=yes backup node nas /fs8 mode=full wait=yes backup node nas /fs9 mode=full wait=yes backup node nas /fs10 mode=full wait=yes backup node nas /fs11 mode=full wait=yes backup node nas /fs12 mode=full wait=yes backup node nas /fs13 mode=full wait=yes backup node nas /fs14 mode=full wait=yes backup node nas /fs15 mode=full wait=yes backup node nas /fs16 mode=full wait=yes -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of James R Owen Sent: Thursday, November 13, 2008 5:48 PM To: ADSM-L@VM.MARIST.EDU Subject: ?how to force NDMP LAN-free backups to fill one tape before writing on another? I am trying to force NDMP LAN-free backups to keep the same tape mounted and serially reuse it when a NetApp filer needs to write multiple backups. We have just implemented our first NDMP LAN-free backups w/ TSM v5.5.1.1, w/ a single NetApp filer backing up 16 VirtualFS from nightly snapshots, e.g., DEFine VIRTUALFSmapping netapp-01 /x.snap /vol/volx /.snapshot/nightly.0 I was disappointed to find that DEVType=NAS requires MOUNTRetention=0: e.g., DEFine DEVclass LTO3N LIBRary=bec3584 DEVType=NAS ESTCAPacity=800G - MOUNTRetention=0 MOUNTWait=5 [that forces a tape dismount after each NDMP backup, right?] We use LTO1 scratch tapes in our 3584 library so I defined 10 * LTO3 volumes into our new BackupL3N STGpool: DEFine STGpool BackupL3N LTO3N POoltype=PRimary DATAFOrmat=NETAPPDump - COLlocate=Group [=default setting] MAXSCRatch=0 The filer wrote NDMP backups on all 10 tapes, so I did MOVE DATA's to collocate all of the backups back onto a single tape and tried: UPDate STGpool BackupL3N COLlocate=Node Same results: NDMP backups on all 10 tapes again! Help? [or is that just how NDMP backups work?] -- [EMAIL PROTECTED] (203.432.6693)