Forking for File System Replication Using DASH Copy
If the same source filer and the source MediaAgent is used as source in another replication, as soon as the source filer backup is complete for the parent replication, two auxiliary copy jobs will run in parallel to send the data to the respective MediaAgents. The data can then be restored to the destination filers. This is known as forking.
How It Works
- The source filer is backed up (as a UNC path) to the source MediaAgent.
- An auxiliary copy job copies the data from the source MediaAgent to the destination MediaAgent (Destination MediaAgent-1).
- A restore job restores the data from the destination MediaAgent (DMA-1) to the destination filer (Destination Filer-1).
- Immediately after the source filer is backed up, another auxiliary copy job is triggered that copies the data to a different destination MediaAgent (Destination MediaAgent-2).
- A restore job restores the data from this destination MediaAgent (DMA-2) to a different destination filer (Destination Filer-2).
- You cannot run or schedule the forked replications individually.
- A forked replication runs when the parent replication's restore job completes.
Last modified: 3/1/2018 6:40:15 PM