Active Full best practices?

[evilaedmin]

We are using a dedupe appliance and in the case of backup ingest everything is great. Synthetic fulls are fast, incrementals are fast and efficient, on-disk storage is efficient. I'm imagining a future where we'll never have to run an active full ever.

However in the days of tape it was always recommended to run active fulls periodically if nothing else as extra checks on the synthetic full processing logic or integrity of media.

Does anything similar exist for Veeam practices?

[Rick.Vanover]

There's no harm in doing that.

Properties of all job types can explicitly indicate to create an occasional active full backup. If you are doing zero active full backups now - you can modify the properties of a backup job to introduce that.

This is in the storage section of the backup wizard, advanced properties, there you can see the option to have active fulls on either monthly or weekly intervals.

[graemegant]

So if the best practice is to carry out an Active Full on a scheduled regular basis. What can we do about large servers that may take some time to carry out an active full, the Active Full of a very large server could take over a week.

We then would also have the issue of uploading the backup as a copy using Cloud Connect, which dependent on line speed can take weeks.

Is a combination of the Reverse Incremental and Storage-level corruption guard not sufficient methods of protection?

Or are there more advanced or other options to confirm the backup will restore?

Thanks
Graeme

[foggy]

Hi Graeme, please review this thread, should give you some thoughts. Thanks!