Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Rapid Recovery 6.0.2 - User Guide

*** Legend Introduction to Dell Data Protection | Rapid Recovery Understanding the Rapid Recovery Core Console Working with repositories Managing Rapid Recovery Core settings Using custom groups Working with encryption keys Protecting machines using the Rapid Recovery Core Working with Microsoft Exchange and SQL Servers Protecting server clusters Exporting protected data to virtual machines Managing protected machines Understanding replication Managing events Generating and viewing reports Restoring data Understanding bare metal restore for Windows machines Retention and archiving Managing cloud accounts Working with Linux machines Understanding the Local Mount Utility Central Management Console Understanding the Rapid Recovery Command Line Management utility Understanding the Rapid Recovery PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets Localization Qualifiers
Extending Rapid Recovery jobs using scripting Rapid Recovery APIs Glossary

Protecting multiple machines on a VMware vCenter/ESX(i) virtual host

Use this procedure to simultaneously protect one or more machines on a VMware vCenter/ESX(i) virtual host.

CAUTION:
If you use agentless protection, Dell recommends that you limit protection to no more than 200 VMs at once. For example, do not select more than 200 VMs when using the Protect Multiple Machines Wizard. Protecting more than 200 VMs results in slow performance. There is no limit to how many VMs a Core can agentlessly protect over time. For example, you could protect 200 VMs today and another 200 VMs tomorrow.
  1. On the Rapid Recovery Core Console, click the Protect drop-down menu, and then click Protect Multiple Machines.
    The Protect Multiple Machines Wizard opens.
  2. On the Welcome page, select one of the following options:
    • Typical
    • Advanced (show optional steps)
  3. Click Next.
  4. On the Connection page of the wizard, from the Source drop-down list, select vCenter / ESX(i).
  5. Enter the host information and logon credentials as described in the following table.
    Table 1. vCenter/ESX(i) connection settings
    Text Box Description
    Host The name or IP address of the VMware vCenter Server/ESX(i) virtual host.
    Port The port used to connect to the virtual host.

    The default setting is 443.

    User name The user name used to connect to the virtual host; for example, Administrator or, if the machine is in a domain, [domain name]\Administrator.
    Password The secure password used to connect to this virtual host.
  6. On the Select Machines page, select one of the following options from the drop-down menu:
    • Hosts and Clusters
    • VMs and Templates
  7. Expand the list of machines and select the VMs you want to protect.
    A notification appears if Rapid Recovery detects that a machine is offline or does not have VMware Tools installed.
  8. Click Next.
  9. On the Adjustments page, enter the credentials for each machine in the following format: hostname::username::password.
    Note: Enter one machine on each line.
  10. Click Next.
    If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 14.

    If the Agent software is not yet deployed to the machines you want to protect, or if any of the machines you specified cannot be protected for another reason, then the selected machines appear on the Warnings page.

  11. Optionally, on the Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
  12. Optionally, on the Warnings page, select After Agent installation, restart the machines automatically.
    Note: Dell recommends this option. You must restart agent machines before they can be protected.
  13. If the status indicates that the machine is reachable, click Next to install the agent software.
    The Protection page appears.
  14. On the Protection page, select the appropriate protection schedule as described below.
    • If you want to use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes).
    • If you want to define a different protection schedule, then in the Schedule Settings option, select Custom protection.
  15. Proceed with your configuration as follows:
    • If you selected a Typical configuration for the Protect Machine Wizard and specified default protection, then click Finish to confirm your choices, close the wizard, and protect the machine you specified.

      The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

    • If you selected a Typical configuration for the Protect Machine Wizard and specified custom protection, click Next to set up a custom protection schedule. For details on defining a custom protection schedule, see Creating custom protection schedules.
    • If you selected Advanced configuration for the Protect Machine Wizard, and default protection, then click Next and proceed to Step 17 to see repository and encryption options.
    • If you selected Advanced configuration for the Protect Machine Wizard and specified custom protection, then click Next to set up a custom protection schedule. For details on defining a custom protection schedule, see Creating custom protection schedules.
  16. Click Next.
  17. On the Repository page, do one of the following:
    • If you already have a repository and want to store the data from this machine for protection in the existing repository, then do the following:
      1. Select Use an existing repository.
      2. Select an existing repository from the list.
      3. Click Next.

      The Encryption page appears. Skip to Step 18 to optionally define encryption.

    • If you want to create a repository, select Create a Repository, and then complete the following steps.
      1. On the Repository, enter the information described in the following table.
        Table 2. Add New Repository settings
        Text Box Description
        Repository Name Enter the display name of the repository.

        By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.

        Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.

        Concurrent Operations Define the number of concurrent requests you want the repository to support. By default the value is 64.
        Comments Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. For example, type DVM Repository 2.
      2. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
        CAUTION:
        Define a dedicated folder within the root for the storage location for your repository. Do not specify the root location. For example, use E:\Repository\, not E:\. If the repository that you are creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss.

        The Add Storage Location dialog box appears.

      3. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
      4. In the Storage Location area, specify how to add the file for the storage location. You can choose to add a locally attached storage volume (such as direct attached storage, a storage area network, or network attached storage). You could also specify a storage volume on a Common Internet File System (CIFS) shared location.
        • Select Add file on local disk to specify a local machine, and then enter the information as described in the following table.
          Table 3. Local disk settings
          Text Box Description
          Data path Enter the location for storing the protected data.

          For example, type X:\Repository\Data.

          When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

          Metadata path Enter the location for storing the protected metadata.

          For example, type X:\Repository\Metadata.

          When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

        • Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table.
          Table 4. CIFS share credentials
          Text Box Description
          UNC path Enter the path for the network share location.

          If this location is at the root, define a dedicated folder name (for example, Repository).

          The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

          User name Specify a user name for accessing the network share location.
          Password Specify a password for accessing the network share location.
      5. In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table.
        Table 5. Storage configuration details
        Text Box Description
        Size Set the size or capacity for the storage location. The minimum size is 1 GB. The default is 250 GB. You can choose from the following:
        • GB
        • TB
          Note: The size that you specify cannot exceed the size of the volume.

          If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB.

          If the storage location is a NTFS volume using Windows 8, 8.1, Windows 10, or Windows Server 2012, 2012 R2, the file size limit is 256 TB.

          Note: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
        Write caching policy The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

        Set the value to one of the following:

        • On
        • Off
        • Sync

          If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

          Note: Setting the write caching policy to On could result in faster performance. If you are using Windows Server 2008 SP2 or Windows Server 2008 R2 SP2, the recommended setting is Off.

          If set to Off, Rapid Recovery controls the caching.

          If set to Sync, Windows controls the caching as well as the synchronous input/output.

        Bytes per sector Specify the number of bytes you want each sector to include. The default value is 512.
        Average bytes per record Specify the average number of bytes per record. The default value is 8192.
      6. Click Next.
    If you chose the Advanced option in Step 1, the Encryption page appears.
  18. Optionally, on the Encryption page, to enable encryption, select Enable Encryption.

    Encryption key fields appear on the Encryption page.

    Note: If you enable encryption, it will be applied to data for all protected volumes for this agent machine.

