GSP945

Overview

Actifio GO for Google Cloud is a SaaS offering which enables powerful enterprise class backup and disaster recovery for Google Cloud residents and on-premises workloads.

Actifio supports the following workloads:

• Compute Engine Instances, On-premises VMware, and Google Cloud VMware Engine VMs
• SAP HANA, Oracle, Microsoft SQL Server, MySQL, Postgres, Db2, MongoDB, and databases running on physical servers

Key Features:

• Application consistent incremental forever capture of databases and VMs which reduces RPO significantly
• Instant recovery on-premises or in the cloud which reduces RTO to minutes
• SLA driven data management
• Google-like search catalog for file / folder restore directly from Persistent Disk or Nearline/Coldline to the VM of choice
• Data encryption in transit and at rest

What you'll do

Below is a diagram of the lab environment:

In this lab you will perform the following:

1. RDP into an already provisioned SQLSERVER Compute Engine instance running Microsoft SQL Server ACTIFIO-MSSQL.
2. Connect to ACTIFIO-MSSQL 2017 server and browse some sample table data.
3. Download the Actifio connector (agent) from Actifio SKY Data Mover and install it on SQLSERVER Compute Engine instance.
4. Define SLA Template & Profile (backup policy).
5. Add SQLSERVER Compute Engine instance as a host on AGM; Discover ACTIFIO-MSSQL instance and all the databases on it.
6. Protect ACTIFIO-MSSQL server with backup policy defined in step #4.
7. Run on-demand backups.
8. View backups.

Prerequisites

Some familiarity with Microsoft SQL Server.

Setup

Before you click the Start Lab button

Read these instructions. Labs are timed and you cannot pause them. The timer, which starts when you click Start Lab, shows how long Google Cloud resources will be made available to you.

This hands-on lab lets you do the lab activities yourself in a real cloud environment, not in a simulation or demo environment. It does so by giving you new, temporary credentials that you use to sign in and access Google Cloud for the duration of the lab.

To complete this lab, you need:

• Access to a standard internet browser (Chrome browser recommended).

Note: Use an Incognito or private browser window to run this lab. This prevents any conflicts between your personal account and the Student account, which may cause extra charges incurred to your personal account.

• Time to complete the lab---remember, once you start, you cannot pause a lab.

Note: If you already have your own personal Google Cloud account or project, do not use it for this lab to avoid extra charges to your account.

How to start your lab and sign in to the Google Cloud console

1. Click the Start Lab button. If you need to pay for the lab, a pop-up opens for you to select your payment method. On the left is the Lab Details panel with the following:

   • The Open Google Cloud console button
   • Time remaining
   • The temporary credentials that you must use for this lab
   • Other information, if needed, to step through this lab

2. Click Open Google Cloud console (or right-click and select Open Link in Incognito Window if you are running the Chrome browser).

   The lab spins up resources, and then opens another tab that shows the Sign in page.

   Tip: Arrange the tabs in separate windows, side-by-side.

   Note: If you see the Choose an account dialog, click Use Another Account.

3. If necessary, copy the Username below and paste it into the Sign in dialog.

   {{{user_0.username | "Username"}}}

   You can also find the Username in the Lab Details panel.

4. Click Next.

5. Copy the Password below and paste it into the Welcome dialog.

   {{{user_0.password | "Password"}}}

   You can also find the Password in the Lab Details panel.

6. Click Next.

   Important: You must use the credentials the lab provides you. Do not use your Google Cloud account credentials. Note: Using your own Google Cloud account for this lab may incur extra charges.

7. Click through the subsequent pages:

   • Accept the terms and conditions.
   • Do not add recovery options or two-factor authentication (because this is a temporary account).
   • Do not sign up for free trials.

After a few moments, the Google Cloud console opens in this tab.

Note: To view a menu with a list of Google Cloud products and services, click the Navigation menu at the top-left.

Task 1. Connecting to Microsoft SQL Server 2017 instance

