Using Microsoft SQL Server backups for point-in-time recovery on Compute Engine

In this tutorial, you perform backups on a Compute Engine SQL Server instance. The tutorial shows you how to manage these backups and store them in Cloud Storage and how to restore a database to a point in time.

This tutorial is useful if you are a sysadmin, developer, engineer, database admin, or devops engineer who wants to back up SQL Server data.

Note: Although managing backups is crucial for any disaster recovery plan, this tutorial doesn't address the topic of disaster recovery for SQL Server.

The tutorial assumes that you are familiar with the following:

• Microsoft Windows
• Microsoft SQL Server
• SQL Server full, differential, and transaction log backups
• Compute Engine
• Cloud Storage

Objectives

• Launch a SQL Server instance and create a database.
• Perform full, differential, and transaction log backups.
• Upload the backups to Cloud Storage.
• Restore the database from a Cloud Storage backup.

Costs

This tutorial uses the following billable components of Google Cloud:

• Compute Engine
• Networking
• Cloud Storage
• SQL Server (premium with compute engine)

To generate a cost estimate based on your projected usage, use the pricing calculator. New Google Cloud users might be eligible for a free trial.

Before you begin

1. Sign in to your Google Account.

   If you don't already have one, sign up for a new account.

2. In the Cloud Console, on the project selector page, select or create a Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to the project selector page

3. Make sure that billing is enabled for your Google Cloud project. Learn how to confirm billing is enabled for your project.

4. Enable the Compute Engine API.

   Enable the API

When you finish this tutorial, you can avoid continued billing by deleting the resources you created. For more information, see Cleaning up.

Preparing the SQL Server instance

In this section, you launch the SQL Server instance, prepare the database, and configure an encryption key.

Launch the SQL Server instance

Your first task is to launch a SQL Server instance and create the backup folder.

1. Open Cloud Shell:

   GO TO Cloud Shell

2. Launch a SQL Server instance:

   gcloud compute instances create sqlserver \
       --zone=us-central1-c \
       --machine-type=n1-standard-1 \
       --image-family=sql-std-2019-win-2019 \
       --image-project=windows-sql-cloud \
       --boot-disk-size=50GB \
       --boot-disk-type=pd-standard \
       --tags=sqlserver \
       --scopes=https://www.googleapis.com/auth/cloud-platform
   

3. Install the Chrome RDP for Google Cloud extension.

   Note: You launch this extension later directly from the Cloud Console.

4. Go to the VM instances page in the Cloud Console and find the Windows instance you want to connect to:

   GO TO THE VM INSTANCES PAGE

5. Set the initial password for the instance. Store the password in a safe place.

6. Click the RDP button for the instance you want to connect to. The Chrome RDP extension opens.

7. Enter your username and password (leave the Domain field blank), and then click OK to connect.

   

   You are prompted to accept the certificate.

8. If you accept the terms, click Continue.

Install SQL Server Management Studio

Install Microsoft SQL Server Management Studio (SSMS) by doing the following:

1. In your RDP session, minimize all windows, and start the Windows PowerShell ISE app.

2. At the PowerShell prompt, download and execute the SSMS installer:

   Start-BitsTransfer `
       -Source "https://aka.ms/ssmsfullsetup" `
       -Destination "$env:Temp\ssms-setup.exe"
   & $env:Temp\ssms-setup.exe
   

3. Accept the prompt to allow changes to be made.

4. In the SSMS installer, click Install.

5. When the installation is finished, click Restart to restart the remote machine. This closes the RDP session.

6. To reconnect, in the RDP window, click Connect. If the remote machine has not finished restarting, wait a few moments and then try connecting again.

7. Enter your username and the password you saved earlier (leave the Domain field blank), and then click OK to reconnect.

Prepare the database

1. In the RDP session, minimize all windows, and then open Google Cloud SDK Shell (not the same as Cloud Shell) on the Windows desktop.

