Using the Control Panel backup/restore feature

To create your portal data backup manually, switch to the Backup page in the COMMON SETTINGS section on the left sidebar and use the Data Backup section.

1. select the necessary type and location of the Storage for your backup files:
   • select the Temporary tab if you wish to download the backup to your local drive when the backup process is over. You'll be able to do that using the link that appears below.
     
   • select the Documents module tab and click the Plus button next to the field that appears below. The Select folder window will open. Set a folder in the Common Documents section where you wish to store your backup and click the OK button.
     
   • select the Third-Party Storage tab, choose one of the available third-party storages and enter the necessary data to access it:
     1. The necessary service (Amazon AWS S3, Google Cloud Storage, Rackspace Cloud Storage, Selectel Cloud Storage, DropBox, Box.com, OneDrive, Google Drive) must be previously connected in the Integration section of the portal settings. Otherwise the corresponding storages will be disabled and grayed out.
     2. The third-party account (DropBox, Box.com, OneDrive, Google Drive, Yandex Disk and storages connected via the WebDAV protocol, such as Nextcloud or ownCloud) must be previously connected to the Documents module as well as make shared and put into the Common Documents section. Otherwise the corresponding storages will be disabled and grayed out.
     

     When the necessary storage is selected, specify the data to access it in the fields that appear below:

     • For the Amazon AWS S3 service, the following fields are available:
       • Bucket - unique Amazon bucket name, e.g. my-new-test-bucket-12345.
       • Region - an AWS region where your Amazon bucket resides, e.g. us-east-2.
       • Service Url - this is an optional property; change it only if you want to try a different service endpoint. Leave this field empty to use the default value.
       • Force Path Style - when true, requests will always use path style addressing. Leave this field empty, as the Service Url property is not specified.
       • Use Http - if this property is set to true, the client attempts to use HTTP protocol, if the target endpoint supports it. By default, this property is set to false. Set it to true or leave this field empty to use the default value.
       • Server Side Encryption Method - the server-side encryption algorithm used when storing this object in S3. The possible values are:
         • None
         • Server-Side Encryption - SSE-S3 (your assets will be encrypted with strong AES-256 GCM keys, one separate key for each object. The keys themselves are encrypted with a rotating root key for additional protection) or SSE-KMS (your assets will be encrypted with with a versatile encryption mechanism. Like SSE-S3, it relies on strong AES-256 encryption method, but provides more complex and flexible model, offering separate permissions for a KMS key, audit trail feature, and ability to create unique custom keys). For SSE-KMS, you can choose Managed CMK - Default AWS managed CMK or Customer managed CMK. When the Customer managed CMK option is selected, you need to specify the KMS Key Id.
         • Client-Side Encryption - when this option is selected, you need to specify the KMS Key Id.
     • For the Google Cloud Storage service, the following field is available: Bucket (unique Google Cloud bucket name, e.g. test_bucket111419).
     • For the Rackspace Cloud Storage service, the following fields are available: Public container (Rackspace public container URL address), Private container (Rackspace private container URL address) and Region (a region where your Rackspace containers are located).
     • For the Selectel Cloud Storage service, the following fields are available: Private container (Selectel private container name, e.g. test_container) and Public container (Selectel public container name, e.g. test_container_public).
     • For the DropBox, Box.com, OneDrive, Google Drive, Yandex Disk services or storages connected via the WebDAV protocol, click the Plus button next to the field that appears below. The Select folder window will open. Set a third-party resource directory located in the Common Documents section where you wish to store your backup and click the OK button.
   • select the Computer file tab if you wish to save the backup on your local drive. In the Choose the storage location field that appears below, specify the path to the folder where you wish to store your backup.
     
   If you select the Documents module or one of the third-party services connected to it (DropBox, Box.com, OneDrive, Google Drive, Yandex Disk and storages connected via the WebDAV protocol), the backup file size affects the overall disk space used on your portal.
2. check the Include Mail in backup box if you want to backup the Mail data as well. This increases the backup process time and backup file size, but if this option is unchecked, the Mail data will be lost after restoring and you'll need to connect accounts again. Please refer to the Backup Mail data section to find aditional instructions for Mail.
   The license data will not be included into the backup. After restoring data from the backup, you will need to upload your license file again.