You can change the settings later from the Configuration tab in the Rapid Recovery Core Console.

For more information about encryption, see the topic Working with encryption keys.
    CAUTION:
    Rapid Recovery uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys. While using encryption is optional, Dell highly recommends that you establish an encryption key, and that you protect the passphrase you define. Store the passphrase in a secure location as it is critical for data recovery. Without a passphrase, data recovery is not possible.
  19. If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, select Encrypt data using an existing Encryption key, and select the appropriate key from the drop-down menu.

    Proceed to Step 21.

  20. If you want to add a new encryption key to the Core and apply that key to these protected machines, then enter the information as described in the following table.
    Table 6. Encryption key settings
    Text Box Description
    Name Enter a name for the encryption key.

    Encryption key names must contain between 1 and 130 alphanumeric characters. You may not include special characters such as the back slash, forward slash, pipe, colon, asterisk, quotation mark, question mark, open or close brackets, ampersand or hash.

    Description Enter a comment for the encryption key.

    This information appears in the Description field when viewing encryption keys from the Core Console.

    Passphrase Enter the passphrase used to control access.

    Best practice is to avoid special characters listed above.

    Record the passphrase in a secure location. Dell Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase.

    Confirm Passphrase Re-enter the passphrase you just entered.
  21. Click Finish to save and apply your settings.
  22. If the Warning page appeared and you are still satisfied with your selections, click Finish again.
The Rapid Recovery Agent software is deployed to the specified machines, if necessary, and the machines are added to protection on the Core.

Was this topic helpful?

[Select Rating]



Protecting multiple machines manually

