이 콘텐츠는 선택한 언어로 제공되지 않습니다.

9.3. Scheduling Snapshots


When a snapshot is scheduled, an icon is displayed in the info column of the volumes main tab which shows that snapshot scheduling is done. Once the scheule expires, the icon will be removed from the info column. You can schedule the snapshot creation for the selected volume using (recurrence type) option. By default, the recurrence type value is set to None.

Note

You can delete existing Snapshot schedule by changing the recurrence type to None.

Procedure 9.3. Scheduling Snapshots

  1. Click the Volumes tab. The list of all volumes in the system is displayed.
  2. Select the volume of which you want to schedule Snapshot.
  3. Click Snapshot and click New to open Create/Schedule Snapshot page.
  4. In General tab, enter Snapshot Name Prefix and Description.
  5. Click Schedule tab.

    Figure 9.2. Scheduling Snapshots

  6. Select the recurrence schedule for the Snapshot. You can schedule the snapshot to recur at intervals of a specified number of minutes, hours, days, weeks, or months; either perpetually, or between specified dates.

    Figure 9.3. Recurrence Schedule

    Set Recurrence to the unit of time that you want to use as an interval between snapshots. If you do not want to set up recurring snapshots, leave this field set to None.
    Minutes
    Takes a snapshot every N minutes, where N is the value of the Interval field, with the first snapshot being taken at the time specified in the Start Schedule by field.
    Hours
    Takes a snapshot every N hours, where N is the value of the Interval field, with the first snapshot being taken after the time specified in the Start Schedule by field. Subsequent snapshots will be taken at the start of the hour. For example, if snapshots are to recur every 2 hours, and the first snapshot occurs at 2.20 PM, the next snapshot will occur at 4.00 PM.
    Days
    Takes a snapshot at the time specified in the Execute At field every N days, where N is the value of the Interval field, with the first snapshot being taken after the time specified in the Start Schedule by field.
    Weeks
    Takes a snapshot at the time specified in the Execute At field every N weeks, where N is the value of the Interval field, with the first snapshot being taken after the time specified in the Start Schedule by field.
    Months
    Takes a snapshot at the time specified in the Execute At field every N months, where N is the value of the Interval field, with the first snapshot being taken at the time specified in the Start Schedule by field.
    The End by option determines whether snapshots will stop after a certain date. To set an end date, set End by to Date, and use the fields beside End Schedule By to enter a date and time at which snapshots should stop. To take snapshots continuously with no end date, set End by to No End Date.
  7. Click OK to set the snapshot recurrence schedules.
If a soft limit or a hard limit for the number of shapshots of a volume reaches a limit, an alert is generated.

Note

Syncing of shapshots takes 5 minutes from the CLI.

Important

Scheduling of snapshots cannot be done from CLI once it is scheduled from Red Hat Gluster Storage Console. In the case of Red Hat Gluster Storage Nodes are no longer managed by Red Hat Gluster Storage Console, snapshot scheduling could be done using gluster CLI as well by running the command echo "none" > /var/run/gluster/shared_storage/snaps/current_scheduler.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat