Cross-cluster resource synchronization

On this page

Teamwork Cloud offers a one-way resource synchronization functionality allowing you to move resources from one Teamwork Cloud server to another and periodically update them. This is a convenient way to collaborate with disconnected teams or departments and share not only resources but their entire history as well. Therefore you can use resource synchronization as an alternative to exchanging .mdzip files and then updating server projects with local changes. In addition, you can perform a one-time synchronization operation to offload resources to another server for archiving.

Using resource synchronization for collaborating

You can periodically synchronize Teamwork Cloud resources from the source server to the target server so that other users could use synchronized projects in other projects stored on the target server.

Setting up a periodic synchronization operation to share resources that can be reused on the target server.

To use resource sync for collaboration between disconnected Teamwork Cloud sites

1. On the target Teamwork Cloud server, create a remote resource configuration to synchronize selected resources from the source to the target server:
   1. Connect to the source Teamwork Cloud server and select the resources and/or categories you want to synchronize.
   2. Select the category on the target Teamwork Cloud server where you want the synced resources to be stored.
   3. Select one of the following synchronization triggers: on every commit, on commit with a specific tag, or manual synchronization
2. Use the synchronized resources in your projects stored on the target server.
3. Update synchronized resources when new project versions become available.

Using resource synchronization for resource offloading

If there are dormant recourses in your Teamwork Cloud server, you can move them to another server for archiving to free up space on the main server (e.g., production server).

Setting up a one-time synchronization operation to move resources to another server.

To use resource sync for moving resources to another Teamwork Cloud server

1. On the target Teamwork Cloud server (e.g., archive server), create a remote resource configuration for a single time synchronization operation:
   1. Connect to the source Teamwork Cloud server (e.g., production server) and select the resources and/or categories you want to synchronize.
   2. Select the category on the target Teamwork Cloud server where you want the synced resources to be stored.
   3. Select one the On every new commit synchronization trigger.
2. Use Data Manager to remove the synced resources from the source server to free up server space.
3. Remove the remote resource configuration created in step 1.

Removing the read-only flag from offloaded resources

If you have used resource synchronization to offload resources to a remote server, these resources are read-only and you can no longer edit them. However, there is a way to remove the read-only flag from synchronized resources and make them active again.

To remove the read-only flag from offloaded resources

• Run Data Manager and execute the following command:

  -rrof, --remove-read-only-flag <-resourceID=<value1>,<value2> --categoryID=<value1>,<value2>>

  Example

  datamanager -rrof --resourceID=a4c498c9-f125-453c-b9cb-3d5a6e675714 --categoryID=a1d569ea-fe6a-402f-8a25-aef6b932de48