Use this procedure to manually enter each machine that you want to protect.

  1. On the Rapid Recovery Core Console, click the Protect drop-down menu, and then click Protect Multiple Machines.
    The Protect Multiple Machines Wizard opens.
  2. On the Welcome page, select one of the following options:
    • Typical
    • Advanced (show optional steps)
  3. Click Next.
  4. On the Connection page of the wizard, from the Source drop-down list, select Manually.
  5. Click Next.
  6. On the Select Machines page, enter the machine details in the dialog box in the format hostname::username::password::port. Examples include:
    10.255.255.255::administrator::&11@yYz90z::8006
    abc-host-00-1::administrator::99!zU$o83r::168
  7. Click Next.
    If the Protection page appears next in the Protect Multiple Machines Wizard, skip to Step 11.

    If the Agent software is not yet deployed to the machines you want to protect, or if any of the machines you specified cannot be protected for another reason, then the selected machines appear on the Warnings page.

  8. Optionally, on the Machines Warnings page, you can verify any machine by selecting the machine and then clicking Verify in the toolbar.
  9. Optionally, on the Machines Warnings page, select After Agent installation, restart the machines automatically.
    Note: Dell recommends this option. You must restart agent machines before they can be protected.
  10. If the status indicates that the machine is reachable, click Next to install the agent software.
    The Protection page appears.
  11. On the Protection page, select the appropriate protection schedule as described below.
    • If you want to use the default protection schedule, then in the Schedule Settings option, select Default protection (hourly snapshots of all volumes).
    • If you want to define a different protection schedule, then in the Schedule Settings option, select Custom protection .
  12. Proceed with your configuration as follows:
    • If you selected a Typical configuration for the Protect Machine Wizard and specified default protection, then click Finish to confirm your choices, close the wizard, and protect the machine you specified.

      The first time protection is added for a machine, a base image (that is, a snapshot of all the data in the protected volumes) will transfer to the repository on the Rapid Recovery Core following the schedule you defined, unless you specified to initially pause protection.

    • If you selected a Typical configuration for the Protect Machine Wizard and specified custom protection, click Next see Creating custom protection schedules.
    • If you selected Advanced configuration for the Protect Machine Wizard, and default protection, then click Next and proceed to Step 14 to see repository and encryption options.
    • If you selected Advanced configuration for the Protect Machine Wizard and specified custom protection, click Next, to set up a custom protection schedule. For details on defining a custom protection schedule, see Creating custom protection schedules.
  13. On the Repository page, the following:
    • If you already have a repository and want to store the data from this machine for protection in the existing repository, then do the following:
      1. Select Use an existing repository.
      2. Select an existing repository from the list.
      3. Click Next.

      The Encryption page appears. Skip to Step 19 to optionally define encryption.

    • If you want to create a repository, select Create a Repository, and then complete the following steps.
      1. On the Repository, enter the information described in the following table.
        Table 1. Add New Repository settings
        Text Box Description
        Repository Name Enter the display name of the repository.

        By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.

        Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.

        Concurrent Operations Define the number of concurrent requests you want the repository to support. By default the value is 64.
        Comments Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. For example, type DVM Repository 2.
      2. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
        CAUTION:
        Define a dedicated folder within the root for the storage location for your repository. Do not specify the root location. For example, use E:\Repository\, not E:\. If the repository that you are creating in this step is later removed, all files at the storage location of your repository are deleted. If you define your storage location at the root, all other files in the volume (e.g., E:\) are deleted, which could result in catastrophic data loss.

        The Add Storage Location dialog box appears.

      3. Click Add Storage Location to define the specific storage location or volume for the repository. This volume should be a primary storage location.
      4. In the Storage Location area, specify how to add the file for the storage location. You can choose to add a locally attached storage volume (such as direct attached storage, a storage area network, or network attached storage). You could also specify a storage volume on a Common Internet File System (CIFS) shared location.
        • Select Add file on local disk to specify a local machine, and then enter the information as described in the following table.
          Table 2. Local disk settings
          Text Box Description
          Data path Enter the location for storing the protected data.

          For example, type X:\Repository\Data.

          When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

          Metadata path Enter the location for storing the protected metadata.

          For example, type X:\Repository\Metadata.

          When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.

        • Or, select Add file on CIFS share to specify a network share location, and then enter the information as described in the following table.
          Table 3. CIFS share credentials
          Text Box Description
          UNC path Enter the path for the network share location.

          If this location is at the root, define a dedicated folder name (for example, Repository).

          The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.

          User name Specify a user name for accessing the network share location.
          Password Specify a password for accessing the network share location.
      5. In the Storage Configuration area, click More Details and enter the details for the storage location as described in the following table.
        Table 4. Storage configuration details
        Text Box Description
        Size Set the size or capacity for the storage location. The minimum size is 1 GB. The default is 250 GB. You can choose from the following:
        • GB
        • TB
          Note: The size that you specify cannot exceed the size of the volume.

          If the storage location is a New Technology File System (NTFS) volume using Windows XP or Windows 7, the file size limit is 16 TB.

          If the storage location is a NTFS volume using Windows 8, 8.1, Windows 10, or Windows Server 2012, 2012 R2, the file size limit is 256 TB.

          Note: For Rapid Recovery to validate the operating system, Windows Management Instrumentation (WMI) must be installed on the intended storage location.
        Write caching policy The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations.

        Set the value to one of the following:

        • On
        • Off
        • Sync

          If set to On, which is the default, Windows controls the caching. This is appropriate for Windows 10, and for versions of Windows Server 2012 and later.

          Note: Setting the write caching policy to On could result in faster performance. If you are using Windows Server 2008 SP2 or Windows Server 2008 R2 SP2, the recommended setting is Off.

          If set to Off, Rapid Recovery controls the caching.

          If set to Sync, Windows controls the caching as well as the synchronous input/output.

        Bytes per sector Specify the number of bytes you want each sector to include. The default value is 512.
        Average bytes per record Specify the average number of bytes per record. The default value is 8192.
      6. Click Next.
    If you chose the Advanced option in Step 1, the Encryption page appears.
  14. Optionally, on the Encryption page, to enable encryption, select Enable Encryption.

    Encryption key fields appear on the Encryption page.

    Note: If you enable encryption, it will be applied to data for all protected volumes for this agent machine.

