Spool Copy Question

[JG5]

All of my magnetic primary storage policies have a synchronous aux copy to secondary disk. The primary copy is set for 1 week retention, and the secondary for 28 days. If I manually prune the only full copy from a primary storage policy, the next backup will be forced full - makes sense.

My question is this - if I configure the primary copy as a spool copy, the backup job will run, and once the aux copy successfully completes it will be pruned from the primary copy during the next data aging job. Will the subsequent incremental backup be forced full since the last full is no longer contained in the primary copy as a result of the spool copy retention settings?

Thanks.

 

[rodneysmith]

No as the data is still available on the secondary copy, since Simpana was the one to age off the first copy it knows that it is still on the second version which it flags as the "primary copy".
I have customers that have spool copies set up and the incrementals run fine and don’t get converted to full’s
rgds rod

 

[JG5]

I actually ran a few tests and validated just what you said, but forgot to post back until I got the notification.

Thanks for the reply.