Extended Copy Precedence

[mrfokker]

I have roughly 15 client computers backing up to a single disk storage policy. I have an aux policy that is set first weekend every month backup a copy to retain for 548 days for my extended copys. This has been working fine for the most part. On occasion however tapes on random days during the month are flagged as extended that do not follow the policy I set up in my aux copy. The problem doesn't seem too rampant usually one or two additional tape per month. Usually I look at the contents and its nothing I can be without such as system states from a month ago. I have made sure all my clients are associated to the storage policy. Any help as always is appreciated.

 

[birky]

Hi mrfokker

you could always create a new SP and have seperate subclients for your system states...seperate it away from your actual data backups..how long do you need to retain sys states realisticaly?



Birky
CommVault Certified Engineer

 

[Cyklops]

Birky is right suggesting separate policies for System State backups. When you run a 'normal' Full versus Incremental schedule policy and all jobs succeed like they should the file system backup will flag the first weekend (full) backup as 'first of time period' with the extended (E) copy. However as System State backups are always full backups it is possible that an earlier backup for this machine (which was an Incremental for the File System) will be flagged as Extended for the System State. Separate SP's is a way to resolve this.

regards

 

[mrfokker]

Thanks for the info. I will make the necessary changes to my storage policies.