Replicating File Storage for Classic Shares

Determining the remote data center for the replicated storage volume in the console

IBM Cloud data centers are paired into primary and remote combinations in every region worldwide. When you replicate data, consider the local data residency laws because moving data across borders can have legal implications. Replication across regions is not permitted.

The following table shows the data center codes within each region.

Determining the remote data center for the replicated storage volume from the CLI

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.

IBM Cloud data centers are paired into primary and remote combinations in every region worldwide. When you replicate data, consider the local data residency laws because moving data across borders can have legal implications. Replication across regions is not permitted.

$ ibmcloud sl file replica-locations 560156918
ID        Short Name   Long Name
449494    dal09        Dallas 9
957095    wdc04        Washington 4
1004995   sjc03        San Jose 3
1441195   dal10        Dallas 10
1854795   dal12        Dallas 12
2017603   wdc07        Washington 7
2017695   wdc06        Washington 6
2178495   sjc04        San Jose 4

 # slcli file replica-locations --help
 Usage: slcli file replica-locations [OPTIONS] VOLUME_ID

 Options:
 --sortby TEXT   Column to sort by
 --columns TEXT  Columns to display. Options: ID, Long Name, Short Name
 -h, --help      Show this message and exit.

Creating the initial replica in the console

Replications work based on a snapshot schedule. You must first have snapshot space and a snapshot schedule for the source volume before you can replicate. The Order Replica option appears when Snapshot space and Snapshot schedule are available for the source volume. Replication is managed under Storage > File Storage for Classic in the IBM Cloud® console.

1. Click the name of your storage volume to display its details.

2. Click Actions and click Order Replica.

3. Select the existing snapshot schedule that you want your replication to follow. The list contains all of your active snapshot schedules.

   You can select only one schedule even if you have a mix of hourly, daily, and weekly. All the snapshots, which were captured since the previous replication, are replicated regardless of the schedule that originated them. For more information, see Working with Snapshots. Replication starts 5 minutes after the snapshot is taken to ensure that the most up-to-date data is copied to the replica volume.

4. Select a Location for the replica volume.

5. Click Continue.

6. Enter in a Promo Code if you have one, and click Recalculate. The other fields in the window are completed by default.

   Discounts are applied when the order is processed.

7. Review your order, and read the service agreement. If you agree with the terms, check the box.

8. Click Place Order.

Creating the initial replica from the CLI

Replications work based on a snapshot schedule. You must first have snapshot space and a snapshot schedule for the source volume before you can replicate.

$ ibmcloud sl file replica-order 560156918  -s DAILY -d dal09 --tier 4
This action will incur charges on your account. Continue?> y
OK
Order 110551616 was placed.
 > Storage as a Service
 > File Storage
 > 500 GBs
 > 4 IOPS per GB
 > 500 GB (Snapshot Space)
 > Replication for tier-based performance. Replicant of: SL02SEV1414935_268

$ slcli file replica-order --help
Usage: slcli file replica-order [OPTIONS] VOLUME_ID

Options:
-s, --snapshot-schedule [INTERVAL|HOURLY|DAILY|WEEKLY]
                                Snapshot schedule to use for replication,
                                (INTERVAL | HOURLY | DAILY | WEEKLY)
                                [required]
-l, --location TEXT             Short name of the data center for the
                                replicant (e.g.: dal09)  [required]
--tier [0.25|2|4|10]            Endurance Storage Tier (IOPS per GB) of the
                                primary volume for which a replicant is
                                ordered [optional]
-h, --help                      Show this message and exit.

Viewing the replica volumes in the Volume List in the console

You can view your replication volumes on the File Storage for Classic page under Storage > File Storage for Classic. The volume name shows the primary volume's name followed by REP. The Type is Endurance or Performance – Replica.

Viewing the replica volumes from the CLI

$ ibmcloud sl file replica-partners 560156918
ID          User name                  Account ID   Capacity (GB)   Hardware ID   Guest ID   Host ID
560382016   SL02SEV1414935_268_REP_1   1234567      500             -             -          -

  # slcli file replica-partners --help
  Usage: slcli file replica-partners [OPTIONS] VOLUME_ID

  Options:
  --sortby TEXT   Column to sort by
  --columns TEXT  Columns to display. Options: ID, Username, Account ID,
                  Capacity (GB), Hardware ID, Guest ID, Host ID
  -h, --help      Show this message and exit.

Viewing the replication history in the console

To view the Replication history, click Manage on the main menu bar. Select Account, and scroll to the Audit Log. The Storage Replication Events list contains the names of the volume, a description of the replication event and the timestamp of the event.

Editing the Replication Schedule in the console

The replication schedule is based on an existing snapshot schedule. To change the replica schedule from Hourly to Daily or Weekly or vice versa, you must cancel the replica volume and set up a new one.

However, if you want to change the time of day when your Daily replication occurs, you can adjust the existing schedule on the active volume.

1. On the active volume details page, click Actions .
2. Select Edit Snapshot Schedule.
3. Look in the Snapshot frame under Schedule to determine which Daily schedule you're using for replication. Change the schedule that you want.
4. Click Save.

Deleting an existing replica file share in the console

You can cancel replication either immediately or on the anniversary date, which causes billing to end.

1. Click the volume from the File Storage for Classic page.
2. Click Actions .
3. Select Delete Replica.
4. Select when to cancel. Choose Immediately or Anniversary Date, and click Continue.
5. This operation deletes the replica volume with all its data. Click the checkbox to acknowledge the information, and click Delete.

Canceling replication when the primary volume is deleted in the console

When a primary volume is deleted, the replication schedule and the volume in the replica data center are deleted, too.

You can expect the volume to remain visible in your Storage list for at least 24 hours (immediate cancellation) or until the anniversary date. Certain features aren't going to be available any longer, but the volume remains visible until it is reclaimed. However, billing is stopped immediately after you click Delete Replica.

Active replicas can block reclamation of the Storage volume. Make sure that the volume is no longer mounted, host authorizations are revoked, and replication is canceled before you attempt to cancel the original volume.