StoreOnce Backup Copy Validation

[crazycommando]

Hi. In response to requiring a years worth of retention we have just finished our StoreOnce implementation.
Since we have everything we need for a great setup (3par, Fast local, 2 StoreOnce devices replicating), etc I'm keen to make sure I do everything perfectly.

Would anyone kindly give their thoughts as this setting:-

What we have:-
-Physical Server with Veeam 8 patch 1
-3Par San
-Local & remote StoreOnce setup and Share added to repository with correct settings

Backup job to Local disk (MSA2040)
-Daily
-Restore Points: 30 days
-Compression: Optimal

Backup Copy job
-Virtual machines - looking at the backup Job
-Target: local StoreOnce Cifs, Restore Points365 days
-GFS - 12 Monthly backups (might seem redundant but shouldn't matter with Storeonce?)
-Compression: Dedupe-friendly

-How does this look?
-Does it matter that the main job uses compression and the copy job is set to 'Dedupe-friendly'
-I read in this forum of other users being unhappy with backup copy jobs and StoreOnce but that was a few years ago. Any issues to watch out for.

Really appreciate anyone's feedbackup. THanks

[veremin]

-How does this look?

Looks solid.

-Does it matter that the main job uses compression and the copy job is set to 'Dedupe-friendly'

Nope, it doesn't.

Any issues to watch out for.

Be aware to specify gateway server closer to the device. Also, keep in mind that GFS points will be created not sooner than backup copy chain reaches 365 points and the oldest point is moved to the day specified for GFS restore point creation.

Thanks.

[foggy]

And also make sure you run the latest firmware on your StoreOnce devices.

[crazycommando]

Many thanks! Keep up the outstanding work!

[veremin]

You're welcome. Let's know, if you have other questions.

[crazycommando]

Yes. Would you mind clarifying this point:-
"Also, keep in mind that GFS points will be created not sooner than backup copy chain reaches 365 points and the oldest point is moved to the day specified for GFS restore point creation."

So the GFS (Keep the following restore points for archival purposes) doesn't kick in until after the 'Restore points to keep' finishes?

Would you suggest a more conventional approach such as:-
-Restore Points to keep: 30
-Monthly backup: 12

This would be fine for us.

[foggy]

So the GFS (Keep the following restore points for archival purposes) doesn't kick in until after the 'Restore points to keep' finishes?

Correct. The first GFS restore point will be created once the regular chain contains the specified number of restore points and the latest restore point in the chain (full backup) reaches the day specified for GFS restore point creation. So lowering the regular retention makes sense.

[crazycommando]

Got it. Many thanks!