I agree with Carsten (bingo) on this one. Also, check out the scheduled cloning 
feature(yes, it actually works through NMC too). You can actually set your 
retention on your AFTD's, to say 3 weeks, and then schedule cloning every week 
to another pool where you set max. number of savesets in the destination pool 
to be 1 and then the retention you really want.
This way, you can back up to an AFTD, clone to 2 tape pools(1 backup and 1 
clone) with regular intervals and the disk gets cleaned automagically. 

I use this at a couple of customer sites, and after the initial small config 
changes like making sure nothing collides etc. the systems just keeps on going 
and going.


/tony

-----Oprindelig meddelelse-----
Fra: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] På 
vegne af bingo
Sendt: 27. juni 2013 23:57
Til: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Emne: [Networker] AFTD device/nsrstage command with 8.0.1.5

An easier way would be ...
  - clone the save sets (setting the appropriate retention time for that pool, 
for example "10 years")
  - just let the save sets on AFTD expire after a shorter period, usually 
defined by the backups' retention policy This would avoid the scripted cleaning 
process.

BTW - the cloning process should tell you if there was an unsuccessful SS.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------