schedules modify
Use the
schedules modify command to modify a schedule.
Syntax
crcli schedules modify --schedulename <schedule name> --action {securecopy | securecopyanalyze |sync-copy | copy-lock | sync | copy | analyze | recoverycheck }[--appnickname <nickname> ][--contentFormat {filesystem | databases | backups} ]--days <number of days> [--disable ][--enable ][--excludefilepath file path ][--excludefiles <"filename"> ]--hours <number of hours> [--includefilepath file path ][--includefiles <"filename"> ][--contentFormat {filesystem | databases | backups} ][--newschedulename <name> ]--nextrun <"date and time"> [--retlockduration <length of time> ][--storagedatainterface <interface name> ]
Parameters
--action ,
-a
{securecopy | securecopyanalyze | sync-copy | copy-lock | sync | copy | analyze | recoverycheck }
(Required) The action that you want the policy to run. The
shelteredharbor option is available only if the Sheltered Harbor feature is enabled and is run on a Sheltered Harbor policy.
--appnickname ,
-i
<nickname>
(Required for an analyze action) A meaningful name for the application
--contentFormat ,
-t
{filesystem | databases | backups}
(Optional; used with the analyze action) The type of data to be analyzed
--days ,
-d
<number of days>
(Optional) Interval of schedule runs in days
NOTE If the interval exceeds 24 hours, a combination of days and hours is required
--disable ,
-x
(Optional) Disables a schedule
--enable ,
-e
(Optional) Enables a schedule
--excludefilepath ,
-p
<"file path">
(Optional for the analyze action) File path to exclude from an analyze operation
--excludefiles ,
-l
<"filename">
(Optional; used with the analyze action) Files to exclude from an analyze operation
--hours ,
-h
<number of hours>
(Optional) Interval of schedule runs in hours
NOTE If the interval exceeds 24 hours, a combination of days and hours is required
--includefilepath ,
-f
<"file path">
(Optional for the analyze action) File path to include in an analyze operation
--includefiles ,
-c
<"filename">
(Optional; used with the analyze action) Files to include in an analyze operation
--newschedulename ,
-s
<schedule name>
(Optional) New name for the schedule
--nextrun ,
-t
<"date and time">
(Optional) The date and time for the schedule to run. Follow the format of this example: "07/10/21 3:00PM EDT".
--retlockduration ,
-r
<length of time>
(Optional) Overrides the retention lock duration of the policy
--schedulename ,
-n
<schedule name>
(Required) The name of the schedule to modify
--storagedatainterface ,
-g
<interface name>
(Optional; used with the analyze action) The network storage interface through which the CyberSense application connects to storage.
Example
[root@cr-system]# crccli schedules show -n Schedule1
bash: crccli: command not found...
[root@ldpda108 staging]# crcli schedules show -n Schedule1
Schedule Details:
-----------------
id: 606df03270ec150001ba3d2f
schedulename: Schedule1
policy: phm-policy
enabled: true
actions: copy-lock
retlockduration: 12h
createdby: crso
createdbyrole: security-officer
creationdate: 2021.04.07 13:47:30
modifieddate: 2021.04.07 13:47:30
Frequency Details:
------------------
days: 0
hours: 12
[root@cr-system]# crcli schedules modify --schedulename Schedule1 --newschedulename CR-Schedule --days 1 --hours 12
Schedule: Schedule1 modified successfully.
[root@cr-system]# crcli schedules show --schedulename CR-Schedule
Schedule Details:
-----------------
id: 606df03270ec150001ba3d2f
schedulename: CR-Schedule
policy: phm-policy
enabled: true
actions: copy-lock
retlockduration: 12h
createdby: crso
createdbyrole: security-officer
creationdate: 2021.04.07 13:47:30
modifieddate: 2021.04.07 15:10:12
Frequency Details:
------------------
days: 1
hours: 12