When this lab spun up, a Microsoft SQL 2017 server on Windows 2016 Datacenter VM was provisioned for you as part of this lab. You will install the Actifio agent on this VM, discover the SQL server databases, and then protect them.

1. In the Cloud Console, expand the Navigation menu (), and select Compute Engine > VM Instances.

You should see 3 VM instances.

2. Click the sqlserver instance RDP.

This opens up the Connect using your RDP client pop-up.

3. Click the Download the RDP file if you will be using a 3rd-party client link to download the file.

4. Once downloaded, click on the downloaded RDP file. This connects to the sqlserver instance using RDP. In case you get any certificate warning, just ignore and click Continue as shown in the below screen.

5. When prompted for credentials, enter the Username as demouser and password as P@ssw0rd and then click the Continue button.

6. In a few moments, you are connected to the sqlserver instance using RDP.

Now connect to the SQL server running on this instance and explore some data.

7. Click on the Windows icon, select Microsoft SQL Server Tools 18 and then select Microsoft SQL Server Management Studio.

In a few moments, the SQL Server Management Studio login screen opens.

8. Select Server Name: ACTIFIO-MSSQL, then click on the Connect button.

9. Browse through some databases and tables.

• In the Object Explorer pane, expand Databases and to see the OLTP database named AdventureWorks2017.
• Expand the tables in it and to see it has a bunch of tables.
• Right click the "HumanResources.Employee" table and select "Select top 1000 rows" to see some data.

See the below screen for reference.

Note: In this lab, you protect this "ACTIFIO-MSSQL" server and all the databases within it.

Task 2. Installing Actifio connector

To download the needed Actifio connector (agent) and install it on the sqlserver Compute Engine instance, you need the internal IP address of Actifio Sky data mover, because all the Actifio agents are hosted on Actifio Sky data mover appliance.

Note: Connector is needed so that Actifio can discover all the databases running on a host (SQLSERVER Compute Engine instance), orchestrate application consistent backups, and perform mount, restore and other operations.

1. To get the internal IP address, go back to the Compute Engine page on the Cloud Console and copy the internal ip address of the sky-server instance.

2. Now go back to the sqlserver instance that you are already connected to using RDP and open the Internet Explorer to add the internal ip address of the sky-server instance.

This will open up the "Actifio Resource Center" page.

3. Click on the Windows Connector link as shown in the below screen.

4. When prompted to either run or save the file, click Run.

In a few moments, a User Account Control pop-up window will appear.

5. Click on the Yes button to continue with the Actifio connector installation.

This brings up the Actifio connector setup wizard.

6. Within the Actifio connector setup wizard:

• Click Next on the welcome screen.
• Click Next to continue with the default installation path.
• On the Select Component dropdown, select Actifio Connector with Change Tracking Driver, click Next.
• On the "Ready to install" screen click Install.

The installation takes a few seconds to complete.

7. When complete, click the Finish.

Click Check my progress below to check your lab progress. Install Actifio connector

Task 3. Logging into Actifio Global Manager (a.k.a AGM)

1. Navigate to the Cloud Console > Compute Engine page and copy the external IP address of agm-server.

2. Open a new browser tab/window and paste the following URL:

https://\<agm-server\>:443

Remember to replace the <agm-server> with agm-server's external IP address obtained from step #1 above.

3. This takes you to the AGM login screen. Use the below credentials to log in.

• Username: admin
• Password: @ct1f1O!#@

Note: Ignore any security/certificate warnings and continue.

4. Once logged in, the dashboard page opens.

Task 4. Defining SLA templates and profiles (a.k.a backup policies)

Before you discover your MSSQL server, you define an SLA template and profile, which together in Actifio make a backup policy. Once you define a backup template and profile, you discover the ACTIFIO-MSSQL server on the sqlserver instance (you previously connected to) and then protect the "ACTIFIO-MSSQL" server.

