On Wed, Jun 28, 2006 at 03:52:43PM +0200, Manel Rodero wrote:
> So the idea is create an script similar to this:
> 
> - The day of the special backup execute an script that
> - Lists all the clients in the normal group and duplicate them chaging the
> retention/browse policy and the backup group
> - Do the backup (start the group)
> - When the backup finishes, erase these special clients (the data in the
> tapes will not be erased because of its 1 year retention policy)

As was mentioned, it's probably easiest (since the only thing you're
changing/duplicating in the special instance of the client is the
browse/retention time,) to use the normal backup/configuration instance
and use mminfo to modify the retention for those savesets.

I deal with having two instances per client here (one for daily backups,
another for monthly/quarterly archives) and it has it quirks, but it
works.


> If we need to recover data from these special backups (rarely), we will
> recreate the necessary client and recover its data.

Multiple instances aren't actually different clients.  If you turn on
the detailed view, you'll see they have the same client id that
Networker uses to associate backup to client.  As long as at least one
client instance in your environment exists with the client id of the
saveset you want to restore, you're fine.  If you ever delete a client
(all configuration instances) and later want to restore some data, save
yourself some effort by recording the client id before deleting all the
client instances.  Later, when you need to do a restore, recreate the
client with the same client id and the restore should work fine.

Dave

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
wit 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