Backup and DR agent on Windows hosts

This page describes how to install the Backup and DR agent on a Windows host and perform other operations such as check the status of your backup, restart, and uninstall the Backup and DR agent.

How it works

The Backup and DR agent for Microsoft Windows runs as a Windows service under the Local System account. The Backup and DR agent writes logs to a log file in its installation directory. For Microsoft Windows Server, the installer comes in connector-Win32-<version>.exe format.

When you install the Windows Backup and DR agent, you have the option to install the Change Tracking Driver. If you intend to protect Microsoft SQL Server applications, install the Backup and DR agent with the Change Tracking Driver to enable efficient incremental backups.

Microsoft SQL Server is supported on NTFS and ReFS volumes. The Change Tracking Driver doesn't support SMB volumes.

After you install the agent, you need to initialize trusted communications between the backup/recovery appliance and the Backup and DR agent. This only needs to be done once. The secret key needs to be added within two hours of being generated. If the secret key expires, you need to generate a new key.

Install the Backup and DR agent on a Windows host

To install the Backup and DR agent on a Windows host, use the following instructions:

  1. Download the Windows Backup and DR agent from the Obtain the right Backup and DR agent for your host section.

  2. Log on to the host as a user with the Administrator account type.

  3. If this is a Compute Engine instance, you need to ensure the iSCSI initiator is started and also ensure it auto-starts upon reboot. To do this, launch the iSCSI Initiator application using the steps below.

    1. Click the Start Menu.

    2. Type in iSCSI Initiator to find the application.

    3. Launch the process.

    4. When prompted to enable iSCSI, click Yes.

      The iSCSI Initiator page appears. To close it, click OK.

  4. Copy the installer file to your Windows server.

  5. Launch connector-win32-version.exe.

  6. Click Run and follow the setup wizard instructions.

  7. Select the designated location where you want to install the agent and click Next.

  8. If you intend to protect SQL Server databases, select Backup and DR agent with Change Tracking Driver and click Next.

  9. Select the Add windows Firewall rules to enable communication on the default port (5106) checkbox and click Next.

  10. Click Install.

  11. After you install the agent, a secret key is displayed. Save the key in a notepad or editor and click Next. You need to add this in the Backup and DR agent section of Add Windows host. This secret key is valid for 2 hours.

  12. Click Finish.

Check Backup and DR agent status

After the agent is installed, you can verify its status on the Windows hosts.

Verify the agent is running

To verify that the Backup and DR agent is running, run the following command on the host. This opens up the Microsoft Management Console (MMC) snap-in for Services.

  1. Run the following command:

    services.msc
    
  2. Verify the following services are both in the Running status with Automatic startup type:

    • Google Cloud Backup and DR agent

    • Google Cloud Backup and DR CBT agent

Install the Backup and DR agent from the Windows command prompt

To install the Backup and DR agent from a script or from a Windows command prompt, use the following instructions.

  1. Open a Windows Command prompt using the Run as administrator option.

  2. Run the following command from the directory where you copied the agent installer file.

    connector-Win32-version.exe /SUPPRESSMSGBOXES /NORESTART /VERYSILENT /TYPE=FULL
    

Regenerate the secret key

The secret key that is generated in the Install the Backup and DR agent on a Windows host section is valid only for two hours. You need to add it to the management console within this timeframe or generate a new one.

To generate a new key and add it to the management console, use the following instructions:

  1. Open a Windows Command prompt using the Run as administrator option.

  2. Change to the install directory. By default, the command would be cd C:\Program Files\Google Cloud Backup and DR:

    • To reset the secret key after confirmation the action, run the following command:

        UDSAgent secret --reset
      
    • To reset the secret immediately without confirmation, run the following command:

        UDSAgent secret --reset --restart
      
  3. Save the secret key in a notepad or in editor. This secret key is valid for two hours.

Restart the Backup and DR agent on a Windows host

To restart the Backup and DR agent on a Windows host use the following instructions:

  1. Open services.msc on the host.

  2. Select Google Cloud Backup and DR agent and click Restart.

Uninstall the Backup and DR agent

To uninstall the Backup and DR agent, use the following instructions:

  1. Open a Windows Command prompt using the Run as administrator option.

  2. Go to the c:\Program Files\Google Cloud Backup and DR folder created during the installation.

  3. Select and double-click the uninstaller executable: unins000.exe

  4. Click Yes to confirm and then click OK to finish.

Uninstall the Backup and DR agent from command prompt

To uninstall the Backup and DR agent using a script or from a command prompt, use the following instructions.

  1. Open a Windows Command prompt using the Run as administrator option.

  2. Run the following command.

          "C:\Program Files\Google Cloud Backup and DR\unins000.exe" /VERYSILENT /NORESTART /SUPPRESSMSGBOXES
    

Add a secret key

If you want to update the secret key or didn't add the secret key the first time, you can add in the Windows host using the following instructions:

  1. Go to management console, select Manage and then select Hosts.

  2. Right-click the Windows host and choose Edit.

  3. Go to the Backup and DR agent Settings section and find the Secret text box.

  4. Paste the secret key that you saved earlier in the Secret text box and click Save. Ensure the Certificate status changes to Valid.

What's next