Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with recycle

Status
Not open for further replies.

ejgarcia

IS-IT--Management
May 28, 2003
72
US
Hello,

I have a client to be backed up to a tape with his index.
I mean Index and Data in a same tape.

I also have 2 days for browse and retent policies.

The problem is the index of this client has taken the browse policy of the Networker server and the volume is not expiring until index of the server expires.

Here is an mminfo output:

client name browse retent created size group pool
orioncluster W:\ 11/20/2003 11/20/2003 11/18/2003 10 GB Correo Correo
orioncluster W:\ 11/20/2003 11/20/2003 11/18/2003 58 GB Correo Correo
ciclope.caf.com index:eek:rioncluster 05/21/2004 05/21/2004 11/19/2003 19 KB Correo Correo

thanks you
 
What you're describing is actually expected behavior.

This is because the client index is on the backup server, not on the client. That is: the index backed up from and is owned by the backup server.

There are two ways around this:

1) create a separate pool, and in the saveset list for that pool, specify:

bootstrap
index:*

This will result in all client indexes and bootstrap to be saved onto this pool.

2) use the nsrmm command to manually change the browse and retention times of the client indexes to what you want. for example:

nsrmm -S (ssid) -w (browse date) -e (retention date)

You can use the mminfo command to determine the ssid's of the indexes savesets.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top