2. Create a backup folder:

   mkdir c:\backup
   

3. Create a restore folder:

   mkdir c:\restore
   

Prepare the database

1. In Google Cloud SDK Shell, on the instance, create a test database:

   osql -E -Q "create database testdb"
   

2. Create a test table:

   osql -E -Q "create table testdb.dbo.testtable(status varchar(255))"
   

Configure the encryption key

1. In Google Cloud SDK Shell, create a primary database key:

   osql -E -Q "USE master;CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'MASTER1!';"
   

   Note: In this tutorial, you use the password Master1! for the encryption key, but you can choose whichever password you want.

2. Create a backup certificate:

   osql -E -Q "USE primary; CREATE CERTIFICATE testdbcert WITH SUBJECT = 'testdb certificate';"
   

Performing backups

In this section, you create full, differential, and transaction log backups while changing the database between each one.

1. Add a row to the test table:

   osql -E -Q "insert into testdb.dbo.testtable ([status]) VALUES ('Initial')"
   

2. In Google Cloud SDK Shell, perform a full backup:

   osql  -E -Q "BACKUP DATABASE testdb TO DISK='c:\backup\testdb.bak' WITH INIT,
       COMPRESSION,
       ENCRYPTION
       (
           ALGORITHM = AES_256,
           SERVER CERTIFICATE = testdbcert
       )  "
   

   Note: You'll receive a warning that you have not backed up the certificate. Backing up the certificate is beyond the scope of this tutorial.

3. Add a row to the test table:

   osql -E -Q "insert into testdb.dbo.testtable ([status]) VALUES ('After Full Backup')"
   

4. Perform a differential backup:

   osql  -E -Q "BACKUP DATABASE testdb TO DISK='c:\backup\testdb-diff.bak' WITH DIFFERENTIAL,
   COMPRESSION,
   ENCRYPTION
       (
       ALGORITHM = AES_256,
       SERVER CERTIFICATE = testdbcert
       ) "
   

5. Add a row to the test table:

   osql -E -Q "insert into testdb.dbo.testtable ([status]) VALUES ('After Diff Backup')"
   

6. Perform a transaction log backup:

   osql  -E -Q "BACKUP LOG testdb TO DISK='c:\backup\testdb-log.bak' WITH COMPRESSION,
   ENCRYPTION
       (
       ALGORITHM = AES_256,
       SERVER CERTIFICATE = testdbcert
       ) "
   

7. Add a row to the test table:

   osql -E -Q "insert into testdb.dbo.testtable ([status]) VALUES ('Bad Row')"
   

8. Verify the rows in the table:

   osql -E -Q "select * from testdb.dbo.testtable"
   

   The output looks like this:

   Initial
   
    After Full Backup
    After Diff Backup
    Bad Row
   

Managing your backups

In this section, you store your backups remotely in Cloud Storage, configure your Cloud Storage bucket to prune old backups automatically, and schedule your backups. If you're running multiple database servers, consider creating multiple directories in your Cloud Storage bucket to represent different servers.

Upload your backups to Cloud Storage

Now that you have a few backup files, you can upload your backups to Cloud Storage.

1. In Cloud Shell, create a Cloud Storage bucket. Bucket names must be globally unique across Google Cloud. To ensure that your bucket name is unique, consider namespacing it with your project name, as shown here:

   gsutil mb "gs://${DEVSHELL_PROJECT_ID}-sql-backups"
   

2. In the shell window in the RDP session, copy your files to your Cloud Storage bucket. In the following command, replace [BUCKET_NAME] with the name of the bucket you just created.

   gsutil cp -n c:\backup\testdb*.bak gs://[BUCKET_NAME]
   

   Note: The -n flag prevents the gsutil tool from overwriting identical files.

   You can use the gsutil cp command to create entire directory structures and to upload multiple files at a time.

Set up automatic file pruning in Cloud Storage

