No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Command Reference for Block

OceanStor Dorado V3 Series V300R002

This document is applicable to OceanStor Dorado3000 V3, Dorado5000 V3, Dorado6000 V3 and Dorado18000 V3. Based on the CLI provided by the DeviceManager, this document describes how to use various commands classified by functions and how to set the CLI and manage the storage system through these commands.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
create snapshot_schedule general

create snapshot_schedule general

Function

The create snapshot_schedule general command is used to create a LUN's timing snapshot schedule.

Format

create snapshot_schedule general name=? period=? day_of_week=? week_start_time=? week_reserved_num=? frequency_time_unit=? frequency_time=? frequency_reserved_num=? [ schedule_id_list=? ] [ description=? ]

Parameters

Parameter

Description

Value

name

Timing snapshot schedule name.

  • The value contains 1 to 31 ASCII characters, including letters, digits, periods (.), underscores (_), and hyphens (-).
  • When creating SNAPSHOT_SCHEDULEs in a batch by assigning the schedule_id_list=? parameter, the created SNAPSHOT_SCHEDULEs will be auto-named by appending four digits starting from 0000 to each name. For example, if you specify the SNAPSHOT_SCHEDULE name as auto, the created SNAPSHOT_SCHEDULEs will be auto-named auto0000, auto0001, and so on.
NOTE:

When creating SNAPSHOT_SCHEDULEs in a batch, the length of name=? cannot exceed 27 characters.

period

Policy type of a timing snapshot schedule.

The value is "weekly" or "frequency", where:

  • "weekly": creates timing snapshots weekly.
  • "frequency": creates timing snapshots at fixed intervals.

You can specify multiple types of policies separated by commas (,), such as: period=frequency,weekly.

day_of_week

Day in a week when timing snapshots are created.

  • The value can be "mon", "tue", "wed", "thu", "fri", "sat", or "sun". For example, day_of_week=mon.
  • You can specify multiple days separated by commas (,), such as: day_of_week=mon,tue.

week_start_time

Time in a week when timing snapshots are created.

The value is in the format of "HH:MM". It is a point in time between "00:00-23:59".

week_reserved_num

Reserved number of timing snapshots created weekly.

The value is an integer from 1 to 256.

frequency_time_unit

Unit of the fixed interval.

The value can be:

  • "hour": indicates hour.
  • "minute": indicates minutes.
  • "second": indicates seconds.

frequency_time

Fixed interval.

  • If the value of "frequency_time_unit" is set to "hour", "frequency_time" ranges from 1 to 24.
  • If the value of "frequency_time_unit" is set to "minute", "frequency_time" ranges from 1 to 1440.
  • If the value of "frequency_time_unit" is set to "second", "frequency_time" is 30.

frequency_reserved_num

Reserved number of timing snapshots created at fixed intervals.

The value is an integer from 1 to 256.

schedule_id_list

ID list of timing snapshot schedules.

  • The value is an integer from 1 to 512.
  • You can create multiple schedule IDs separated by commas (,) or an ID range using hyphens (-), such as: 1,5-8.

description

Description.

-

Level

Administrator

Usage Guidelines

  • Before performing this operation, confirm that the ID of the schedule to be set is correct.
  • Before performing this operation, confirm that the ID of the schedule to be set exists.
  • Before performing this operation, confirm that the name of the schedule to be set exists.
  • When period=weekly is set, parameters day_of_week and week_start_time are mandatory.
  • When period=frequency is set, parameter frequency_time is mandatory.

Example

  • Create timing snapshot schedule "1".
    admin:/>create snapshot_schedule general name=auto period=weekly,frequency day_of_week=sun week_start_time=00:00 week_reserved_num=10 frequency_time_unit=second frequency_time=30 frequency_reserved_num=10 schedule_id_list=1 
    Create snapshot schedule auto0000 successfully.
  • Create timing snapshot schedules "1" and "2".
    admin:/>create snapshot_schedule general name=auto period=weekly,frequency day_of_week=sun week_start_time=00:00 week_reserved_num=10 frequency_time_unit=second frequency_time=30 frequency_reserved_num=10 schedule_id_list=1-2 
    Create snapshot schedule auto0000 successfully. 
    Create snapshot schedule auto0001 successfully.

System Response

None

Translation
Download
Updated: 2019-07-16

Document ID: EDOC1100049140

Views: 115026

Downloads: 134

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next