Modify Arcserve Cloud Cyber Resilient Data Store

This section provides information about how to modify Arcserve Cloud Cyber Resilient Data Store.

You can modify an already existing cloud cyber resilient data store. However, due to some restrictions, you cannot modify the following details of a data store:

• Data Store Folder
• Cloud Account
• Region
• Bucket Name
• Endpoint
• Retention Policy
• Enable Deduplication
• Index Destination
• Hash Destination
• Enable Compression

Follow these steps:

1. Log into Arcserve UDP, and click the resources tab.
2. From the left pane, navigate to Destinations, and click Recovery Point Servers.
3. The Destinations: Recovery Point Servers page displays in the center pane.
3. Right-click the required Arcserve Cloud Cyber Resilient data store and select Modify Arcserve Cloud Cyber Resilient Data Store.
4. The Modify Arcserve Cloud Cyber Resilient Data Store dialog opens.
4. Update the following details as needed, and then click Save.
• Data Store Name: Specifies the name of the data store.
• Concurrent Active Jobs: Limits the maximum number of concurrent active 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.
• Note: Limit to number only impacts the replication outbound job, not the replication inbound job. Limit to number does not impact the Restore or BMR jobs. Such jobs are not placed in a queue.
• 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 snapshot can be retained before they are automatically deleted.
• Note: To optimize cloud 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 snapshot must be retained before they are automatically deleted.
• Note: To optimize cloud 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 snapshot must be retained before they are automatically deleted.
• Note: To optimize cloud 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).
• By default, the cleanup job for expired objects runs daily at 3:00 AM. To change this schedule, modify the following registry values:
• Registry Path
• Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Arcserve\Unified Data Protection\Engine\DataStore\<datastorename>\GDD
• Registry Values
• CIDSCleanupScheduleHour (DWORD) - Specifies the hour
• CIDSCleanupScheduleMin (DWORD) - Specifies the minutes
• Example
• To set the cleanup time to 9:30 PM, configure the values as follows:
• CIDSCleanupScheduleHour = 21
• CIDSCleanupScheduleMin = 30
• Allow at least a 1 hour window for the cleanup job to complete, and schedule snapshots outside this window to avoid overlap.
• Hash Memory Allocation:
• Specifies the amount of physical memory that you allocate to keep 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 smaller than 4 GB (or is identical to 4 GB), the default value of Hash Memory Allocation is identical to 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 at this time. 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 the RPS has 32 GB of physical memory. Assume that 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. Then, the default value of Hash Memory Allocation is 22.4 GB (22.4 GB = 28 GB * 80%).
• Enable Encryption: Specifies that encryption settings are enabled.
• Note: You cannot enable or disable encryption after the Arcserve Cyber Resilient data store is created. If you have enabled encryption while adding the data store, you can change the encryption password. To change, specify and confirm the encryption password.
5. 

The Arcserve Cloud Cyber Resilient Data Store is modified successfully.