Best Settings backup job for big file servers

[mrainbow]

Hi all!
how best to set up file server backup

the main problem is how to make sure that, for example, after 30 days, data that is no longer on the file server is also deleted in a full backup

that is, if I have directories "1", "2", "3" on the reserved disk
during the month, in an infinitely incremental mode, points are created.
but after 30 days, if I delete the "2" folder, it will also be deleted from the full backup.

Is it possible to do with Veeam B&R?

data on disks that I back up, 6TB+

[mrainbow]

Can setting "Remove deleted data items after" and 'Defragment and compact full backup file" help me?

[mrainbow]

Understood.
yes, that's how it works.

Delete deleted data after n-days
and defragmenting and compacting the image.

[rennerstefan]

Hi,

the "Remove deleted items data after" really if for objects that have been deleted or excluded from a job but there are already backups existing. It tells Veeam to delete those after n days once they are removed or excluded from the job. See: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

The Compact may help here better but be sure you know about the process as it requires some resources:
"During the compact operation, Veeam Backup & Replication creates a new empty file and copies to it data blocks from the full backup file. As a result, the full backup file gets defragmented and the speed of reading and writing from/to the backup file increases."
See: https://helpcenter.veeam.com/docs/backu ... ml?ver=110

[HannesK]

Hello,

but after 30 days, if I delete the "2" folder, it will also be deleted from the full backup.

if you delete data today with a 30 days retention, then the data will be deleted after 30 days. That's how backup products / retention works in general. No need to do anything.

that is, if my full image takes 8TB - and the data in it is 5TB - does that mean I need to have 5TB+ free on the disk?

normally not (assuming that you use REFS / XFS). If you use other file systems or NAS shares as repository, then yes, it takes up temporary space.

Best regards,
Hannes

[mrainbow]

I probably misunderstood. sorry for stupidity)

example:
there is a disk on the server, 10TB (disk1)
data on it 8TB

1) the first full backup of this disk is taking place on the veam server

2) after some time, the data on this disk (disk1) becomes 6TB (we deleted some of the folders, intentionally)

3) on the veam server, in the job on the backup of this disk, the retention policy is set for 30 days.

4) disk image full backup, 8TB on the veam server
although disk1 on the data server is already at 6

with all the possible number of points, and defragmentation, those folders that were deleted from the client, from disk1, cannot be deleted from the full backup, right?

is this not configurable?

I am deleting data on the client server, not the disk on the Veeam in the job

[mrainbow]

Hello,

if you delete data today with a 30 days retention, then the data will be deleted after 30 days. That's how backup products / retention works in general. No need to do anything.


normally not (assuming that you use REFS / XFS). If you use other file systems or NAS shares as repository, then yes, it takes up temporary space.

Best regards,
Hannes

if at the time of creating the first full backup, the folder "2" existed, but after a couple of days, it was deleted,

then after 30 days or points, with the Create a full synthetic backup or defragmentation option enabled, this folder "2" will be deleted from the 1st full backup?

[rennerstefan]

The whole topic depends not only on the deletion of the data on the server but also if “folder 2” was completely removed from the file system including marking the storage blocks as free. As your question is around image base backup keep in mind veeam reads blocks, not the actual “folder 2” or content of the vmdk. With that said the free space will only be reflected once it is not handed over to veeam anymore by the vddk. After that a compact may make sense to see that free space also reflected in the backup file size.
Hope that clarifies it a bit.