You can change the settings later from the Configuration tab in the Rapid Recovery Core Console.

For more information about encryption, see the topic Working with encryption keys.
    CAUTION:
    Rapid Recovery uses AES 256-bit encryption in the Cipher Block Chaining (CBC) mode with 256-bit keys. While using encryption is optional, Dell highly recommends that you establish an encryption key, and that you protect the passphrase you define. Store the passphrase in a secure location as it is critical for data recovery. Without a passphrase, data recovery is not possible.
  15. If you want to encrypt these protected machines using an encryption key that is already defined on this Rapid Recovery Core, select Encrypt data using an existing Encryption key, and select the appropriate key from the drop-down menu.

    Proceed to Step 17.

  16. If you want to add a new encryption key to the Core and apply that key to these protected machines, then enter the information as described in the following table.
    Table 5. Encryption key settings
    Text Box Description
    Name Enter a name for the encryption key.

    Encryption key names must contain between 1 and 130 alphanumeric characters. You may not include special characters such as the back slash, forward slash, pipe, colon, asterisk, quotation mark, question mark, open or close brackets, ampersand or hash.

    Description Enter a comment for the encryption key.

    This information appears in the Description field when viewing encryption keys from the Core Console.

    Passphrase Enter the passphrase used to control access.

    Best practice is to avoid special characters listed above.

    Record the passphrase in a secure location. Dell Support cannot recover a passphrase. Once you create an encryption key and apply it to one or more protected machines, you cannot recover data if you lose the passphrase.

    Confirm Passphrase Re-enter the passphrase you just entered.
  17. Click Finish to save and apply your settings.
    The wizard closes.
  18. If the Warning page appeared and you are still satisfied with your selections, click Finish again.
The Rapid Recovery Agent software is deployed to the specified machines, if necessary, and the machines are added to protection on the Core.

Was this topic helpful?

[Select Rating]



Monitoring the protection of multiple machines

You can monitor the progress as Rapid Recovery applies the protection polices and schedules to the machines.

In the Rapid Recovery Core Console, navigate to the Rapid Recovery Home page and then click [Events] (Events).

The Events page displays, broken down by Tasks, Alerts, and Events. As volumes are transferred, the status, start times, and end times display in the Tasks pane.

You can also filter tasks by status (active, waiting, completed, queued, and failed). For more information, see Viewing tasks.

Note: To only see tasks that are waiting to be performed, make sure that you select the Waiting Tasks icon.

As each protected machine is added, an alert is logged, which lists whether the operation was successful or if errors were logged. For more information, see Viewing alerts.

