Backing up during Windows 2012 R2 Deduplication process ?

[albertwt]

People,

I'm still using Veeam Backup & Replication 8.0.0.2084, so Hopefully this is works better in V9.

What would happens for the VM backup when the File Server that is running Windows Server 2012 R2 currently running Data Deduplication ?

Does Veeam Backup can still back it up or it will be corrupted ?

Since I do not know how long the data deduplication time frame, it would be impossible for Veeam Backup job to wait until the process is finished.

[foggy]

Since Windows Data Deduplication is VSS-aware, you can backup this VM just fine. But don't expect backup file size reduction, since on the block level data is still there.

[veremin]

What would happens for the VM backup when the File Server that is running Windows Server 2012 R2 currently running Data Deduplication ?

And keep in mind that in this case VB&R server (or mount server) should be also running on Windows Server 2012 R2. Otherwise, problems during file level restore are expected. Thanks.

[albertwt]

Yes Vlad,

I've just upgraded it to Windows Server 2012 R2 as well.

[albertwt]

Since Windows Data Deduplication is VSS-aware, you can backup this VM just fine. But don't expect backup file size reduction, since on the block level data is still there.

Do I have to stop the VM backup job while the deduplication is still on going ?

[foggy]

I believe this is not required.

[skrause]

I have backed up VMs while the dedupe process was running (either started before, or during the job) and have had not had noticeable issues.

[albertwt]

Many thanks Steve and Alex for the clarification, so I guess I can just leave the backup job running as normal.

What about running SDelete within the VM after the deduplication process ? is that needed ?

[foggy]

As described in the thread mentioned above, it is required (as well as some additional steps) if you want to reduce backup file size.

[Gostev]

Actually, this is incorrect: SDelete is no longer required with v9, thanks to BitLooker.

[foggy]

The OP is still on v8, though.