Granular File Level Backup

[spilch]

Will the Veeam agent ever be able to do Granular File level backup?

At this point, Veeam needs to have a Full backup, when doing File level backups by utilizing VSS.
I get why, to ensure that none of the files are changed from that point on wards. But some of our clients just don't have the bandwidth for that and it would take days to complete.
If the network drops for whatever reason, veeam needs to start all over again. (I already know we can seed to another location like an external to kick start the full backup)

Another example would be if the clients hard disk didn't have enough space to keep a backup cache copy and then upload it.
We have clients where we don't manage their computers just the backups.

It would be nice if Veeam could just pick up where it left off again.

[Dima P.]

Hello Steven.

At this point, Veeam needs to have a Full backup, when doing File level backups by utilizing VSS.

In case of file level backup its a full run for selected files only. What amount of data customer is backing up?

It would be nice if Veeam could just pick up where it left off again.

You mean ability to resume the paused full backup?

[spilch]

Hi Dima,

This can be any amount, from 100 GB to 1TB of data.
Correct, or if the backup hit the backup Window. The backup would pause to continue during the next window.

[Dima P.]

Steven,

Thank you for the clarification!

This can be any amount, from 100 GB to 1TB of data.

With such amount of data Image level backup might be a better option. You can configure exclusions for volume level backup. If you choose file level backup mode, select volumes and unchecked undesired folders under such volume - it's still going to be am image level backup of entire volume with changed tracking on a block level.

[spilch]

Thanks Dima, but what about after the full backup is complete.
If an incremental stops due to the backup Window? Is it going to leave a vib file with what it was able to copy?
Or does it just scarp that and try again at the next window?

Also let's say the end client doesn't want a System Image or Volume level.
The have specific Files and Folders they want backed up. Say around 200 GB out of there 1TB of stuff.

[Dima P.]

Steven,

If an incremental stops due to the backup Window? Is it going to leave a vib file with what it was able to copy?

Incomplete restore point should remain at repository, it should be deleted during next job run.

Also let's say the end client doesn't want a System Image or Volume level.
The have specific Files and Folders they want backed up. Say around 200 GB out of there 1TB of stuff.

File level backup is still possible, but it does very simple changed block tracking based on file modification date. Whenever file is modified its version is included in incremental restore point.

[spilch]

Incomplete restore point should remain at repository, it should be deleted during next job run.

Will the VIB that is to be delete be useful in anyway for the new VIB?
As in will it check that VIB for any possible backed up files to carry over to the new VIB, since it is about to be deleted.

File level backup is still possible, but it does very simple changed block tracking based on file modification date. Whenever file is modified its version is included in incremental restore point.

That is fine and typically the way it works. Does File level have the ability to pause? Does File level have the ability to use incomplete VIB, considering it is just file level backup.

[Dima P.]

Will the VIB that is to be delete be useful in anyway for the new VIB?

Nope.

Does File level have the ability to pause? Does File level have the ability to use incomplete VIB, considering it is just file level backup.

Unfortunately there is not such feature, but I keep tracking this request.

[spilch]

Thanks Dima, thanks for explaining everything.