> [!CAUTION]
> **Caution:** Support for backing up and restoring workloads managed using the legacy appliance management console is deprecated. For more information, see [Feature deprecations](https://docs.cloud.google.com/backup-disaster-recovery/docs/deprecations.md.txt) in the Backup and DR documentation.

Backup and DR supports Windows server application types that include Microsoft
SQL Server, SMB, and local file systems. Before you can discover and back up
data from these hosts, you must do the following:

- [Install the Backup and DR agent on Windows host](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/windows-agent)

- Add the Windows host

## Add Windows host

If you have added the Windows server to Backup and DR as a Compute Engine
instance or as a VMware VM, then a host for this VM already exists and you don't
need to add it again using the following procedure.
Instead, find and edit that host and proceed from [step 7](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/discover-windows-server.md.txt#step7).

Use the following instructions to add a new Windows Server host to appliance management console:

1. Click **Manage** \> **Hosts**.

2. Select **+ Add Host**.

3. In the **Add Host** form, enter the name and an optional friendly name.
   The name of a host should start with a letter, and can contain letters
   and digits (0-9). Underscore ('_') characters are not valid in host names.

4. Enter the IP address of the host in **IP Address** . Click the **plus sign (+)**
   to add it.

5. In the **Appliances** section, select the appliance management console managed
   appliances that serve this host. If the list is long, you can use the search
   field to find a specific appliance or group of appliances.

6. Leave **Host Type** as **Generic**.

7. Enter **Application Discovery Credentials** to discover and protect the
   database applications on the host. This field is applicable only for
   MaxDB, PostgreSQL, SAP ASE, and SAP IQ databases.

8. In the Backup and DR agent settings, complete the following:

   - The Backup and DR agent port is normally port 5106. If it is anything else,
     enter the port number here.

   - If there are CIFS shares that need to be discovered you must supply a
     username and password that can access those CIFS shares.

   - You must supply the secret key generated on the Windows host using the
     instructions
     [Install the Backup and DR agent on a Windows host](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/windows-agent)
     or [Regenerate the secret key](https://docs.cloud.google.com/backup-disaster-recovery/docs/configuration/windows-agent#regenerate)
     section. You can add the secret key now or later using the [Add a secret key](https://docs.cloud.google.com/backup-disaster-recovery/management-console/configuration/discover-windows-server.md.txt#add)
     instructions but before running the application discovery.

9. Click **Add**.

### Add a secret key

If you want to update the secret key or if you did not add the secret key for
the first time, you can add it in the Windows host using the following
instructions.

1. Click **Manage** and then select **Hosts**.

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

3. Scroll to **Backup and DR Agent Settings** section and find the
   **Secret** field.

4. Paste the secret key that you saved earlier in the **Secret** field
   and click **Save** . Ensure the certificate status changes to **Valid**.

## Find logs and scripts on Windows server hosts

On a Microsoft Windows server host, UDSAgent.logs are stored in
`C:\Program Files\Google Cloud Backup and DR\log`

You can create scripts to perform pre- and post- actions on applications on your
Windows hosts. Create a new folder in which to store all scripts:
`C:\Program Files\Google Cloud Backup and DR\scripts`.

> [!NOTE]
> **Note:** The Backup and DR agent can be firewalled out if the host joins a domain after the Backup and DR agent has been installed. If this happens, uninstall and then re-install the Backup and DR agent.

## Discover local file system

Use these instructions to add local file systems, you must do the following:

1. Discover the local file system in either of these ways:

   - Go to **Back up \& Recover** and select **Back up**.

   - Go to **App Manager** , click **Applications** , and then select
     **Add application**.

2. Select the **All Apps** tile. If you select the **All Apps** tile you
   also discover Microsoft SQL Server apps.
   After the local file systems are discovered, you can find them using the
   file system filter in the **Applications** page.

## Service access point IP address for cluster support

If a file system is a cluster resource and if you want it to be backed up
irrespective of which cluster node is hosting the file system, specify the
Cluster resource IP address as a Service Access Point IP. This allows the
backup/recovery appliance to connect to the Backup and DR agent using the
cluster resource IP and to back up the file system from the active cluster node.
For backup to work correctly across all cluster nodes, the Backup and DR agent
must be installed on all cluster nodes.