Learn more about SLA templates and profiles from the YouTube video Considerations for Designing SLA Architecture.

Creating a template

In this section, you create an SLA template, which dictates how to backup, how frequently to backup, and the retention period.

For simplicity, you will define a Template with a simple policy that will backup your ACTIFIO-MSSQL server twice everyday and store backups in a local cache (also known as snapshot pool). You will configure the database logs to be backed up every hour.

Note: In real life, you would add another policy to the template to send backups to Google Cloud Storage - NearLine or ColdLine to have a secondary copy in case of a disaster or to meet your long term retention to optimize your storage cost. But for simplicity, you will back up the database to the snapshot pool (a.k.a local cache).

1. On the AGM, navigate to SLA Architect > Templates, and then click CREATE TEMPLATE on the top right.

A new template page opens.

2. Enter a meaningful template name and description that describes the template. It's common for customers to use "Gold" templates (backup policies) to protect tier 1 applications with RPO of less than an hour. "Silver" to protect tier 2 applications that have RPO needs between 1 to 12 hours and so on.

3. In this lab, since you're backing up the database twice a day (with hourly log backups), call your template DB-Gold.

4. Next click the + button between the production and snapshot box (or click the + Add button next to Snapshot label under the Policies section.

The Production To Snapshot page opens.

5. Give the backup policy a meaningful name. Call it Snap every 12 hours since it will back up every 12 hours.

6. Scheduling - Set to Continuous.

You could also define a windowed policy in case you want backups to run only within a specified window.

7. Every - Specifies how frequently you want to backup the data. Since you want to backup twice a day, set the backup frequency to "Every 12 hours"

8. Starting At - Specifies the start time at which you want the backup policy to trigger. Set the backup to trigger at 6 AM and then every 12 hours from there.

9. Retain For - Specifies how long backups are retained. Set to 7 days. All backup copies in the local storage (snapshot pool) will expire after 7 days.

10. Leave the other defaults as is.

11. Click Advance Policy Settings. This opens the Policy Settings popup.

In the policy settings, set:

• Application Consistent to Take application consistent backup
• Backup SQL Server User Logins to Yes
• Enable Database Log Backup to Yes
• Set RPO (Minutes) to 60
• Log Backup Retention Period to 7
• Replicate Logs (Uses StreamSnap Technology) to No
• Send Logs to OnVault Pool to No. You would set to yes if you wanted to send the log backups to Cloud Storage NearLine/ColdLine.

12. Click Save Changes on the Policy Settings popup.

13. Click Update Policy. This will take you back to the previous Templates page.

14. Click Save Template.

You just created/defined a template with a policy that will backup the database every twelve hours (and log every hour) and retain them for 7 days.

Creating a profile

In the previous section, you defined a backup policy that dictates how frequently to back the data and its retention period. You haven't defined where backups should be stored. You will do that by defining Profiles.

In this section, you create a profile which dictates where backups are stored.

1. Navigate to SLA Architect > Profiles menu on the Actifio Global Manager (AGM).
2. Once on the Profiles page, click CREATE PROFILE.

The Create New Profile dialog opens.

3. Give the profile a meaningful name, LocalStorage, with a description of "This will store backups locally in a snapshot pool".

4. For the appliance select the skybasecentos7.... appliance. There is only one.

5. For "Snapshot Pool" - select act_per_pool000.

Leave everything else at their default value.

6. Click Save Profile.
7. Navigate again to SLA Architect > Profiles and check if you can see the profile "LocalStorage" that was just created.

You just created/defined a profile that dictates where backups are stored.

This profile, together with the template created in the previous section, will dictate:

• How to backup data
• How frequently to back your data
• Where backups are stored
• How long should backups are retained

Now you just apply the template and profile you created to any data source to automatically back that data source based on the backup definition.

Click Check my progress below to check your lab progress. Create SLA Templates & Profiles

Task 5. Backing up the ACTIFIO-MSSQL database server

To discover and protect the Microsoft SQL Server instance, trigger the SQL Server backup wizard.

1. Navigate to the "Backup & Recover > Backup" menu on the AGM.

This will open up the "Select the type of application you wish to add or protect" page with all the Actifio GO supported databases & application types.

2. Click on SQL Server icon as shown in the screen below:

This will open up the Microsoft SQL Server backup wizard as shown below.

Since AGM doesn't yet know the information about the host running Microsoft SQL Server instance, it shows a "No host found" message.

3. Go ahead and add sqlserver (which has a SQL server instance running on it) as a host by clicking the + Add Host button. See the screen above.

4. In the Add Host popup, enter:

   • Name: Enter "sqlserver" which is the GCE instance name on which SQL Server instance is running. You could enter anything, but for easy identification just use the Compute Engine instance name as is.

   • IP Address: Enter the internal IP address of this VM instance and hit the "+" button. In this case it's "10.128.0.2". Double check the internal IP address of the "sqlserver" instance on the "Compute Engine > Instance" page on Google Cloud Console page.

   Note: Click the plus icon after entering the IP address.
   • Appliances: Select the available sky server.

5. Leave other details as is and click the Add button at the bottom of the popup as shown in the screen below.

   

Once the host is added, it will get listed as shown below.

Click Check my progress below to check your lab progress. Verify that the SQLSERVER host has been added

6. Now, click on the Next button.

This will trigger discovery of Microsoft SQL Server instance on the host sqlserver. Once the discovery is complete, all the discovered SQL Server instances would be listed.

7. Select the discovered ACTIFIO-MSSQL SQL Server instance and click on the Next button as shown in the below screenshot.

   

8. Now, select the ACTIFIO-MSSQL SQL Server instance and then select Apply SLA. Once you select Apply SLA, a dropdown to choose Template will appear.

9. Select "DB-Gold", and for the Profile select "LocalStorage".

10. Click the OK button.

    Remember the template and profile that was created in the previous section which together defines a backup policy? You are now assigning the backup policy to this SQL Server instance.

    

11. You can hover on the preview column to see the preview of the backup schedule and retention period for the applied DB-Gold template. See the below screen.

    

12. Click on the Next button (at the bottom right) which will advance the wizard to the settings page as shown below.

    

To configure any SQL server backup specific settings, you can make use of the Application Settings link. In this lab, you will use the defaults and not change any settings.

13. So, click the Next button to view the summary page.

14. Click the Finish button as shown below.

    Note: You would get a popup warning not to navigate to another page unless the operation completes.

15. Click the Finish button again as shown below.

    

    Once the operation completes, you would see the status column set to green tick mark (as shown below) indicating that the ACTIFIO-MSSQL instance is now protected with the desired backup policy.

    

    You just discovered and protected your Microsoft SQL Server instance with the DB-Gold policy that you defined in the previous section. Remember the backup policy would backup the database every 12 hours and logs every 1 hour. And those backups will be stored locally for 7 days.

    Note: Since you defined a continuous policy, the first backup gets triggered automatically after the SLA template and profiles are attached/applied to any application object.

16. To verify the same, navigate to the Monitor > Jobs page and you will see that a backup job would be running as shown in the below screen.

17. If you don't see any job in running state, then wait for a few seconds and refresh the page.

18. Wait for the backup job to finish. It would take about a couple of minutes. Once finished, it would disappear. Alternatively, you could make use of the "Status" filter from the left pane and also select "Succeeded" so that you can view jobs in either running or succeeded state.

​​

Click Check my progress below to check your lab progress. Back up ACTIFIO-MSSQL database server

Task 6. Triggering on-demand backup

To trigger an on-demand backup:

1. Navigate to App Manager > Applications page.

2. Select the desired database instance from the list. For this lab, select the ACTIFIO-MSSQL server instance.

3. Right click and select Manage SLA from the action menu or click on the Manage SLA.

4. Under Policies select what you want to trigger the on-demand backup. In this case, choose Snapshot > Snap every 12 hours.

5. Select what you would like to be included in the backup. For this lab, select the DB + LOG to backup both DB and Log.

6. Enter a meaningful label for the Label field and click the Run SLA button. You will get a Backup started successfully message.

7. Click Okay.

You just triggered an on-demand backup for your database application.

8. To view/monitor the backup job progress, navigate to the Monitor > Jobs page on the AGM. You will see an on-demand backup job in progress.

9. Click the job ID to see the job details.

Click Check my progress below to check your lab progress. Trigger On-Demand Backup

Viewing backups

To view all backups available for a given application:

1. Navigate to App Manager > Applications.
2. Select ACTIFIO-MSSQL.
3. Right click and select Access from the action menu item. Alternatively, you could also click on the chevron next to the Manage SLA button at the bottom right of the page and select Access.

This will present a guitar view (a.k.a swim lanes) as shown below. You can view all the available backups in the local snapshot pool or OnVault (Cloud Storage) for the respective application.

The image details tile on the right presents image details like backup image name, size, its expiry date, recovery range for DB log roll forward and so on.

Task 7. Recovering a database from a backup image

1. From the Access page, select the desired point in time backup image for this ACTIFIO-MSSQL server.

Note: Every bubble on the lane represents a PIT backup image available for the application on the respective storage. And, if you have multiple PIT backup images around a similar time, each of those images will be represented by a smaller bubble on top of the bigger bubble.

Since you also took an on-demand backup, you can see two smaller bubbles. You will pick from one of the available PIT backup images. Ignore "Dedup" and "Remote Dedup" lanes as they are not supported on Actifio GO.

2. Once the image is selected, the image tile on the right will display relevant image details.
3. Click on Mount.

Note: If you want to do a traditional restore of the data, click the "chevron" icon next to "Mount" and select the "Restore" option as shown in the screen above. "Restore" lifts and shifts the entire data back to the source from where it was captured. The amount of time taken for a restore operation to complete depends on the size of data to be restored, network throughput, and disk performance.

This lab focuses on using the most frequently used "Mount" option to quickly recover the data. Data can be recovered in minutes to reduce RTO time as there is no movement of data.

4. Once on the Mount screen, select sqlserver as target. You can mount the backup image on any target server where you want to recover the data. For simplicity, in this lab, you will recover the database back on the source server but as a different database.
5. Provide a meaningful label in the label field. In this lab, "qwiklab demo".
6. Select the AdventureWorks2017 database. Once you select the database, additional options display.
7. The SQL Server Instance Name field is auto populated. This is because you are mounting the backup image on the same source server from which the back was taken - which is already known to AGM. You could mount the backup image to any target server by selecting the appropriate target host and providing the correct SQL Server instance name running on that host.
8. For the SQL Server Database Name - set to "Recovered_AdventureWorks2017" for this lab.

9. Leave other values at their default and click Submit. This triggers a mount job behind the scenes.

10. When successful, click Okay.

11. Now, navigate to Monitor > Jobs page. You will see a mount job running. Wait for a few seconds and the mount job will complete.

13. Now RDP back into the SQLSERVER Compute Engine instance and refresh the object explorer pane in the SQL Server Management Studio. You will see the new database Recovered_AdventureWorks2017 appear as shown below.

You just recovered your AdventureWorks2017 database in a matter of seconds. You can query the recovered database just like any other database.

Click Check my progress below to check your lab progress. Recover "AdventureWorks2017" Database from a backup image

Congratulations!

You just learned how to backup and recover a Microsoft SQL Server with Actifio.

Manual last updated January 24, 2024

Lab last tested January 24, 2024

Copyright 2024 Google LLC All rights reserved. Google and the Google logo are trademarks of Google LLC. All other company and product names may be trademarks of the respective companies with which they are associated.