Need help with other JFrog products?
Using the latest JFrog Mission Control version? See the documentation here.
When setting up DR, or restoring your Master service, you will need to synchronize repositories between your Master and Target services:
- When setting up DR, you need to synchronize repositories once initialization is complete and you will be moving data from your Master to your Target service.
- When doing a Restore, you need to synchronize repositories after invoking Restore from the Actions menu and you will be moving data from your Target back to your Master service.
In order to synchronize repositories, whether executing DR or doing a Restore, you need to enable DR replications to allow replication of your repository data to take place. In both cases, this is done by selecting Enable DR Replications from the Actions menu.
Invoking automatic repository synch for DR
Invoking automatic repository synch for Restore
Depending on the amount of data in your filestore, this may be a resource intensive operation. Therefore, to avoid overloading your systems which may cause performance issues, Mission Control lets you manage synchronization of your repositories either manually or automatically.
After you select Enable DR Replications from the Actions menu, Mission Control manages replication indirectly by setting the cron expression that determines the timing of replication for each repository being replicated. If the amount of data in your system does not pose any performance then you can let this process proceed automatically to completion. If, however, your repositories contain a large amount of data, you might consider doing a manual sync.
You can invoke replication directly on the Artifactory service (the Master service when invoking DR, the Target service when doing a restore) in a gradual manner according to your IT policies and available bandwidth. For details, please refer to Replication in the Mission Control User Guide, or to Scheduling and Configuring Replication in the JFrog Artifactory User Guide. In this way, using your knowledge of how much data is hosted in each of your repositories, you may implement a gradual synchronization process with minimal or no impact to your system performance.
Even so, Mission Control avoids risking a performance hit and ensures that replications are not all invoked simultaneously. All replications are configured to run sequentially, at 5 minute intervals (default) to ensure that replication is initiated in a staggered manner to avoid a heavy load burst when data transfer begins. You can modify the time interval through the
drconfig.replication.cronIncrement parameter in your
At any time, the Repositories panel gives you a clear picture of the synchronization status of your repositories. Click any header in the Legend to view only those repositories in the selected status. For example, click Missing Repo to view those repositories that exist in the Master service but were missed in the Target service. The table in the Repositories panel displays the following information for both the Master and Target service:
|The repository key|
|The amount of storage occupied by files in the repository|
|The number of physical files in the repository|
|The number of folders in the repository|
|The number of items in the repository. Note that while a file is stored only once, it may appear as several items in different locations in the repository.|
This concludes the "Synchronize" step of setting up DR. For the next steps of setting up DR, please refer to Setting Up Disaster Recovery.