What’s data transfer?
Cross-server transfer involves downloading an entity from the source server and then uploading this file to the target server to create a new remote copy.
Depending on the export method used, the dump file may retain information about its origin. This allows for one-way synchronisation, ensuring that any changes made to the original entity are automatically applied to the synchronised remote entity on the target server.
Important! Synchronisation overrides all changes made to the remote entity. Therefore, synchronised entities on the target server have limited editing capabilities to maintain consistency with the source.
Only the entity's owner can export it for transfer. However, it can be uploaded to a remote server under a different account with the necessary roles.
To use this functionality, user accounts on both servers must have the Syndicate Manager role and the appropriate Creator role for the entity type (e.g., Dashboard Creator for dashboards, Database Creator for databases, etc.).
Why you may need cross-server data transfer
Although it is possible to dump and restore entities within the same server, we recommend using the standard cloning and sharing functionality for a more streamlined approach to managing access to your entities on the same instance of DataTile
Cross-server data transfer is a distribution mechanism designed for scenarios where data and reports are produced on one DataTile server and must be delivered to one or more other servers. This separation may be necessary due to the following:
Staged quality checks
Security restrictions
Mass distribution
Here are the primary use cases for cross-server distribution:
Research delivery
Research suppliers might lack access to high-stakes clients' infrastructure. By leveraging this feature, they can securely produce research deliverables like databases, dashboards, and reports and effortlessly transfer them to the client's DataTile server.
This ensures the accurate and seamless delivery of new waves, reports, and dashboards without disrupting user tasks. Pre-release staging and quality checks prevent errors and eliminate the need for manual versioning of deliverables.
Syndicated studies
Centrally maintained syndicated databases can automatically be populated to the DataTile servers belonging to various customers.
This protects the intellectual property rights of the data owner by ensuring the level and scope of access to the distributed database without the possibility of downloading raw data. At the same time, it gives data users the flexibility to blend syndicated data with their own research, creating comprehensive reports with deeper insights.
Additionally, it drastically reduces the cost of delivery and simplifies support by providing the support team with an identical client environment without the need to access their server.
Exporting an Entity to a dump file
Security requirements
Role: Database creator for exporting databases.
Role: Dashboard creator for exporting dashboards.
Role: Syndicate manager for downloading entities as dump files.
Entity Ownership: To maintain data privacy, only the entity's owner is permitted to export it as a file.
Steps to Export an Entity
Select the entity in your space.
On the toolbar, click the download icon.
From the menu, select the download option.
The “Download with sync” option will produce the file containing the credentials for establishing a synchronisation link with the original database.
It might take a few seconds to generate the dump file before the download begins.
Afterwards, you can create new entities from this dump file yourself or pass it to other users, allowing them to do so on another server.
Although dump files expire, keeping them secure is crucial. Anyone can use them to restore your entities on another server and access sensitive information. The best practice is to delete dump files once the transfer is complete and they are no longer needed.
Restoring an Entity from Dump Files on a New Server
Security requirements
Role:
Database creatorfor creating databases.Role:
Dashboard creatorfor creating dashboards.Role:
Syndicate managerto allow user to restore entities from a dump file.
To create a new entity from a dump file, authenticate on the target server and do the following:
Click on the + icon
in the Drive to create a new Entity.Select the option
Entity from dump file.Select the dump file from your disk.
Press Upload.
The newly created entity will be owned by the account under which it was restored. You can manage it as usual by sharing, granting access, or deleting it.
Be mindful of dependencies between the entities you plan to restore. For example, dashboards depend on databases. Transfer and restore entities one at a time, considering their dependencies. Ensure the required databases exist in the target folder before restoring a dashboard.
The source and target servers should be on the same version. DataTile may refuse dump files created by servers of different versions. Additionally, dump files may expire if kept for too long.
Populating changes from origin to remote entities
Requirements
Role:
Syndicate manageraccess to the API for downloading entities as dump files.Entity ownership- to maintain data privacy, only the entity's owner is permitted to export it and provide it for uploading on another server.
When you create a dump of an entity with synchronisation credentials, its icon changes to signify that this entity now serves as a source for remote entities.
The info panel of an entity provides information about the time of last synchronisation and other related details.
DataTile facilitates change management in the delivery process by allowing you to update and edit original entities on the source server without affecting remote deliverables.
Publish changes when ready to propagate them
Select the entity whose changes you want to propagate.
Click on the download button in the toolbar.
Click on the "Populate changes" option in the dropdown menu.
DataTile will synchronise remote entities within a few minutes.
Publish synchronized entities in the order of their dependency to minimize potential dysfunctions of the remote entities.
The deletion of the original entity will not affect remote entities. The sync relation will be interrupted, but remote entities will remain.
Please be aware of the following limitations for synchronized entities:
Reduced editing functionality: The editing capabilities of synchronized entities are limited in maintaining consistency with their source.
Cloning prohibition: Synchronised entities cannot be cloned.
Dumping prohibition: Creating dump files from synchronised remote entities is restricted to avoid further uncontrolled distribution.