Info: Performing 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.
Creating a backup of an Studio Server installation is essential when for instance performing a major upgrade to a higher version.
Creating a backup
Step 1. Create a complete dump or backup of your existing Studio Server database.
Step 2. Create a complete backup of the FileStore folder.
The default locations of this folder are:
- Linux: /FileStore
- Windows: c:\FileStore
Step 3. (Optional, only needed when modifications have been made to the Studio Server code — for example customization work to integrate Studio Server with 3rd-party applications.) Create a backup of the complete Studio Server directory.
The location is dependent on the system and HTTP Server used (Apache/IIS), but the directory should normally be in one of the following locations:
- Windows: c:\inetpub\wwwroot
- Linux: /var/www/html
Note: Leave the old folder in place. (In most production environments, the new Studio Server is initially installed next to the existing server so that the new setup can be tested before it is made live.)
Step 4. (Optional, only if you have not performed step 3.) Create a backup of the configuration files.
Restoring a backup
Step 1. Restore the Studio Server database.
Step 2. Restore the FileStore folder.
Note: When restoring the FileStore in a new location, make sure to update the paths in the configuration files.
Step 3. Restore the Studio Server folder structure or install a new version of Studio Server.
Step 4. Run the Health Check page for Studio Server to verify that all is working correctly.