Feature Request: Bitlooker for Replication

[mcrape]

Hi there - it would be awesome if we could exclude directories for replication jobs. I'm sure a lot of folks have something like a c:\temp directory that grows with SQL Backups, downloads, etc. Stuff that we likely don't need replicated. I'm not sure, but does the replication job currently skip files such as the memory dumps, paging, and hibernation files (if they exist)?

[jmmarton]

As another way to think about it, why not use BitLooker to exclude those folders from the backup, then in the properties of the replication job specify backup files rather than production storage as the source?

Joe

[PTide]

As another way to think about it, why not use BitLooker to exclude those folders from the backup, then in the properties of the replication job specify backup files rather than production storage as the source?

In case you wanted your replication to occur evey X minutes that approach would require you to backup your VM every X minutes, which is not very convenient I believe.

but does the replication job currently skip files such as the memory dumps, paging, and hibernation files (if they exist)?

Yes, there is an option to exclude swap file blocks and deleted file blocks in "Advanced Settings". Please see this article for more info.

[mcrape]

With regards to the first point, yes, exactly - my replication jobs aren't built from backups. In some instances I may have a replication job for a VM that is not backed up (odd, I know).

[HannesK]

+1 for Bitlooker for replication

[Gostev]

@Hannes but we have it already?

[HannesK]

my fault... I was missing "exclude deleted file blocks" but I simply did not read correct... forget my request, thanks

[veremin]

Exclude deleted file blocks functionality is also there. Thanks.