Requirement
- A backup of a specific database
- A backup of all database relevant certificates
Prerequisites
- Access to the Server Manager
- Service Account requires write permissions to the backup destination directory
Procedure
Please log in to the Server Manager and open the "Backup" module.
Backups that have already been set up are displayed here.
Now set up a new backup with "New":
Profile name: freely selectable
Database: select the database to be backed up via the pull-down menu.
Backup path: select here the directory on the hard disk where the backup should be stored.
Hint:
The directory must be created on the hard disk beforehand.
If the SQL server is to be located on another server, the directory must be created on the SQL server beforehand.
This means that the database backup will always be saved on the server with the SQL server.
Select the directory:
SQL Server Authentication: If the service user is used to log on to the SQL Server, via Windows Authentication. Leave the checkmark set here.
If a local SQL user is used for logon, remove the checkmark and enter the user data with password.
In our example, we use the Windows authentication and confirm with "Next".
Now enter the desired interval of the backup:
As an example, here we have selected "Weekly" Every "Monday", "Wednesday" and "Friday" at 16:01.
In the description, the whole thing is summarized in words.
In the preview, you can see when in the future the backup will be performed.
The period and interval of the backup can be freely adjusted according to the needs.
You can also set an end date.
After that, confirm with "Next".
Now the advanced settings for the backup:
Active: Setting whether the backup should be active directly. If not, the backup must be started manually after it has been created.
Select the type of backup in the pull-down menu:
Full backup or differential backup.
Note
for automatically repeating backups, please always select the date and time to Add filename.
Via the Drop-down menu, you can select whether only the date or also the time should be added.
Why is this important?
The backup is always saved with the specified file name without adding the date and time.
Case study:
1. the backup is performed automatically. 3 times a week or 1 time a week or another period.
- At least the date must be added here.
2. the backup is performed several times a day.
- Here the date and time must be added.
If the date or date and time is not added, and an automatic backup is configured, the new backup will be added to the already existing backup and the backup file will increase in size.
If countless backups have already been written to a backup file, this backup file may cannot be restored!
Now the item Export certificates:
Here all certificates are exported, which are needed for this database.
All certificates are combined in a single .pfx file.
Export path: The certificates are stored locally on the server where the Server Manager is installed. That means, if the SQL-Server is installed on another server, the same directory as the database backup cannot be selected.
Export Password: Enter a password here that will be required when importing the certificates.
Hint:
Please make sure that the user stored at the backup service has write permissions in the defined directory and is allowed to export certificates.
In our example, the SQL server is installed on the same server, so we can select the same directory.
Complete the setup by clicking "Finish".
In the overview:
The backups that have been performed are now displayed.
Under Actions, the backup can be started manually at any time.
If the certificates are not exported automatically in the backup, it is necessary to export them manually.
To do this, please switch to the "Databases" module:
Select the database and select "Certificates".
All certificates are displayed in this menu. It is possible to switch the view between "All" and "Required certificates".
Here the certificates can be exported manually with "Export all".
This is necessary if the backup of the database is made directly through the SQL server.