I have already discussed the advantages of using Windows Deduplication for Veeam Backup Repositories, and introduced the idea of using Replacador to replicate a windows deduplication volume.
Now we will set up Replacador on a windows deduplication volume that holds a Veeam Backup Repository and then run the replication process.
First browse to C:\LaserVault\Replacador and execute the ReplacadorConfig application.
We will use this to define a replication task for our source and destination volumes.
In this first example, we will replicate the volume to another volume on an external drive on the same server. The same process also runs across a network or the Internet. We will give an example of that later.
In the Replication Configuration Screen, press the Add Definition button and define a replication task.
In this case, we make the task name vmbackup, the machine name is ‘.’ ( a period means the current machine).
The volume Path is D:\ Normally a deduplication volume will be a drive letter on the current machine.
Don’t click OK yet.
Each replication needs at least one Destination. You can actually replicate to multiple destinations at once.
Click the Add Destination button and a new form opens to define the destination.
In this case we are replicating to another volume on the same server, so the Machine Name is ‘.’ for the local server again.
In the case of a different network location, this could be the VNC name of the target machine, or its IP address.
The username is the local username on the target machine plus a password. In this case we are using administrator, but you could use the system account or whatever is appropriate. The user needs to have sufficient authority to run Windows Deduplication garbage collection on the target machine.
The volume path is the local pathname on the target machine to the deduplication volume that will be a clone of the source deduplication volume.
The UNC path is the UNC version of this target deduplication volume, consisting of \\machinename\\volume
In the case where the target is on this local machine, just use the volume path again.
Now click OK, then OK, then OK, and your replication is configured.
The Replacador Manual explains how to run the Replacador Transfer program from the command line or thru the task scheduler, but since we are just testing, we will just click to execute the ReplacadorTransfer application. Since there is only one replication task defined and the default action of the application is to replicate, it will do exactly what we want.
When you first start the Replacador Transfer, it looks like nothing is happening. Actually Replacador transfer starts a deduplication job on the source volume to make sure that everything is ready for replication. If you have already deduplicated the volume, this part of the task will just take a minute or two.
Once the source volume is deduplicated, a command window will open and display the replication progress.
You can get a better idea what is going one by looking at the Task Manager performance screen.
Replication is really just a specialized copy task that takes very few CPU or memory resources. The limiting factor is the speed of reading, transmitting, and writing the data on the target volume.
The whole point to replication is to reduce the data traffic to the minimum needed to move the changes from the source volume to the destination volume. The first replication will be a large one, which is why it is sometimes a good idea to replicate to an external drive to seed the actual target server volume. After that, the replication process should be a small fraction of the original deduplication volume content, even for a new full backup.
When Replacador is done, you will have an exact copy of the deduplicated volume on the target server. Each time you replicate in the future, only the changed chunks and reparse points on the deduplicated volume will be sent to the target volume. The original files will not be reflated at any time in the process.