First up, to answer Stan's question: My definition of 'safe' mostly means 'no
scanning' since these backups are almost 100% manual. We're almost at the
point where the 'save' and 'mminfo' commands have turned into an API!
We can, however, let the 'normal' index expire since saveset recovers are
doable (about 1-5 files in each backup). In fact I've done this once before,
marking the target offsite tapes as 'readonly + manual' and just replacing with
new ones.
[Yes, we do backup these indexes. But its a royal pain whenever its done since
trying to get 60+ client index backups to stay on one tape (and without 'media
alert' pages) is like trying to herd cats!]
Peter's suggestion below is the most likely route here for us (my suspicion
about how this license works was implying it, but wanted to see if anyone else
had taken the plunge first :) ). I'll see if I can run a quick test this
weekend on a client who's backup is going to totally expire soon.
Thanks All,
--TSK
Peter Viertel wrote:
> A client licnese is checked for and allocated to a client each time a
> backup is attempted. You can get the license back by deleting the client
> record... If you then recreate the client, no license will be allocated
> so long as you're only restoring from it..
>
> I have a process that goes like this:
>
> 1. use nsradmin to dump out all the client resources for a client that I
> want to retire. Eg:
>
> echo ". Type: NSR client; name: fred123;enabler in use: Yes\noption
> hidden\nprint" | nsradmin -i - >clientsavefile
>
> 2. check the dump is good, then delete that client.
>
> 3. recreate that client:
>
> nsradmin -i clientsavefile
>
>
> It's a bit more complex than this sometimes, eg if the host is gone from
> dns. or if you have multiple client records for the one client.. A lot
> of the info you dump out is readonly fields, but the important thing is
> to recreate the client with the same index, client-id, and retention
> info...
>
+----------------------------------------------------------------------
|This was sent by t.s.kimball AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
