volume reallocation schedule
Modify schedule of reallocate job
Availability: This command is available to cluster administrators at the admin privilege level.
Description
Schedules a reallocation scan for an existing reallocation job. If the reallocation job does not exist, use the volume reallocation start command to define a reallocation job.
You can delete an existing reallocation scan schedule. However, if you do this, the job's scan interval reverts to the schedule that was defined for it when the job was created with the volume reallocation start command.
This command is not supported for FlexGroups or FlexGroup constituents. |
Parameters
-vserver <vserver name>
- Vserver-
Specifies the Vserver.
-path <text>
- Path-
Specifies the path of the reallocation for a LUN, NVMe namespace, file, or volume.
[-d, -del <true>]
- Delete-
Deletes an existing reallocation schedule when set to true. If you use this command without specifying this parameter, its effective value is false and the reallocation schedule is not deleted. If you specify this parameter without a value, it is set to true and the reallocation schedule is deleted.
[-s, -cron <text>]
- Cron Schedule-
Specifies the schedule with the following four fields in sequence. Use a space between field values. Enclose the values in double quotes.
-
minute is a value from 0 to 59.
-
hour is a value from 0 (midnight) to 23 (11:00 p.m.).
-
day of week is a value from 0 (Sunday) to 6 (Saturday).
-
day of month is a value from 1 to 31.
If you specify 31 as the value for the day of month, reallocation scans will not run in any months with fewer than 31 days.
Use an asterisk "*" as a wildcard to indicate every value for that field. For example, an * in the day of month field means every day of the month. You cannot use the wildcard in the minute field.
You can enter a number, a range, or a comma-separated list of values for a field.
-
Examples
cluster1::> volume reallocation schedule -s "0 23 6 *" /vol/db/lun1
Schedules a reallocation job to run at 11 pm every Saturday on lun1.