schedule --add --day <day of the week> [--cleaner] [--replication] [--start_time <hh:mm>] [-- stop_time <hh:mm>] [--name <name>]

Description

Creates a new Cleaner or Replication schedule for a DR Series system (on a source DR). For a specific container, you would use the --name <name> command option with the start time and stop time set points.

NOTE: Without any Cleaner schedule set, the DR Series system Cleaner process automatically starts within two minutes after it detects that no data ingest operation or other system operation activity is present. So, if your DR Series system runs intermittent or inconsistent ingest, readback, or replication operations, there is no need to set a Cleaner schedule (it will automatically run during periods of low or non-activity). However, if your system runs regular and consistent ingest, readback, or replication operations, you should create a Cleaner schedule that runs only during a known period of low or non-activity (for example, on a day or time period sufficient to complete this process). If your system does not meet either of these cases, you can still manually run the Cleaner. For more information, see maintenance --filesystem [--reclaim_space].

Syntax

NOTE: Set a corresponding stop time for every start time in each Cleaner (or Replication) schedule you create. The following example shows setting up a Cleaner schedule for the remainder of the week (Monday through Saturday).

NOTE: Do not select 00:00 for a start time or stop time endpoint for midnight when setting Cleaner or Replication schedules (instead, use either the 23:55 or 00:05 value).

NOTE: To create a Replication schedule (use the DR Series system CLI --replication command), and the same process shown here to schedule the start and stop times for a Replication schedule. This lets you schedule start and stop times for each day in the week in which you want the Replication process to run.

schedule --delete --day <day of the week> [--cleaner] [--name <name>] [--replication]

Description

Deletes a day in an existing Cleaner or Replication schedule for a DR Series system (on a source DR). The --name option is only applicable for replication and not for the cleaner. You can use it to specify a container.

NOTE: To delete days from either an existing Cleaner or Replication schedule, specify the day in the week and the schedule type.

Syntax

Result

schedule --help

Description

Displays the list of schedule-related options that can be used as a reference when using the DR Series system CLI.

Syntax

Result

Data Integrity Checking

Data Integrity Checking

The DR Series system design includes an online data integrity verification feature known as Data Check, which checks for potential or unexpected data inconsistencies in the data store associated with the internal system deduplication engine. Data Check performs a series of checks for unexpected data inconsistencies as early as possible in the data ingest and backup process.

Data Check checks and verifies data both during the write process and also the data already stored on the system disks. The design purpose is to detect potential issues early enough in the data management process so that original data can be used to backup and correct any potential data inconsistencies. Data Check reports data verification issues, but it is not intended nor designed to repair these issues itself.

Any data inconsistencies that are encountered are reported as DR Series system alerts, and these filesystem errors can be repaired using the Maintenance mode (for more information, see Maintenance.

The Data Check feature runs continuously except for when the DR Series system enters its Maintenance mode (it does not run while the system is in this mode). Data Check leaves the system in an Operational mode when it detects an error, at which point, it sends an alert and an event.

If an alert has already been sent, but has not been cleared (for example, when repairs occur during the Maintenance mode), no new event is sent. Similarly, for events, one is sent for the first detected data inconsistency, and then the total number of issues detected during the scan are listed in a new event.

If Data Check is enabled, it runs in the background as a low-priority process, and changes to an idle state when the other major DR Series system operations (data ingest, replication, and cleaner) are active.

NOTE: Unless otherwise noted, all later references to datacheck or Data Check in this guide are used interchangeably to represent the Data Check feature in the DR Series system.