Managing Snapshots

Adding a Snapshot schedule in the console

You can decide how often and when you want to create a point in time reference of your storage volume with Snapshot schedules. You can have a maximum of 50 snapshots per storage volume. Schedules are managed through the Storage > Block Storage for Classic tab of the IBM Cloud® console.

Before you can set up your initial schedule, you must first purchase snapshot space if you didn't purchase it during the initial provisioning of the storage volume. For more information, see Ordering Snapshots.

Snapshots schedules can be set up for hourly, daily, and weekly intervals, each with a distinct retention cycle. The maximum limit of snapshots is 50 per storage volume, which can be a mix of hourly, daily, and weekly schedules, and manual snapshots.

1. Click your storage volume, click Actions, and click Edit Snapshot Schedule.
2. In the Snapshot Schedule window, you can select from three different snapshot frequencies. Use any combination of the three to create a comprehensive snapshot schedule.
   • Hourly
     • Specify the minute each hour that a snapshot is to be taken. The default is the current minute.
     • Specify the number of hourly snapshots to be retained before the oldest is discarded.
   • Daily
     • Specify the hour and minute that a snapshot is to be taken. The default is the current hour and minute.
     • Select the number of hourly snapshots to be retained before the oldest is discarded.
   • Weekly
     • Specify the day of the week, hour, and minute that a snapshot is to be taken. The default is the current day, hour, and minute.
     • Select the number of weekly snapshots to be retained before the oldest is discarded.
3. Click Save. Then, you can create another schedule with a different frequency. If the total number of scheduled snapshots is over 50, you receive a warning message and you are not going to be able to save another snapshot.

The list of the snapshots is displayed as they're taken in the Snapshots section of the Block Storage for Classic Detail page.

Adding a Snapshot schedule from the CLI

You can decide how often and when you want to create a point in time reference of your storage volume with Snapshot schedules. You can have a maximum of 50 snapshots per storage volume.

Before you can set up your initial schedule, you must first purchase snapshot space if you didn't purchase it during the initial provisioning of the storage volume. For more information, see Ordering Snapshots.

Before you begin, decide on the CLI client that you want to use.

• You can either install the IBM Cloud CLI and install the SL plug-in with ibmcloud plugin install sl. For more information, see Extending IBM Cloud CLI with plug-ins.
• Or, you can install the SLCLI.

$ ibmcloud sl block snapshot-enable 560156918 -s WEEKLY -c 5 -m 0 --hour 2 -d 0
OK
WEEKLY snapshots have been enabled for volume 560156918.

$ slcli block snapshot-enable --help
Usage: slcli block snapshot-enable [OPTIONS] VOLUME_ID

  Enables snapshots for a given volume on the specified schedule

Options:
  --schedule-type TEXT    Snapshot schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
                          [required]
  --retention-count TEXT  Number of snapshots to retain  [required]
  --minute INTEGER        Minute of the day when snapshots should be taken
  --hour INTEGER          Hour of the day when snapshots should be taken
  --day-of-week TEXT      Day of the week when snapshots should be taken
  -h, --help              Show this message and exit.

$ slcli block snapshot-schedule-list --help
Usage: slcli block snapshot-schedule-list [OPTIONS] VOLUME_ID

Options:
  -h, --help  Show this message and exit.

Managing a Snapshot schedule with Terraform

To create a snapshot schedule, use the ibm_storage_block resource and specify information in the snapshot_schedule argument. The following example defines two different schedules. One schedule is for weekly snapshots that are taken on Sundays at 1:20 PM. Twenty snapshots are kept before the oldest one is deleted to make space for a new one. The second schedule is for hourly snapshots.

resource "ibm_storage_block" "test1" {
        type = "Endurance"
        datacenter = "dal13"
        capacity = 20
        iops = 0.25
        os_format_type = "Linux"

        # Optional fields
        allowed_virtual_guest_ids = [ 27699397 ]
        allowed_ip_addresses = ["10.40.98.193", "10.40.98.200"]
        snapshot_capacity = 10
        hourly_billing = true

        # Optional fields for snapshot
        snapshot_schedule {
        schedule_type   = "WEEKLY"
        retention_count = 20
        minute          = 20
        hour            = 13
        day_of_week     = "SUNDAY"
        enable          = true
        }
        snapshot_schedule {
        schedule_type   = "HOURLY"
        retention_count = 20
        minute          = 2
        enable          = true
  }
}

If you want to update the schedule, change these values and apply them to your resources. If you want to delete the schedule, remove its details from the ibm_storage_block resource definition, and apply your changes.

Taking a manual Snapshot in the console

Manual snapshots can be taken at various points during an application upgrade or maintenance. You can also take snapshots across multiple servers that were temporarily deactivated at the application level.

The maximum limit of snapshots per storage volume is 50.

1. Click your storage volume.
2. Click Actions.
3. Click Take Manual Snapshot.

The snapshot is taken and displayed in the Snapshots section of the Block Storage for Classic Detail page. Its schedule appears Manual.

Taking a manual Snapshot from the CLI

