@carsten

Maybe I didn't specify what I meant: If it comes to a recovery after the 21 
days, you will only have the one clone of the saveset, so the behavior you 
mention will be irrelevant. And up until 21 days, NW will use the one with the 
lowest timestamp, as you correctly mention.

/tony

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

@tony

Out of my experience your statement: 
  "And as a side note, remember that a clone is exactly that, a clone. This 
means that NW doesn't care the least whether you point it to a clone to do the 
recover from or the original saveset." 
is not really correct. At least not when NW selects the recover media.

NW will in fact always go for the original backup instance - precisely the one 
with the lowest clone ID timestamp. This makes sense as otherwise he might 
potentially grab the slower tape. It is a pain if you set the location for a 
backup tape media to another value than your jukebox' name as NW will not even 
choose another media - even if it is inside the autochanger - unless you will 
force him to do so. And you can achieve that in several ways:
  - mark the original backup save set 'suspect'
  - for save set restores: specifiy the save set instance (-S ssid/cloneid)

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