(Optional; used with the analyze action) The type of data to be analyzed
--days-d<number of days>
(Required) Interval of schedule runs in days
NOTE:Not required if
--days is set. If the interval exceeds 24 hours, a combination of days and hours is required.
--excludefilepath,
-p<"file path">
(Optional; used with the analyze action) File path to exclude from an analyze operation
--excludefiles,
-e<"filename">
(Optional; used with the analyze action) Files to exclude from an analyze action
--hours,
-h<number of hours>
(Required) Interval of schedule runs in hours
NOTE:Not required if
--days is set. If the interval exceeds 24 hours, a combination of days and hours is required.
--includefilepath,
-f<"file path">
(Optional; used with the analyze action) File path to include in an analyze operation
--includefiles,
-i<"filename">
(Optional; used with the analyze action) Files to include in an analyze action
--policyname,
-p<policy name>
(Required) The name of the policy
--retlockduration,
-r<length of time>
(Optional) Overrides the retention lock duration that is configured for the policy
--schedulename,
-n<schedule name>
(Required) The name of the schedule
--startdate,
-s<"date and time">
(Required) The date and time for the schedule to run. Follow the format of this example: "07/10/21 3:00PM EDT".
--storagedatainterface,
-g<interface name>
(Optional; used with the analyze action with CyberSense version 8.2 and earlier) The network storage interface through which CyberSense connects to storage.
Example
[root@cr-system]# crcli schedules add --schedulename schedule01 --policyname phm-policy --action securecopy --startdate "07/10/21 3:00PM EDT" --hours 1
Schedule: schedule01 added to the system successfully.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\