For information on viewing all events, see Viewing all events.


Was this topic helpful?

[Select Rating]



Understanding agentless protection

By installing the Rapid Recovery Agent software, you can protect physical or virtual machines on the Rapid Recovery Core. The supported operating systems are indicated in system requirements in the topic "Rapid Recovery Agent software requirements."

Rapid Recovery now offers another approach for protecting machines.

The Rapid Snap for Virtual feature of Rapid Recovery lets you protect virtual machines (VMs) on a VMware ESXi host without installing the Rapid Recovery Agent software.

To protect a VM without the Rapid Recovery Agent, the Rapid Recovery Core works with the snapshot technology native to VMware.

Rapid Recovery agentless protection uses the ESXi agent client and the existing application program interface (API) to protect selected VMs on a single host without installing Rapid Recovery Agent software. The Rapid Recovery Core then communicates with the virtual machine disk (VMDK) to determine the necessary details of the protected volumes. Because Rapid Recovery creates recovery points based on volumes, not VMDKs, each volume can be separately mounted, restored, and exported.

Note: Rapid Recovery recommends that VMware Tools be installed on virtual machines (VMs) you want to protect on vSphere or ESXi hosts. When VMware Tools are installed on a VM using a Windows operating system (OS), the backups that the Rapid Recovery Core captures use Microsoft Volume Shadow Services (VSS). For information on the behavior of agentless VMs with or without VMware Tools, see Benefits of installing VMware Tools for agentless protection.

Agentless protection also uses VMware Changed Block Tracking (CBT) to reduce the time needed for incremental snapshots. CBT determines which blocks changed in the VMDK file, letting Rapid Recovery back up only the portions of the disk that have changed since the last snapshot. This backup method often results in shorter backup operations and reduced resource consumption on network and storage elements.

There are multiple benefits to using agentless protection. Some of the most useful attributes include the following characteristics:

  • No additional software is required on the host machine.
  • Agentless protection lets you opt to automatically protect new VMs added to the ESXi host.
  • A restart is not required during the protection process.
  • Credentials are not required for each individual VM.
  • Agentless protection lets you protect a VM even if it is powered off.
  • Agentless protection lets you restore to disks.
  • Agentless protection does not require free space on a volume during transfers.
  • Agentless protection supports all guest operating systems.
  • Agentless protection lets you export dynamic disks or volumes.
    Note: If dynamic volumes are complex (striped, mirrored, spanned, or RAID), they export as disk images and parse into volumes after the export operation completes on the exported VM.

While there are many reasons to use agentless protection for ESXi VMs, opt for the protection method that best suits your environments and business needs. Along with the previously mentioned benefits, there are also the following considerations to keep in mind when choosing agentless protection:

  • Agentless protection does not support protection of dynamic volumes (for example, spanned, striped, mirrored, or RAID volumes) at the volume level. It protects them at the disk level.
  • Agentless protection does not support Live Recovery. For more information about this feature, see Understanding Live Recovery.
  • After each restore of a single volume to the protected VM, you must restart the VM.
  • Agentless protection does not collect Microsoft SQL or Microsoft Exchange metadata.
  • You cannot perform a SQL attachability check, log truncation, or a mountability check on recovery points captured on agentless protected machines.
  • Agentless protection does not collect or display volume labels, or drive letters.
  • Agentless protection does not display the actual amount of space used on a VM if the virtual disk type is thick provision eager zeroed.

If you choose to use agentless protection for your ESXi VMs, the host must meet the following minimum requirements for agentless protection to be successful.

  • The host machine must be running ESXi version 5.0.0 build 623860 or later.
  • The host machine must meet the minimum system requirements stated in the Rapid Recovery Installation and Upgrade Guide.
  • For volume-level protection, VMDKs must include either Master Boot Record (MBR) partition tables or GUID partition tables (GPTs). VMDKs without these partition tables are protected as whole disks rather than as individual volumes.
  • Each VMware virtual machine must have VMware Tools installed to ensure snapshot consistency.
CAUTION:
Dell recommends that you limit agentless protection to no more than 200 VMs at once. For example, do not select more than 200 VMs when using the Protect Multiple Machines Wizard. Protecting more than 200 VMs results in slow performance. There is no limit to how many VMs a Core can agentlessly protect over time. For example, you could protect 200 VMs today and another 200 VMs tomorrow.

Was this topic helpful?

[Select Rating]



Related Documents