$ ibmcloud sl block snapshot-create 562193766
OK
New snapshot 562208096 was created.

$ slcli block snapshot-create --help
Usage: slcli block snapshot-create [OPTIONS] VOLUME_ID

Options:
  -n, --notes TEXT  Notes to set on the new snapshot
  -h, --help        Show this message and exit.

Listing all Snapshots with Space Used information and Management functions in the console

A list of retained snapshots and the space that is used can be seen on the Block Storage for Classic Detail page. Management functions (editing schedules and adding more space) are conducted on the Block Storage for Classic Detail page by using the Actions menu or links in the various sections on the page. The Snapshot page displays how much capacity the volume has and how much of it is used.

You receive notifications when you reach space thresholds – 75%, 90%, and 95%.

• At 75% capacity, a warning is sent that snapshot space usage exceeded 75%. To remediate this issue, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule. If you reduce the snapshot data or increase the space, the warning system is reset, and no autodeletion occurs.
• At 90% capacity, a second warning is sent when snapshot space usage exceeded 90%. Like with reaching 75% capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
• At 95% capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95%. Snapshots continue to be deleted each time usage exceeds 95% until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.

By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time from the CLI.

If snapshot space utilization increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if utilization jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%.

Listing all Snapshots with Space Used Information from the CLI

$ ibmcloud sl block snapshot-list 562193766
id          user_name             created                     size_bytes   notes
562208096   SL02SEVC1414935_651   2023-10-25T12:09:34-05:00   24000        -

$ slcli block snapshot-list --help
Usage: slcli block snapshot-list [OPTIONS] VOLUME_ID

Options:
  --sortby TEXT   Column to sort by
  --columns TEXT  Columns to display. Options: id, name, created, size_bytes
  -h, --help      Show this message and exit.

Check and update notification status from the CLI

Notifications are sent when you reach three different space thresholds – 75%, 90%, and 95%.

• At 75% capacity, a warning is sent that snapshot space usage exceeded 75%. To remediate this issue, you can manually add space, or delete retained unnecessary snapshots. You can reduce the number of retained snapshots in the schedule. If you reduce the snapshot data or increase the space, the warning system is reset, and no autodeletion occurs.
• At 90% capacity, a second warning is sent when snapshot space usage exceeded 90%. Like with reaching 75% capacity, if you take the necessary actions to decrease the snapshot data or increase the space, the warning system is reset and no autodeletion occurs.
• At 95% capacity, a final warning is sent. If no action is taken to bring your space usage under the threshold, automatic deletion starts so that future snapshots can be created. Scheduled snapshots are deleted, starting with the oldest, until usage drops under 95%. Snapshots continue to be deleted each time usage exceeds 95% until it drops under the threshold. If the space is manually increased or snapshots are manually deleted, the warning is reset and reissued if the threshold is exceeded again. If no actions are taken, this notification is the only warning that you receive.

If snapshot space utilization increases too rapidly, then you might receive one notification before autodeletion of the oldest scheduled snapshot occurs. For example, if utilization jumps from 76% to 96% within 15 minutes, you receive one notification about exceeding 75% and one notification about exceeding 95%. The system skips the 90%-exceeded warning.

By default, snapshot warning notifications are enabled for every customer. However, you can choose to disable them. When this feature is disabled, all ticket generation and notifications are stopped. You can disable and enable notifications for the volume at any time.

$ ibmcloud sl block snapshot-get-notification-status 562193766
Enabled: Snapshots space usage threshold is enabled for volume '562193766'.

$ ibmcloud sl block snapshot-set-notification --disable  562193766
OK
Snapshots space usage threshold warning notification has been set to 'false' for volume '562193766'.

$ slcli block snapshot-get-notification-status
Usage: slcli block snapshot-get-notification-status [OPTIONS] VOLUME_ID
  Get snapshots space usage threshold warning flag setting for a given volume

Options:
  -h, --help  Show this message and exit.

$ slcli block snapshot-set-notification VOLUME_ID
Usage: slcli block snapshot-set-notification VOLUME_ID [OPTIONS]

Options:
 --disable  Disable snapshot threshold warning notification for the storage volume
 --enable   Enable snapshot threshold warning notification for the storage volume
 -h, --help  Show this message and exit.

Increasing the amount of Snapshot space for a volume in the console

You might need to add snapshot space to a volume that didn't previously have any or might require extra snapshot space.

Snapshot space can be increased. It can't be reduced. You can select a smaller amount of space until you determine how much space you need. Remember, automated and manual snapshots share the space.

Snapshot space is changed through Storage > Block Storage for Classic.

1. Click your storage volume, click Actions, and click Change Snapshot Space.
2. Select from a range of sizes from the prompt. For more information about available snapshot capacity allotments, see Ordering snapshots.
3. Click Continue.
4. Enter any Promo Code that you have, and click Recalculate. The Charges for this order and Order Review fields are completed by default.
5. Read the service agreement, and if you agree with the terms click checkbox, and click Place Order. Your additional snapshot space is provisioned in a few minutes.

Deleting a snapshot schedule in the console