3. click the MAKE BACKUP button.

Once the backup process is completed you'll find the backup .tar.gz file (portal-name_date_time.tar.gz) in the specified folder. If you've selected the Temporary storage, the link to download the created backup will be available for 24 hours.

Perform additional actions to backup the Mail data.

1. Enter the Community Server container:

   docker exec -it onlyoffice-community-server bash

2. Go to the services folder:

   cd /var/www/onlyoffice/Services/TeamLabSvc

3. Open the configuration file:

   nano TeamLabSvc.exe.config

4. Add settings for access to the host machine:

   <backup>
     <mailServer pathToMailFilesOnHost="/app/onlyoffice/MailServer/data" hostAddress="127.0.0.1" hostUsername="root" hostKey="/tmp/key.pem" />
   </backup>
   

   • pathToMailFilesOnHost - the full path to the Mail Server files. For Linux, you can specify the following path: /app/onlyoffice/MailServer/data.<
   • hostAddress - the address of the machine where the Mail Server container is located.
   • hostUsername - the username for connecting to the machine where the Mail Server container is located.
   • hostPassword - the password for connecting to the machine where the Mail Server container is located.
   • hostKey - the path to the file with the user's SSH certificate for connecting to the machine where the Mail Server container is located. The file must be in the OpenSSH format, it can be generated with Putty Key Generator.
   ImportantEither hostPassword or hostKey field must be filled in. If both fields are filled in, the connection will be performed using the key first, if unsuccessful, the password will be used.
   ImportantThe user (hostUsername) specified in the settings must have rights to read and write the folder with the Mail Server files (pathToMailFilesOnHost). For Linux machines, you can execute the following command: chmod -R 755 /app/onlyoffice/MailServer/data.
5. Save the file (Ctrl+S) and exit (Ctrl+X).
6. Restart the service:

   systemctl restart onlyofficeBackup

7. Proceed to the Data restore section to restore data from the backup file.

To automate the backup process, switch to the Backup page in the COMMON SETTINGS section on the left sidebar and use the Automatic backup section:

1. click the Disabled switcher to enable the feature.
2. select the necessary Storage for your backup files (the available options are the same as those described above, except for the Temporary storage which is only available in the Data Backup section).
3. specify the time interval at which backups should be created: Every day with an indication of the necessary time of the day, Every week with an indication of the necessary day of the week and time of the day, or Every month with an indication of the necessary day of the month and time of the day.
4. set The maximal number of backup copies to be stored selecting the necessary value (from 1 to 30) from the corresponding drop-down list.
5. check the Include Mail in backup box if you want to backup the Mail data as well.
6. click the SAVE button.

Backups will be created automatically with the specified periodicity.

To restore your portal data from the previously created backup file, switch to the Restore page in the COMMON SETTINGS section on the left sidebar.

1. select the Source where your backup files are stored:
   • select the Documents module tab and click the Plus button below. In the Select file window, choose the necessary backup file stored in the Common Documents and click OK.
   • select the Third-Party Storage tab, choose the necessary third-party storage and enter the data to access it as well as the necessary backup file URL address in the Path field.

     For accounts connected to the Documents module (DropBox, Box.com, OneDrive, Google Drive, Yandex Disk and storages connected via the WebDAV protocol), click the Plus button below. In the Select file window, choose the necessary backup file stored in the third-party resource directory located in the Common Documents section and click OK.

   • select the Computer file tab, click the Plus button next to the Choose the storage location field, and browse for the necessary backup file stored on your local drive.
     Instead of selecting a backup file from a certain Source, you can just click the Show the backup list link below the radio buttons to select the necessary backup file from the backup history (if a backup file was deleted manually from the storage, it will not be available in the list). Click the Restore link next to the necessary backup file. To delete a backup file from the list, click the icon.
2. if necessary, leave the Send notification about portal restore process to users box checked to notify your portal users;
3. click the RESTORE button.
   Remember that you will need to upload your license file again when the restoring process is complete. This can be done in the Payments section.
   If you created a backup file in the cloud version and then restore it in the server version, current passwords will be reset and access can only be restored via the Forgot your password? link on the authorization page.