Best Strategy for SMB

[tuscani]

Hey all.. I am trying to determine the best backup method for our smaller clients with limited storage... Currently using Forward Incrementals with Weekly Synthetic Fulls on Sat as well as Transform previous full backup chains into rollbacks. The problem is, I never have enough space in the repository to hold the incrementals AND a second full before the existing full can be deleted.

[chrisdearden]

How about a more straight forward reverse incremental ?

[tuscani]

I will look into doing reverse incr.. Also, assuming "Transform previous full backup chains into rollbacks" is not checked, how many fulls will VEEAM keep?

[chrisdearden]

A reverse incremental only keeps a single full , which is the last run. All previous runs are turned to rollbacks.

[foggy]

assuming "Transform previous full backup chains into rollbacks" is not checked, how many fulls will VEEAM keep?

This depends on the retention settings you specify. For better understanding of the forward incremental mode, I suggest reviewing this thread.

[tuscani]

Thanks,.. seems like reverse incrementals are the way to go... are the restore points saved into the vrb files? If I have say 14 restore points how are the vrb files handled if each nightly job is a full? I thought I read they are injected into the VBK. I guess I am just trying to determine how many vrb files I would expect to see at any given time. Thanks!

[foggy]

If I have say 14 restore points how are the vrb files handled if each nightly job is a full? I thought I read they are injected into the VBK. I guess I am just trying to determine how many vrb files I would expect to see at any given time.

I suggest reviewing the corresponding section of the Veeam B&R user guide (p.28) for better understanding of what reversed incremental backup mode is. It is described in pretty good detail there. If you still have some questions after reading it, feel free to ask here.

[tuscani]

Thanks.. as always RTFM right!!

Is there any issues with backup and replication job running at the same time?

[Vitaliy S.]

Hi Justin,

If you're referring to having both backup and replication jobs targeted to the same source VM, then be aware that only one job will process VM at a time. If another job attempts to process a VM which is already being backed up, this VM will be placed in a waiting queue and will start processing only after the first job completes.

Thanks!

[foggy]

And here is the existing topic discussing this in more detail.

[tuscani]

Thanks again