Starting a backup
A backup can be started in three ways:
- Manually, using the Backup... item of the 4D File menu or the Backup button of the Maintenance and Security Center.
- Automatically, using the scheduler that can be set in the Settings,
- Programmatically, using the
4D Server: A backup can be started manually from a remote machine using a method that calls the
BACKUPcommand. The command will be executed, in all cases, on the server.
- Select the Backup... command in the 4D File menu.
The backup window appears: You can see the location of the backup folder using the pop-up menu next to the "Backup destination" area. This location is set on the Backup/Configuration page of the Database Settings.
The Database properties... button causes the Backup/Configuration page of the Structure Settings to be displayed.
- Click Backup to start the backup using current parameters.
Scheduled automatic backup
Scheduled backups are started automatically. They are configured in the Backup/Scheduler page of the Settings.
Backups are automatically performed at the times defined on this page without any type of user intervention. For more information on using this dialog box, refer to Scheduler in backup settings.
BACKUP 4D language command is executed from any method, the backup starts using the current parameters as defined in the Settings. You can use the
On Backup Startup and
On Backup Shutdown database methods for handling the backup process (see the 4D Language Reference manual).
Managing the backup processing
Once a backup is started, 4D displays a dialog box with a thermometer indicating the progress of the backup:
This thermometer is also displayed on the Backup page of the MSC if you have used this dialog box.
The Stop button lets the user interrupt the backup at any time (refer to Handling backup issues below).
The status of the last backup (successful or failed) is stored in the Last Backup Information area of the Backup page in the MSC or in the Maintenance page of 4D Server. It is also recorded in the database Backup journal.txt.
Accessing the application during backup
During a backup, access to the application is restricted by 4D according to the context. 4D locks any processes related to the types of files included in the backup: if only the project files are being backed up, access to the structure is not possible but access to the data will be allowed.
Conversely, if only the data file is being backed up, access to the structure is still allowed. In this case, the application access possibilities are as follows:
- With the 4D single-user version, the application is locked for both read and write; all processes are frozen. No actions can be performed.
- With 4D Server, the application is only write locked; client machines can view data. If a client machine sends an add, remove or change request to the server, a window appears asking the user to wait until the end of the backup. Once the application is saved, the window disappears and the action is performed. To cancel the request in process and not wait for the end of the backup, simply click the Cancel operation button. However, if the action waiting to be executed comes from a method launched prior to the backup, you should not cancel it because only operations remaining to be performed are cancelled. Also, a partially executed method can cause logical inconsistencies in the data. > When the action waiting to be executed comes from a method and the user clicks the Cancel operation button, 4D Server returns error -9976 (This command cannot be executed because the database backup is in progress).
Handling backup issues
It may happen that a backup is not executed properly. There may be several causes of a failed backup: user interruption, attached file not found, destination disk problems, incomplete transaction, etc. 4D processes the incident according to the cause.
In all cases, keep in mind that the status of the last backup (successful or failed) is stored in the Last Backup Information area of the Backup page in the MSC or in the Maintenance page of 4D Server, as well as in the Backup journal.txt. displayed in the Last Backup Information area of the Backup page in the MSC or in
GRAPH SETTINGS of 4D Server, as well as in the
Backup journal of the application.
- User interruption: The Stop button in the progress dialog box allows users to interrupt the backup at any time. In this case, the copying of elements is stopped and the error 1406 is generated. You can intercept this error in the
On Backup Shutdowndatabase method.
- Attached file not found: When an attached file cannot be found, 4D performs a partial backup (backup of application files and accessible attached files) and returns an error.
- Backup impossible (disk is full or write-protected, missing disk, disk failure, incomplete transaction, application not launched at time of scheduled automatic backup, etc.): If this is a first-time error, 4D will then make a second attempt to perform the backup. The wait between the two attempts is defined on the Backup/Backup & Restore page of the Settings. If the second attempt fails, a system alert dialog box is displayed and an error is generated. You can intercept this error in the
On Backup Shutdowndatabase method.
To make following up and verifying backups easier, the backup module writes a summary of each operation performed in a special file, which is similar to an activity journal. Like an on-board manual, all database operations (backups, restores, log file integrations) are logged in this file whether they were scheduled or performed manually. The date and time that these operations occurred are also noted in the journal.
The backup journal is named "Backup Journal.txt" and is placed in the "Logs" folder of the project. The backup journal can be opened with any text editor.
Management of backup journal size
In certain backup strategies (for example, in the case where numerous attached files are being backed up), the backup journal can quickly grow to a large size. Two mechanisms can be used to control this size:
- Automatic backup: Before each backup, the application examines the size of the current backup journal file. If it is greater than 10 MB, the current file is archived and a new file is created with the [xxx] number incremented, for example "Backup Journal.txt”. Once file number 999 is reached, the numbering begins at 1 again and the existing files will be replaced.
- Possibility of reducing the amount of information recorded: To do this, simply modify the value of the
VerboseModekey in the Backup.4DSettings file of the project. By default, this key is set to True. If you change the value of this key to False, only the main information will be stored in the backup journal: date and time of start of operation and any errors encountered. The XML keys concerning backup configuration are described in the 4D XML Keys Backup manual.
All information regarding the latest backup and restore operations are stored in the application's backupHistory.json file. It logs the path of each saved file (including attachments) as well as number, date, time, duration, and status of each operation. To limit the size of the file, the number of logged operations is the same as the number of available backups ("Keep only the last X backup files") defined in the backup settings.
The backupHistory.json file is created in the current backup destination folder. You can get the actual path for this file using the following statement:
$backupHistory:=Get 4D file(Backup history file)
Deleting or moving the backupHistory.json file will cause the next backup number to be reset. The backupHistory.json file is formatted to be used by the 4D application. If you are looking for a human-readable report on backup operations, you might find the Backup journal more accurate.