Snapshot schedules can be canceled through Storage > Block Storage for Classic.

1. Click the volume ID to display its related information.
2. Click Snapshots.
3. Click the schedule to be deleted in the Snapshot Schedules frame.
4. Click the checkbox next to the schedule to be deleted and click Save.

If you're using the replication feature, be sure that the schedule you're deleting isn't the schedule that is used by replication. For more information about deleting a replication schedule, see Replicating Data.

Deleting a snapshot schedule from the CLI

$ ibmcloud sl block snapshot-disable 562193766 -s DAILY
OK
DAILY snapshots have been disabled for volume 562193766.

$ slcli block snapshot-disable --help
Usage: slcli block snapshot-disable [OPTIONS] VOLUME_ID

  Disables snapshots on the specified schedule for a given volume

Options:
  --schedule-type TEXT  Snapshot schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
                        [required]
  -h, --help            Show this message and exit.

Deleting a snapshot in the console

Snapshots that are no longer needed can be manually removed to free up space for future snapshots. Deletion is done through Storage > Block Storage for Classic.

1. Click your storage volume and click Snapshot to see the list of existing snapshots.
2. Click Actions next to a particular snapshot and click Delete. Click the confirmation box that warns about possible data loss, then click Delete. This deletion doesn't affect any future or past snapshots on the same schedule as snapshots don't depend on each other.

Manual snapshots that aren't deleted in the portal manually are automatically deleted when you take another snapshot if you have reached space limitations. The oldest snapshot is deleted first.

Deleting a snapshot from the CLI

Snapshots that are no longer needed can be manually removed to free up space for future snapshots.

Manual snapshots that aren't deleted in the portal manually, are automatically deleted when you reach space limitations (oldest first).

$ ibmcloud sl block snapshot-delete 562208096
OK
Snapshot 562208096 was deleted.

$ slcli block snapshot-delete
Usage: slcli block snapshot-delete [OPTIONS] SNAPSHOT_ID

Options:
  -h, --help  Show this message and exit.

Restoring storage volume to a specific point in time by using a snapshot in the console

You might need to take your storage volume back to a specific point in time because of user-error or data corruption.

1. Unmount and detach your storage volume from the host to ensure that the host is not connected to the volume during the restore.

   • Unmounting Block Storage for Classic volumes on a Linux® server
   • Unmounting Block Storage for Classic volumes on a Microsoft server

2. Go to the IBM Cloud® console. From the menu, select Classic Infrastructure .

3. Click Storage, Block Storage for Classic.

4. Scroll on the list, and click your volume to be restored. The Snapshots page displays the list of all saved snapshots along with their size and creation date.

5. Click Actions next to the snapshot to be used and click Restore.

   Completing the restore results in the loss of the data that was created or modified after the snapshot was taken. This data loss occurs because your storage volume returns to the same state that it was in of the time of the snapshot.

6. Click Yes to start the restore. The restoration is going to take a while, and your storage volume is locked during the restoration.

   When you return to the volume list, a clock icon appears next to your volume that indicates that an active transaction is in progress. Hovering over the icon produces a window that shows the transaction. The icon disappears when the transaction is complete.

7. Mount and reattach your storage volume to the host.

   • Mount iSCSI LUN on Red Hat Enterprise Linux® 8.
   • Mount iSCSI LUN on CloudLinux 8.
   • Mount iSCSI LUN on Ubuntu 20.
   • Mapping LUNS on Microsoft Windows.

Restoring a volume results in deleting all snapshots that were taken after the snapshot that was used for the restore.

Restoring storage volume to a specific point in time by using a snapshot from the CLI

You might need to take your storage volume back to a specific point in time because of user-error or data corruption.

1. Unmount your volume. You must ensure that the host is not trying to connect to the volume during the restore.

   • Unmounting Block Storage for Classic volumes on a Linux® server
   • Unmounting Block Storage for Classic volumes on Microsoft

2. Then, you can restore the volume with a snapshot by using one of the following commands.

   • From the IBMCLOUD CLI, you can use the ibmcloud sl block snapshot-restore command.

     $ ibmcloud sl block snapshot-restore 562193766 562211890
     OK
     Block volume 562193766 is being restored using snapshot 562211890.
     

     For more information about all of the parameters that are available for this command, see ibmcloud sl block snapshot-restore.

   • From the SLCLI, you can use the slcli block snapshot-restore command.

     $ slcli block snapshot-restore --help
     Usage: slcli block snapshot-restore [OPTIONS] VOLUME_ID
     
     Options:
      -s, --snapshot-id TEXT  The id of the snapshot which is to be used to restore
                              the block volume
      -h, --help              Show this message and exit.
     

3. Lastly, mount and reattach your storage volume to the host.

   • Mount iSCSI LUN on Red Hat Enterprise Linux® 8.
   • Mount iSCSI LUN on CloudLinux 8.
   • Mount iSCSI LUN on Ubuntu 20.
   • Mapping LUNS on Microsoft Windows.

Restoring a volume results in deleting all snapshots that were taken after the snapshot that was used for the restore.