Backing up and restoring Assets Server

There are several parts of Assets Server that need to be backed up regularly to ensure an easy restore and recovery in case of a hardware failure.

Info: Performing some of the steps described in this article requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.

What to backup

Because all Assets Server data is stored on the file system, all data in the following Assets Server folder locations should be backed up:

• Elvis Hot Data
• Elvis Shared Data
• Config

Note: It is recommended to create a backup in multiple locations in case one or more of these locations are compromised due to a security issue.

How to restore

To restore a backup, stop Assets Server, restore the files from your backup and then start Assets Server again.

Restoring the index

After restoring the backup, the state of the Elastic Search index in the Elvis Hot Data folder might not reflect the content of the main File store. You can restore a backup of the Elastic Search index with the Elastic Search terminal commands to synchronize the state of the index and the main File store.

For more information, see Creating or deleting a backup of the index in Assets Server.

Processing-only nodes

There is no direct need to regularly create a backup of a Processing-only node because it does not keep track of any essential data. If the machine fails, the Processing-only node can be easily re-installed on another machine.

Tip: To easily move your configuration to other installations, make a copy of the configuration files of the Processing nodes.