Older backups eventually outlive their usefulness, so you need to remove them. To help automate this process, Cloud Storage has a lifecycle management mechanism that you can use to manage the lifecycle of your backup files.

Warning: The lifecycle mechanism deletes files permanently, with no chance of recovering them. When testing your lifecycle configuration, test it on noncritical data files.

To configure lifecycle management for the objects in your bucket:

1. In Cloud Shell, create a JSON lifecycle configuration file. This file instructs Cloud Storage to delete files after 30 days:

   bash -c 'cat <<EOF >  lifecycle.json
   {
       "lifecycle": {
           "rule": [{
               "action": { "type": "Delete" },
               "condition": { "age": 30 }
           }]
       }
   }
   EOF'
   

2. Set the lifecycle configuration for your Cloud Storage bucket. Replace [BUCKET_NAME] with the name of your bucket:

   gsutil lifecycle set lifecycle.json gs://[BUCKET_NAME]
   

Schedule your backups

In general, it's a good practice to take a full backup periodically and perform differential backups until the next full backup. On Windows, one way to schedule backups is by using scheduled tasks.

If you create a backup script that takes a series of backups, make sure to include some logical validation steps at each point to verify successful completion. If validation fails, make sure the script raises a Windows alert. In addition, to avoid filling up the local disk, make sure the script removes the local backup file after successfully uploading to Cloud Storage.

Restoring from backup

In this section, you restore your SQL Server database from backup files that you stored in Cloud Storage.

1. In Google Cloud SDK Shell in your RDP session, download your backup files from Cloud Storage. Replace [BUCKET_NAME] with the name of your SQL Server backup storage bucket:

   gsutil cp gs://[BUCKET_NAME]/testdb*.bak c:\restore
   

2. Open the SQL Server Management console.

3. Click the Start button, and then click Microsoft SQL Server Tools 18 > Microsoft SQL Server Management Studio 18.

4. Leave the Connection fields as is, and then click Connect.

5. In the left-hand pane, expand Databases.

6. Right-click testdb, and in pop-up the menu, click Tasks > Restore > Database.

7. Import the backup files to the console:

   1. For Source, select Device.
   2. Click the button.
   3. In the dialog that opens, click Add, select all the files under C:\restore, and then click OK.
   4. Click OK.

8. To view point-in-time restore options:

   1. Click Timeline.
   2. Under Restore to, click Specific date and time.
   3. For Timeline Interval, select hour.
   4. Choose a time in the Transaction Log Backup range.

   5. Click Cancel to leave the timeline screen.

      Note: To restore your database to a specific point in time, you press OK instead of Cancel.

9. In this tutorial, you restore the database to its state before the transaction log backup. In order to do that, in the backups list, clear the transaction log row:

   

10. Start the restore process:

    1. Click OK.
    2. Wait for the database to finish the restore process, and when you see the message, Database 'testdb' restored successfully, click OK.

11. List the rows in the test table:

    osql -E -Q "select * from testdb.dbo.testtable;"
    

    The output shows two rows:

    "Initial
    "After Full Backup"
    

    You see all the lines you inserted into the table before taking the transaction log backup.

Cleaning up

Delete the project

Caution: Deleting a project has the following effects:
• Everything in the project is deleted. If you used an existing project for this tutorial, when you delete it, you also delete any other work you've done in the project.
• Custom project IDs are lost. When you created this project, you might have created a custom project ID that you want to use in the future. To preserve the URLs that use the project ID, such as an appspot.com URL, delete selected resources inside the project instead of deleting the whole project.
1. In the Cloud Console, go to the Manage resources page.

   Go to the Manage resources page

2. In the project list, select the project that you want to delete and then click Delete .
3. In the dialog, type the project ID and then click Shut down to delete the project.

What's next

• Read about SQL Server best practices on Google Cloud.
• Read about configuring SQL Server availability groups.
• Read the disaster recovery planning guide for Google Cloud.
• Try out other Google Cloud features for yourself. Have a look at our tutorials.