Specifications

A.3 Migrate to another Microsoft SQL Server

version.

Scenario

The company needs to move a database to another server, where a newer Microsoft SQL

Server version is installed. After the migration, the server must have a different name, and

the old server must remain operational (to provide fast database rollback in case a

contingency occurs).

Acronis solution

1. Install a new Microsoft SQL Server instance.

2. Set the old database to StandBy mode.

3. Create a backup of the old Microsoft SQL Server instance using a previously created

task (running it from the Acronis Recovery for MS SQL Server Management Console)

or create a new task (full backup).

4. Restore to a new Microsoft SQL Server instance.

5. Specify new settings for working with a new Microsoft SQL Server instance.

A.4 Backing up several databases

Scenario

The company uses only one Microsoft SQL Server instance for running several databases. All

databases have different levels of importance concerning data loss: some of them need to

be backed up every day, others require only weekly backups.

Acronis solution

The database administrator should create independent tasks for different databases. While

creating a task, the database administrator specifies the appropriate schedule for each

database.

A.5 Encrypting database archives for storage

Scenario

The company stores database backup archives off-site, hence they should be effectively

protected (encrypted).

Acronis solution

While creating a backup task, the database administrator should set a password to protect

the archive and encryption type (AES 128, 192 or 256) by specifying backup options.

While creating the restore task, the administrator has to provide the correct password to the

archive in order to restore the data. The password should be kept in a safe place so that

data may be restored if the company hires new administrators.