Collapse All Expand All

The Copy destinations form defines the destinations for copying the backup files of a maintenance policy, that is where the files are copied to. The form opens at the Backup creation settings step of the wizard when the Copy new and changed backup files option is enabled, and from the policy properties.

Copy destinations

The program uses two terms:

• a connection is the settings for connecting to a storage: a local or network folder, Yandex Disk, an FTP or SFTP server;
• a copy destination is a connection together with the set of databases and the retention period of the backups.

A policy can have several destinations. For each destination the list shows the connection, its type, the databases, the retention period and the job task that performs the copying.

The Add…, Edit… and Delete buttons add, change or remove a copy destination. When a destination is removed, the connection itself is kept.

Destination settings

Destination settings

On the Destination settings form you need to:

1. Specify which databases of the policy have to be copied: all of the policy's databases or selected databases.
2. Specify the Connection to use. A new one can be created right here by selecting the create new connection ... value in the list: first the connection type is chosen, then the form with its settings opens - a folder, Yandex Disk, an FTP server or an SFTP server. The button opens the settings of the selected connection. Later the connections are managed in the Settings > Connections menu.

   Choosing the type of a new connection

3. Set the retention period of the backups in this destination (Delete after a storage period of).

Copying tasks

Copying is performed by job tasks: each kind of destination has its own task - Backup copying to a folder, Backup copying to Yandex Disk and Backup copying to FTP/SFTP. A task copies new and changed files to all destinations of its kind and deletes outdated ones. The cloud copying tasks are added to the jobs inactive: enable the required task in the policy job or create a separate job for it with its own schedule, for example at night, so that transferring large files does not delay the maintenance. See Maintenance policy jobs.

The progress and the errors are written to the task execution log. For each destination a header with the connection name is written, then the name, size and result for each file, and the number of copied files and the elapsed time at the end.

QMB service access to the backup folder

Copying to the cloud is performed by the QmbService service. If the QmbService service and SQL Server run on different computers, the service needs network access to the SQL Server backup folder; in this case the form shows the access settings block.

Service-side path - the network path to the backup folder as seen from the service computer, for example \\SQL01\Backups. By default a path through the administrative share of the drive is substituted (\\SQL01\D$\SQLBackups).

QMB service account or specified account - the account used to connect to the folder: the one the service runs as, or the one given by a user name and password.

Check access - SQL Server creates a marker file in the backup folder, and the service reads it through the specified path. This confirms that the path leads to that very folder and the account has access to it.