Table of Contents
- Features (only up to version 20.1)
- Data backup (creating the backup)
- Download (Local backup of a backup)
- Upload / remote import of a backup
- Data restore (restoring the backup)
Important: As of version 20.1, the backup module has been rebuilt. Backups must run directly through the server and cannot be imported into Xentral directly through the interface. This is only for the server move. Information about this can be found here.
Features (only up to version 20.1)
Regular backups of the entire system can be made in the Backup module. This applies regardless of whether a system is hosted in the Xentral Cloud, on a root or shared server, or On Premises. You can find the module under Administration → Backup. After a backup is created and downloaded, it can also be restored to another system. Thus, moving a system from one server to another is possible.
The following functions are available:- Backing up the backup and saving it on the server
- Download of the backup to a local computer
- Upload of the backup to a remote server
- Import of a previously created backup
Recommendations and hints
Comparison to previous versions of the backup module
Unlike previous versions of the backup module, exactly one form of backup is still available, previously known as the system backup. This backup form backs up the database with all document, image and PDF files. This ensures that all file links are valid for each individual backup and that no inconsistencies can occur in the system even if multiple backups are made. Due to the form of the backup as a total backup, the backup file may become larger under certain circumstances. Therefore, the backup process runs in the background. For this reason it is necessary to activate the process starter (backup) in the system. During the backup process the different steps of the backup are displayed in the browser.
Note: In order to maintain a consistent data set within a backup, all running process starters are switched off at the beginning of the backup creation. This means that no queries via interfaces, no stock updates or order entries are processed.
Recommendation for data security (1): Please back up your data regularly using a system backup. Recommendation for data security (2): Please regularly download backed-up data from your server and save this data on physically secured storage media (e.g. on external hard disks in a fireproof safe or bank safe deposit box). Recommendation for data security (3): Please check the backup regularly by downloading and unpacking a created archive. In the archive you will find the contents of the Xentral database and a folder userdata with many directories (only in the system backup). Please check if all data is present there.
Recommendation for data protection: A backup contains all - also sensitive - data of your system, i.e. besides accounting data also e.g. personnel, customer and account data. Please make sure that the backed up backup files are stored in a secure location that only allows access to authorized persons. This includes in particular potentially public servers, data storage services without ADV or IT hardware accessible in the office such as external hard disks or openly accessible network storage devices (so-called RAID systems).
Data backup (creating the backup)
A backup is created by clicking the + NEW button. Note: During the backup, no work may be done on the system (not even by other users).
First you can name your backup. It is not necessary to enter date and time information here, they will be added to the backup automatically.
Then the backup is created in the background. Creating a backup may take a long time. Through the display on the page you can see the individual stages of the backup:
Download (Local backup of a backup)
A created backup is first stored on the server and can be restored from there. However, it can also be downloaded to a local computer for backup purposes. To do this, click on the download button in the overview of the backup module.
Select Save... file and download the file. Image example: Firefox on Mac OS.
The file can be found in the doanload area of the browser or in the doanload folder of the computer. Image example: Firefox on Mac OS.
Upload / remote import of a backup
The Importer tab can be used to upload a local backup file to a remote server. There is no size limit for an import and even very large files can be uploaded without any problems as long as there is enough storage space available on the server. Only after the upload is the import of the file possible.
When uploading, the following should be observed:- The file must be of type .zip (ZIP archive) and contain the expected file structure.
- The uploaded file should not exist in the system yet, otherwise the saving is not possible.
- Expert tip: Optionally, a meta file could be attached for each backup. Please note: if the file name is "my-last-backup.zip", the meta file should also be called "my-last-backup.meta". If, a meta file is available, additional checks will be executed after successful recovery. Thus, appropriate messages could be displayed if, for example, the ACTUAL state of a table shows deviations from the TARGET state.
The upload is started in the Importer tab by selecting the file to be uploaded. Afterwards, the upload can be canceled or started by clicking on Upload.
The progress of the upload is displayed continuously. After the upload, the system automatically switches to the overview page.
Data restore (restoring the backup)
The data restore is possible by clicking on the back arrow. Note: During the restore, no work may be done on the system (not even by other users).
In the following, you will be informed by the display of the running process in the background through regular status updates.
After a backup has been successfully imported, the processes that were switched off are reinitiated, including process starters. If a process starter makes changes to the system immediately after the import, this can lead to deviations in the comparison routine. In this case, one or more messages in the following form would indicate which data is affected (in the following case, an update due to a retrieval of payment data from a payment provider that is performed regularly):
Usually these messages are not critical because they can be explained by the running processes in the system.