Add an Arcserve Cyber Resilient Data Store
This section provides information about how to add an Arcserve Cyber Resilient data store as a destination.
Notes:
- The Add Arcserve Cyber Resilient Data Store option is disabled for UDP 10.0. To use this option, upgrade Recovery Point Server (RPS) to UDP 10.2.
- If you have not purchased Arcserve Cyber Resilient Storage, the Add Arcserve Cyber Resilient Data Store option is disabled. If you want to request a trial for Adding Arcserve Cyber Resilient Data Store, click Try It.
- For purchase related information, contact your sales account manager. After purchasing Cyber Resilient Storage, the Add Arcserve Cyber Resilient Data Store option is enabled only after you add the Cyber Resilient Storage account. For more information, see Add an Arcserve Cyber Resilient Storage Account.
Follow these steps:
- On the Protect screen, do one of the following:
- Navigate to Destinations > Recovery Point Servers.
- From the Recovery Point Servers view, select the required recovery point server.
- From the Actions drop-down list, select Add Arcserve Cyber Resilient Data Store.
- Navigate to Destinations > Data Stores.
- On the Data Store page, click Add Data Store, and then select Add Arcserve Cyber Resilient Data Store.
- The Add Arcserve Cyber Resilient Data Store screen appears.
- Specify the following fields and click Save:
- Recovery Point Server: From the drop-down list, select the RPS as needed.
- Note: If you are adding the Arcserve Cyber Resilient data store from the Recovery Point Server view, it is selected by default.
- Data Store Name: Specifies the name of the data store.
- Concurrent Active Sources Limit to: Limits the maximum number of concurrent jobs allowed on the data store to the specified value.
- Default Value: 4
- Refers to a value from 1 to 9999. The value indicates the number of jobs that can concurrently run. If the running jobs meet the number, another job is placed into the queue and the job can only start when one of the running jobs is complete. The completed job could mean a finished, canceled, or failed job. The number applies to the Job Types but not to the Server sources. For example, number 5 indicates that five backup jobs are running. Any job scheduled after five backup jobs waits in the queue, but you can submit another job such as File System Catalog.
- If the value exceeds 16 or 32, a warning message appears indicating increased demand on hardware.
- Data Store folder: Refers to the location of the folder where the data store is created. Type in the local full path or click Browse to navigate to and select the desired local folder.
- Arcserve Cyber Resilient Account: Select the Arcserve Cyber Resilient account from the drop-down list as needed. Pool Name must match the pool name created on your Cyber Resilient Storage device.
- Note: If you have added a single Arcserve Cyber Resilient account to the Console, it is selected by default.
- Pool Name: Refers to the pool name as created in the machine hosting Arcserve Cyber Resilient data store.
- Filesystem: Refers to the Filesystem name that is created in the machine hosting the Arcserve Cyber Resilient data store.
- Port Number: Refers to the port number that is generated in the machine hosting the Arcserve Cyber Resilient data store. For more information about how to get the port number, see Mount Snapshot.
- Immutable Snapshot Schedule Frequency: Allows you to schedule daily, weekly, and monthly snapshots and set a retention period for those snapshots, ensuring the snapshots are taken regularly and remain unchangeable for a specified duration.
- Daily: Creates snapshots for a specified time each day.
- Snapshot Time: Set a time at which you want the snapshot to be taken.
- Retention Period in Days: Define how long a snapshot can be retained before it is automatically deleted.
- Note: To optimize storage consumption, Arcserve recommends that you use a retention period of less than or equal to 7 days or use weekly snapshots instead of retaining daily snapshots for more than 7 days.
- Weekly: Creates snapshots for a specified day of the week.
- Run Schedule Day: Select a specific day of the week on which you want the snapshot to be taken.
- Snapshot Time: Set a time at which you want the snapshot to be taken.
- Retention Period in Weeks: Define how long a snapshot can be retained before it is automatically deleted.
- Note: To optimize storage consumption, Arcserve recommends that you use a retention period of less than or equal to 5 weeks or use monthly snapshots instead of retaining weekly snapshots for more than 5 weeks.
- Monthly: Creates snapshots for a specified day or week of the month.
- Start Day/Week: From the drop-down list, select one of the following as needed:
- Day: Select a specific day of the month or the last day on which you want the snapshot to be taken.
- Week: Select First or Last week as needed, and then select a specific day of the week on which you want the snapshot to be taken.
- Snapshot Time: Set a time at which you want the snapshot to be taken.
- Retention Period in Months: Define how long a snapshot can be retained before it is automatically deleted.
- Note: To optimize storage consumption, Arcserve recommends that you use a retention period of less than or equal to 12 months.
- Notes:
- If you set the retention period for daily, weekly, and/or monthly immutable snapshots to be longer than the recommended limits, and then you click Save, the Recommended Retention Limit Exceeded dialog appears. If you want to go back and update settings as per the recommended values, click Adjust Schedules. Otherwise, click Confirm Schedules to proceed with the current settings.
-
- By default, the snapshot time for all the daily, weekly, and monthly schedules is set to 2 AM. If you proceed with this default snapshot time, the snapshots with lower frequency such as weekly or monthly might overlap with daily snapshots. To avoid this, Arcserve recommends that you configure different snapshot times for different frequencies (daily, weekly, and monthly).
- Enable Deduplication: Specifies that deduplication is enabled for this data store. Arcserve Cloud Console supports both types of deduplications: Source-side deduplication and Global deduplication. Source-side deduplication prevents duplicate data blocks from moving across the network from a particular agent. Global deduplication eliminates duplicate data across all client machines based on the volume cluster level. By default, the Enable Deduplication check box is selected and grayed out.
- Deduplication Block Size: By default, the deduplication block size is selected as 64 KB.
- Hash Memory Allocation:
- Specifies the amount of physical memory allocated to store hashes. This field is pre-filled with a default value. The default value is based on the following calculation:
- If the physical memory of the RPS is less than or equal to 4 GB, the default value of the Hash Memory Allocation is the same as the physical memory of the RPS.
- If the physical memory of the RPS is greater than 4 GB, Arcserve UDP calculates the available free memory. Assume that the available free memory is X GB at present. Arcserve UDP further checks the following conditions:
- If (X * 80%) > = 4 GB, the default value of Hash Memory Allocation is (X * 80%).
- If (X * 80%) 4 GB, the default value of Hash Memory Allocation is 4 GB.
- Example: Consider an RPS with 32 GB of physical memory. Assume that the operating system and other applications use 4 GB memory while creating the data store. So, the available free memory at this time is 28 GB. So the default value of Hash Memory Allocation is 22.4 GB (22.4 GB = 28 GB * 80%).
- Hash destination is on a Solid State Drive (SSD): Specifies that the hash folder is on a solid state drive.
- Note: Configure the hash destination on local SSD if the Hash destination is on a Solid State Drive (SSD) check box is selected.
- Index Destination: Defines the index destination folder to store the index files. Select a different disk to improve the deduplication processing.
- Note: The Index Destination path must be an empty folder.
- Hash Destination: Defines the path to store the hash database. Arcserve Cloud Console uses the SHA1 algorithm to generate the hash for source data. The hash database manages the hash values. Selecting a high-speed Solid State Drive (SSD) increases the deduplication capacity and requires a lower memory allocation. For better hash performance, we recommend formatting the SSD volume as NTFS file system with 4 KB volume cluster size.
- Note: The Hash Destination path must be an empty folder.
- Notes:
- You cannot specify the same path for the following folders: Data Store folder, Index Destination, and Hash Destination.
- Remote or network share paths are not supported for Arcserve Cyber Resilient data stores.
- Enable Compression: Specifies that the data compression settings are enabled.
- Compression Type: Specifies whether to use the Standard or Maximum as the compression type.
- Compression is often selected to decrease the usage of the disk space, but this can negatively impact backup speeds due to increased CPU usage. Based on your requirement, you can select one of the three available options.
- Enable Encryption: Specifies that encryption settings are enabled. When you select this option, you must specify and confirm the encryption password.
- Data encryption is the translation of data into a form that is unintelligible without a deciphering mechanism. The Arcserve UDP solution uses secure AES (Advanced Encryption Standard) encryption algorithms to achieve maximum security and privacy of your data. For data stores, encryption or No encryption is supported. For encryption, only AES-256 is available.
- A password is not required when you are attempting to restore to the computer from which the backup was performed. However, when you attempt to restore it to a different computer, a password is required which is set in the policy and not the password set in the data store.
- Note: After the data store is created, you cannot enable or disable deduplication, compression, or encryption.
- The Arcserve Cyber Resilient data store is added successfully.