Expirationdate on W2KCluster-Savesets too long

[marcoesser]

Hello All,

I´m using NetWorker 6.1.2.Build.340 Network/15 on WindowsNT4.0.

Now we became a new W2K-Cluster to Backup. And I´ve some trouble with it:

The browse and retentionpolicy for the daily backups is set to 5 weeks. The policy for weekly full is set to 5 weeks, too. The monthly fullbackups should stay for 12 month and every quarter year we will make a backup with a retentionpolicy of 3 years.

So far so good, but the policies will not work with this new cluster. Every Saveset from the Cluster will get an Expirationdate which is 3 years from now.

I´ve an extrapool for the indexes, so that this is not the source for the problem.

I have no idea, where to start the search for the problem.
Can somebody help me out of that ?

marco

 

[wallace88]

The browse and retention policies are defined at the client resource level.

The cluster's savesets have browse and retention of 3 years? Are you referring to the physical node clients, virtual node clients, or both?


You need to verify these settings in your client resource for your physical and virtual nodes of your cluster.

 

[marcoesser]

wallace88 write: The cluster's savesets have browse and retention of 3 years? Are you referring to the physical node clients, virtual node clients, or both?


I´ve the problem with both, the physical and virtual node clients. Only some of the client resources have a browse and retention of 3 years, but all savesets from the cluster are treated, like they where saved with this browse and retention time.

Marco