How-to Guides
Users can create the service by entering the required information for Block Storage (BM) and selecting detailed options through the Samsung Cloud Platform Console.
Block Storage(BM) Create
You can create and use the Block Storage (BM) service in the Samsung Cloud Platform Console.
To create Block Storage (BM), follow the steps below.
Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
Click the Block Storage(BM) Create button on the Service Home page. You will be taken to the Block Storage(BM) Create page.
Block Storage(BM) Creation page, input the information needed to create the service, and choose detailed options.
| Category | Required status | Detailed description |
|---|
| Volume name | Required | Volume name- must start with an English letter and be 3~28 characters using English letters, numbers, and special characters (
-)
- cannot be modified after service creation
|
| Disk type | Required | Select Disk Type- SSD: High-performance general volume
- Cannot be modified after service creation
|
| capacity | Required | Capacity setting- Enter a number between 1~16,384 GB
- Cannot be modified after service creation
|
| Max IOPS | Required | Enter IOPS value- Enter a number between 5,000~20,000
- HDD type does not provide performance metric setting function
|
| Max Throughput | Required | Enter the throughput speed (MB/s)- Enter a number between 250~1,000
- HDD type does not provide performance metric configuration functionality
|
| Connection server | Required | Connect Bare Metal Server selection- Provides up to 8 Bare Metal Server connections
- No limit on the number of volumes that can be attached to a Bare Metal Server
|
Table. Block Storage (BM) Service Information Input Items
Summary Check the detailed information and estimated billing amount generated in the panel, and click the Create button.
- Once creation is complete, check the created resources on the Block Storage(BM) List page.
Reference
- Regardless of disk type, all volumes have server-side encryption based on the AES-256 algorithm applied by default.
- The snapshot schedule can be set on the detail page.
- The performance metrics (IOPS, Throughput) of the configured storage are based on maximum values and do not guarantee consistent values.
Caution
Capacity can be expanded only for original volumes that do not use the snapshot feature. For volumes that use snapshots, add the volume to the attached server to secure additional capacity.
Volumes created by the user in addition to the OS’s default volume must be configured with iSCSI.
After checking the IP provided in the iSCSI Information on the Block Storage(BM) Details page, follow the iSCSI configuration steps for each OS.
Linux operating system
information
The iSCSI information (Storage Target IP) was written assuming 10.40.40.41, 10.40.40.42.
- Check the iSCSI information on the Block Storage (BM) detail page.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
- Connection Server item, verify the server and then connect.
- Proceed with iSCSI configuration by referring to the steps below.
- Discover the connection information for the Storage (target IP).
[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.41
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
[root@localhost ~]# iscsiadm -m discovery -t st -p 10.40.40.42
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
code block. Storage (target IP) connection information Discovery - Connect to the storage (target IP). If it is already connected, proceed to the next step.
[root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
[root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
[root@localhost ~]# iscsiadm -m node -p 10.40.40.41:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260] successful
[root@localhost ~]# iscsiadm -m node -p 10.40.40.42:3260 --login
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Logging in to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] (multiple)
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
Login to [iface: default, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260] successful.
Code block. Storage (target IP) connection - To minimize search time, delete all unused Storage (target IP).
[root@localhost ~]# iscsiadm -m node show
100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
[root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
[root@localhost ~]# iscsiadm -m node show
100.100.100.10:3260,1026 iqn.1992-08.com.netapp:sn.c9adbd09cf301d039ea2bc878:vs.3
10.40.40.41:3260,1024 iqn.2000-05.com.3pardata:20210002ac026169
10.40.40.42:3260,1025 iqn.2000-05.com.3pardata:20220002ac026169
[root@localhost ~]# iscsiadm -m node -o delete -p 100.100.100.10:3260
Code block. Delete unused Storage (target IP) - Please rescan to verify the additional disk.
[root@localhost ~]# iscsiadm -m session --rescan
Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
[root@localhost ~]# iscsiadm -m session --rescan
Rescanning session [sid: 65, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 66, target: iqn.2000-05.com.3pardata:20210002ac026169, portal: 10.40.40.41,3260]
Rescanning session [sid: 67, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
Rescanning session [sid: 68, target: iqn.2000-05.com.3pardata:20220002ac026169, portal: 10.40.40.42,3260]
code block. Rescan - Configure Auto Login to log in automatically even after a reboot.
[root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
[root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
[root@localhost ~]# iscsiadm -m node --op=update -n node.conn[0].startup -v automatic
[root@localhost ~]# iscsiadm -m node --op=update -n node.startup -v automatic
Code block. Auto Login setting - Verify the configuration using the following command.
[root@localhost ~]# lsblk
[root@localhost ~]# lsblk
Code block. Verify configuration.
Windows operating system
guide
The iSCSI information (Storage Target IP) was assumed to be 10.40.40.41, 10.40.40.42.
- Check the iSCSI information on the Block Storage (BM) detail page.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to be used on the connected server. You will be taken to the Block Storage(BM) Details page.
- After checking the server in the Connection Server item, connect.
- Proceed with iSCSI configuration by referring to the steps below.
- Open Command Prompt (Admin) and run powershell.
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\Users> cd ..
PS C:\>
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\Users> cd ..
PS C:\>
Code block. powershell execution - Start the volume service.
PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
PS C:\> Start-Service -Name MSiSCSI
PS C:\> get-service -Name MSiSCSI | select -Property Name, DisplayName, Status, StartType
Name DisplayName Status StartType
------- -------------- ------- -----------
MSiSCSI Microsoft iSCSI Initiator Service Running Automatic
PS C:\> Set-Service -Name MSiSCSI -StartupType Automatic
PS C:\> Start-Service -Name MSiSCSI
PS C:\> get-service -Name MSiSCSI | select -Property Name, DisplayName, Status, StartType
Name DisplayName Status StartType
------- -------------- ------- -----------
MSiSCSI Microsoft iSCSI Initiator Service Running Automatic
Code block. Start volume service - Install Multipath I/O. If the Restart Needed item is displayed as Yes, a restart is required.
PS C:\> Install-WindowsFeature -name Multipath-IO
Success Restart Needed Exit Code Feature Result
------- -------------- --------- -----------------
True No Success {Multipath I/O}
PS C:\> Install-WindowsFeature -name Multipath-IO
Success Restart Needed Exit Code Feature Result
------- -------------- --------- -----------------
True No Success {Multipath I/O}
code block. Multipath I/O installation - Modify the Initiator Port Address.
If you are not an Active Directory member, skip this procedure. The Initiator Port Address only needs to be modified when you are an Active Directory member.
- iqn is generated based on the hostname, but when joined to Active Directory, it is changed to DNS format.
Since it is registered in Storage based on the default hostname, for iqn.1991-05.com.microsoft:iqn01.scp.com, iqn01 is the hostname. Remove the DNS information and change it to the name registered when creating the OS in the user Console, such as iqn.1991-05.com.microsoft:iqn01.
- If you are not an AD member, no changes are required.
PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
PS C:\> echo $address
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01.scp.com
PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
PS C:\> Get-InitiatorPort | select NodeAddress
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01
PS C:\> $address = (Get-InitiatorPort | select NodeAddress)
PS C:\> echo $address
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01.scp.com
PS C:\> Set-InitiatorPort -NodeAddress $address.NodeAddress -NewNodeAddress "iqn.1991-05.com.microsoft:iqn01"
PS C:\> Get-InitiatorPort | select NodeAddress
NodeAddress
-----------
iqn.1991-05.com.microsoft:iqn01
Code block. Modify Initiator Port Address
- Set the Storage (target Portal) address as a variable.
PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
PS C:\> $TargetPortalAddresses = @("10.40.40.41", "10.40.40.42")
Code block. Set the Storage (target Portal) address as a variable. - Discover Storage (target Portal).
PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
}
InitiatorInstanceName :
InitiatorPortalAddress :
IsDataDigest : False
IsHeaderDigest : False
TargetPortalAddress : 10.40.40.41
TargetPortalPortNumber : 3260
PSComputerName :
InitiatorInstanceName :
InitiatorPortalAddress :
IsDataDigest : False
IsHeaderDigest : False
TargetPortalAddress : 10.40.40.42
TargetPortalPortNumber : 3260
PSComputerName :
PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
New-IscsiTargetPortal -TargetPortalAddress $TargetPortalAddress
}
InitiatorInstanceName :
InitiatorPortalAddress :
IsDataDigest : False
IsHeaderDigest : False
TargetPortalAddress : 10.40.40.41
TargetPortalPortNumber : 3260
PSComputerName :
InitiatorInstanceName :
InitiatorPortalAddress :
IsDataDigest : False
IsHeaderDigest : False
TargetPortalAddress : 10.40.40.42
TargetPortalPortNumber : 3260
PSComputerName :
code block. Storage (target Portal) Discovery - Connect the disk (target).
PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
}
AuthenticationType : NONE
InitiatorInstanceName : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress : 0.0.0.0
InitiatorSideIdentifier : 400001370000
IsConnected : True
IsDataDigest : False
IsDiscovered : True
IsHeaderDigest : False
IsPersistent : True
NumberOfConnections : 1
SessionIdentifier : ffffcd0b7ba58010-4000013700000006
TargetNodeAddress : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier : 1100
PSComputerName :
AuthenticationType : NONE
InitiatorInstanceName : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress : 0.0.0.0
InitiatorSideIdentifier : 400001370002
IsConnected : True
IsDataDigest : False
IsDiscovered : True
IsHeaderDigest : False
IsPersistent : True
NumberOfConnections : 1
SessionIdentifier : ffffcd0b7ba58010-4000013700000007
TargetNodeAddress : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier : 1000
PSComputerName :IsHeaderDigest : False
TargetPortalAddress : 10.40.40.42
TargetPortalPortNumber : 3260
PSComputerName :
PS C:\> Foreach ($TargetPortalAddress in $TargetPortalAddresses){
Get-IscsiTarget | Connect-IscsiTarget -IsMultipathEnabled $true -IsPersistent $true -TargetPortalAddress $TargetPortalAddress
}
AuthenticationType : NONE
InitiatorInstanceName : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress : 0.0.0.0
InitiatorSideIdentifier : 400001370000
IsConnected : True
IsDataDigest : False
IsDiscovered : True
IsHeaderDigest : False
IsPersistent : True
NumberOfConnections : 1
SessionIdentifier : ffffcd0b7ba58010-4000013700000006
TargetNodeAddress : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier : 1100
PSComputerName :
AuthenticationType : NONE
InitiatorInstanceName : ROOT\ISCSIPRT\0000_0
InitiatorNodeAddress : iqn.1991-05.com.microsoft:iqn01
InitiatorPortalAddress : 0.0.0.0
InitiatorSideIdentifier : 400001370002
IsConnected : True
IsDataDigest : False
IsDiscovered : True
IsHeaderDigest : False
IsPersistent : True
NumberOfConnections : 1
SessionIdentifier : ffffcd0b7ba58010-4000013700000007
TargetNodeAddress : iqn.1992-08.com.netapp:sn.f807925eeae311ec9270d039ea38b250:vs.3
TargetSideIdentifier : 1000
PSComputerName :IsHeaderDigest : False
TargetPortalAddress : 10.40.40.42
TargetPortalPortNumber : 3260
PSComputerName :
code block. Disk (target) connection - Refresh the storage (target) information.
PS C:\> Update-IscsiTarget
PS C:\> Update-IscsiTarget
Code block. Storage (target) information Refresh - Register the Multipath I/O DSM and create an MPIO Disk.
When creating an MPIO disk, a prompt appears if a reboot is required. Press Y or the Enter key to reboot.PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
PS C:\> Update-MPIOClaimedHW
Confirm
Are you sure you want to perform this action?
The operation may require a system restart.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
False
PS C:\> New-MSDSMSupportedHW -VendorId MSFT2005 -ProductId iSCSIBusType_0x9
PS C:\> Update-MPIOClaimedHW
Confirm
Are you sure you want to perform this action?
The operation may require a system restart.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
False
code block. Multipath I/O DSM registration, MPIO Disk creation - Check the list and path of Multipath I/O disks.
You can check MPIO disk information using the mpclaim.exe command. Enter the generated MPIO disk number to view the disk path and status.PS C:\> mpclaim.exe -s -d
For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
MPIO Disk System Disk LB Policy DSM Name
-------------------------------------------------------------------------------
MPIO Disk3 Disk 1 RR Microsoft DSM
PS C:\> mpclaim.exe -s -d 3
MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
Controlling DSM: Microsoft DSM
SN: 600A098038314853475D543544614131
Supported Load Balance Policies: FOO RR RRWS LQD WP LB
Path ID State SCSI Address Weight
---------------------------------------------------------------------------
0000000077040001 Active/Optimized 004|000|001|000 0
TPG_State : Active/Optimized , TPG_Id: 1000, : 25
0000000077040000 Active/Optimized 004|000|000|000 0
TPG_State : Active/Optimized , TPG_Id: 1001, : 26
PS C:\> mpclaim.exe -s -d
For more information about a particular disk, use 'mpclaim -s -d #' where # is the MPIO disk number.
MPIO Disk System Disk LB Policy DSM Name
-------------------------------------------------------------------------------
MPIO Disk3 Disk 1 RR Microsoft DSM
PS C:\> mpclaim.exe -s -d 3
MPIO Disk3: 02 Paths, Round Robin, Symmetric Access
Controlling DSM: Microsoft DSM
SN: 600A098038314853475D543544614131
Supported Load Balance Policies: FOO RR RRWS LQD WP LB
Path ID State SCSI Address Weight
---------------------------------------------------------------------------
0000000077040001 Active/Optimized 004|000|001|000 0
TPG_State : Active/Optimized , TPG_Id: 1000, : 25
0000000077040000 Active/Optimized 004|000|000|000 0
TPG_State : Active/Optimized , TPG_Id: 1001, : 26
Code block. Check Multipath I/O Disk list and path - Check in Disk Management.
View detailed information of Block Storage (BM)
Block Storage(BM) service allows you to view and edit the full resource list and detailed information. Block Storage(BM) Details page consists of Details, Snapshot List, Replication, Operation History tabs.
To view detailed information about the Block Storage(BM) service, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to view detailed information. You will be taken to the Block Storage(BM) Details page.
- Block Storage(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.
| Category | Detailed description |
|---|
| Volume status | Volume status- Available: Creation completed, server connection possible
- Attaching: Connecting to server
- Detaching: Disconnecting from server
- In Use: Server connection established
- Deleting: Service termination in progress
- Editing: Changing settings
- Error Deleting: Abnormal state while deleting
- Error: Abnormal state while creating
|
| Clone creation | Create a replica in a different location |
| Create snapshot | Create a snapshot at a specific point in time |
| Service termination | Cancel service button |
Table. Status information and additional features
Reference
For recovery copies, the Snapshot List and Replication tabs are not displayed.
Detailed information
Block Storage(BM) List page lets you view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|
| Service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform- In the Block Storage(BM) service, it refers to the volume SRN
|
| Resource Name | Resource name- In the Block Storage(BM) service, it refers to the volume name
|
| Resource ID | Service’s unique resource ID |
| constructor | User who created the service |
| Creation Date/Time | Service creation timestamp |
| Editor | User who modified the service |
| Modification date | Date and time the service was modified |
| Volume name | Volume Name- If you need to modify the volume name, click the Edit button
- For detailed information on modifying the volume name, refer to Modify Volume Name reference
|
| Category | Distinguish original status regarding duplication |
| Storage volume name | Volume name within the storage device- Information distinguishing the volume used for analysis when failures or issues occur
|
| capacity | Volume size- If you need to edit the volume name, click the Edit button
|
| Max IOPS | The IOPS value set when creating the service- HDD type does not provide this metric
- Click the Edit button to change the maximum IOPS value
|
| Max Throughput | Throughput speed (MB/s) set when creating the service- HDD type does not provide this metric
- Click the Edit button to change the maximum Throughput value
|
| Disk type | Disk type |
| Encryption | Encryption status- Encryption is provided by default regardless of disk type
|
| Volume Group | Name of the Volume Group the volume belongs to |
| iSCSI information | Storage Target IP information for server connection |
| Snapshot capacity | Snapshot storage capacity- Charges are incurred based on the configured capacity
- If you need to set the snapshot capacity, click the Edit button
|
| Snapshot schedule | Snapshot auto-creation interval- Schedule can be registered after setting snapshot size
- Click the edit button if you need to set a snapshot schedule
- For detailed information about snapshot schedules, see 스냅샷 스케줄 수정하기 reference
|
| Recovery copy | Snapshot name- Displayed when a snapshot exists
- Click the name to go to the snapshot’s detail page
|
| Connection server | Connected Bare Metal Server- To add a Bare Metal Server connection, click the Add button
- To remove a Bare Metal Server connection, click the Disconnect button
|
Table. Block Storage (BM) Detailed Information Items
Reference
For volumes created before December 18, 2025, IOPS and throughput information is not displayed.
Snapshot list
Block Storage(BM) List page lets you view the snapshot of the selected resource.
| Category | Detailed description |
|---|
| Snapshot usage | Total size of stored snapshots |
| Snapshot name | Snapshot name |
| capacity | Snapshot capacity |
| Creation Date/Time | Snapshot creation time |
| Additional features > More | Snapshot management button- Restore: Restore volume from snapshot
- Create restore copy: Generate a restore copy from a snapshot
|
| Delete | Select the snapshots to delete from the snapshot list and delete them all at once. |
Table. Snapshot list tab detailed information items
Caution
- If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
- If the snapshot capacity usage is high (around 90%), replication may be stopped.
- Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically created via schedule), and if the maximum number is exceeded, no further snapshots can be created.
- Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the restored volume can be used after it is reconnected (Mount, Disk Online).
- A recovery copy can only be created once, and it is a separate volume that incurs charges identical to the original.
Reference
- The snapshot creation date and time is based on Asia/Seoul (GMT +09:00).
- When using replication, snapmirror files cannot be deleted.
- When using a Volume Group, set the snapshot schedule on the Volume Group (BM) detail information screen. The created snapshots can be viewed in the Block Storage (BM) snapshot list.
Clone
Block Storage(BM) List page lets you view the replication information of the selected resource.
| Category | Detailed description |
|---|
| Replication Policy | User-configured replication policy |
| Replication cycle | Replication interval of the source set by the user |
| Replication status | Replication progress status according to policy settings |
| Lag Time | Time elapsed since the last successful replication- Available after the replica is created
|
| Volume information | Volume information for original and replica- Classification: Indicates whether it is the original in replication
- Volume Name: The volume name of the original or replica
- Location: The location where the volume was created
- Permissions: User permissions of the volume set according to the replication policy
|
Table. Replication tab detailed information items
Caution
If the snapshot capacity usage is high (around 90%), replication may be stopped.
Reference
- When a replica is created, a copy with the same disk type is generated.
- Replication can be created after configuring the snapshot size.
- If you are using a Volume Group, check the replication information on the Volume Group(BM) list page.
- A replica can modify the connected server when the replication policy is stopped or deleted.
- A replica can use the snapshot feature after the replication policy is deleted.
- If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule in the replica.
On the Block Storage(BM) List page, you can view the tag information of the selected resource and add, modify, or delete it.
| Category | Detailed description |
|---|
| Tag list | Tag list- You can view the Key and Value information of the tag
- Up to 50 tags can be added per resource
- When entering a tag, you can search and select from the list of previously created Keys and Values
|
Table. Block Storage (BM) tag tab item
Work History
Block Storage(BM) List page allows you to view the operation history of the selected resource.
| Category | Detailed description |
|---|
| Task History List | Resource Change History- Operation Time, Resource Type, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, View Operator Information
- Click the Advanced Search button to perform a detailed search
|
Table. Work History Tab Detailed Information Items
Block Storage(BM) Managing Resources
If you need to modify the settings of a created Block Storage (BM) or add or remove connected servers, you can perform the tasks on the Block Storage(BM) Details page.
Edit volume name
You can modify the name of a volume. To rename a volume, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource whose volume name you want to edit. You will be taken to the Block Storage(BM) Details page.
- Click the Edit button for Volume name. The Edit Volume Name popup opens.
- Enter the volume name and click the Confirm button.
Reference
Must start with a letter and can be set using letters, numbers, and special characters (-) within 3 to 28 characters.
Increase capacity
You can increase the volume size. To increase the size, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to expand its capacity. You will be taken to the Block Storage(BM) Details page.
- Click the capacity edit button. The Capacity Edit popup opens.
- After adding the capacity you want to expand (1/~16,384 GB) to the current capacity and entering the total, click the Confirm button.
Caution
- Capacity can be expanded only for the original volume that does not use the snapshot feature.
- Size reduction is not provided.
Modify Snapshot Size
You can modify the capacity of the snapshot storage. To modify the snapshot capacity, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Block Storage(BM) List page: click the resource to modify the snapshot capacity. You will be taken to the Block Storage(BM) Details page.
- Click the Edit button of the Snapshot Capacity item. The Snapshot Capacity Edit popup window opens.
- Set the Use status and generation capacity (%), then click the Confirm button.
- Generation Capacity(%) can be selected in increments of 50 between 100 and ~500.
Caution
- Charges vary depending on snapshot usage and size. (Example: with a volume size of 10 GB and snapshot creation size of 100%, a total of 20 GB is billed.)
- If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
- If the size after modification is smaller than the original, older snapshots will be deleted first.
- When changed to unused, all snapshots will be deleted.
- Replication can be created after setting the snapshot capacity.
- After configuring the snapshot size, it can be added to the Volume Group.
- If the snapshot capacity usage is high (around 90%), replication may be stopped.
- Replicas can use the snapshot feature after the replication policy has been deleted.
Edit Snapshot Schedule
You can modify the automatic snapshot creation interval. To modify the snapshot schedule, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to edit the snapshot schedule. You will be taken to the Block Storage(BM) Details page.
- Click the Edit button for the Snapshot Schedule item. The Snapshot Schedule Edit popup opens.
- Set the snapshot auto creation status and creation interval, then click the Confirm button.
- If you want to automatically create snapshots based on the creation cycle, select automatic creation as enabled.
- Select the generation cycle as daily, hourly, or as weekly, day of week, hourly.
Caution
Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated via schedule), and if the maximum number is exceeded, no further snapshots can be created.
Reference
- The snapshot schedule is based on Asia/Seoul (GMT +09:00).
- You can register a schedule after configuring the snapshot capacity.
- You cannot add it to a Volume Group when configuring a snapshot schedule.
Edit Max IOPS
You can modify the Max IOPS value. To modify the Max IOPS value, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Block Storage(BM) List page, click the resource whose IOPS value you want to modify. You will be taken to the Block Storage(BM) Details page.
- Click the Edit button of Max IOPS. The Max IOPS Edit popup opens.
- After entering the Max IOPS value to change, click the Confirm button.
- The Max IOPS value can be set to a value between 5,000 and 20,000.
Reference
- The Max IOPS value can be modified after the server is initially attached.
- For a recovery copy, the Max IOPS value cannot be modified.
Edit Max Throughput
You can modify the Max Throughput speed. To modify the Max Throughput speed, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- From the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Block Storage(BM) List on the page, click the resource to modify the Throughput speed. You will be taken to the Block Storage(BM) Details page.
- Click the Edit button of Max Throughput. The Max Throughput Edit popup opens.
- After entering the Max Throughput speed to change, click the Confirm button.
- The Max Throughput speed can be set to a value between 250 and 1,000.
Reference
- The Max Throughput speed can be modified after the initial server attach.
- For recovery copies, the Max Throughput speed cannot be adjusted.
Edit Connection Server
You can connect or disconnect the Bare Metal Server, Multi Node GPU Cluster. To modify the connected server, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to edit the connected server. You will be taken to the Block Storage(BM) Details page.
- When adding a connection server, click the Add button in the Connection Server item. The Add Connection Server popup opens.
- After selecting the server you want to connect to, click the Confirm button.
- If you need to disconnect the server, click the Disconnect button in the Connection Server field.
- Be sure to log into the server, perform the disconnect operations (Umount, Disk Offline), and then disconnect.
Caution
- Connect to the server and be sure to perform the disconnect operations (Umount, Disk Offline) before detaching the connected server. Detaching without OS operations may cause a status error (Hang) on the connected server. For detailed information on detaching the server, refer to Detaching the Server.
Reference
- You can connect up to eight Bare Metal Servers created in the same location as the Block Storage.
- There is no limit on the number of volume connections for a Bare Metal Server.
- When adding a connected server, you can use it after performing the connection tasks (Mount, Disk Online) on the server. For detailed information about server connections, refer to Server Connection Guide.
- Connect to the server and be sure to perform the disconnect operations (Umount, Disk Offline) before detaching the connected server. Detaching without OS operations may cause a status error (Hang) on the connected server. For detailed information on detaching the server, refer to Detach Server.
- A replica can modify the connected server when the replication policy is stopped or deleted.
Cancel Block Storage(BM)
You can reduce operating costs by terminating unused Block Storage(BM). However, terminating the service may cause the running service to stop immediately, so you should carefully consider the impact of service interruption before proceeding with the termination.
Caution
- Please note that data cannot be recovered after termination.
- If a connected server exists, you can terminate it after removing all associated resources.
- You can only delete the volume when it is in the Available or Error state.
- If a replication policy is in use, you can cancel it after removing the policy from the associated replica.
- If a Volume Group is being used, you can cancel after disconnecting the associated Volume Group.
- If a recovery copy of the original exists, you can delete the recovery copy before terminating.
To cancel Block Storage, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, select the resource to terminate and click the Terminate Service button.
- After termination is complete, verify on the Block Storage(BM) List page that the resource has been terminated.
1 - Connect to Server
When using a volume on the server, a connect or disconnect operation is required.
On the Block Storage(BM) Details page, after adding a connected server, log in to the server to configure Multi Path and perform connection tasks (Mount, Disk Online). After use, perform disconnection tasks (Umount, Disk Offline) and remove the connected server.
Before using the volume on the connected server, Multi Path configuration is required. Follow the steps below.
Caution
If Multi Path is not configured, service impacts can arise from maintenance activities, failures, and the like.
Linux operating system
Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
On the Block Storage(BM) List page, click the resource to configure Multi Path. You will be taken to the Block Storage(BM) Details page.
In the Connection Server item, verify the server and then connect. Configure Multi Path according to the guide below.
Device Check
- The created volume can be verified with the
fdisk -l command.
Verify DM-Multipath configuration
- In the volume detection process, the Linux system automatically applies Multi Path, which can be verified with the
multipath –ll command. - Volumes with Multi Path applied use Multipath device names such as
/dev/mapper/##### instead of the /dev/sd# format, and can be verified with the fdisk –l command.
iSCSI replacement timeout value setting
- When connecting iSCSI, set the
replacement timeout.
# vi /etc/iscsi/iscsid.conf
node.session.timeo.replacement_timeout = 5
(default 120 값을 5 로 변경)
- After modifying the above, restart the iscsi service.
# systemctl restart iscsid
Windows operating system
Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
On the Block Storage(BM) List page, click the resource to set Multi Path. You will be taken to the Block Storage(BM) Details page.
In the Connection Server item, verify the server and then connect. Configure Multi Path according to the guide below.
Connect to Server (Mount, Disk Online)
To use the volume added to the connected server, you must log into the server and perform the connection tasks (Mount, Disk Online). Follow the steps below.
Linux operating system
Example configuration for server connection
- Server OS: LINUX
- Mount location: /data
- Volume size: 24 GB
- File system: ext3, ext4, xfs etc
- Additional allocated disk: /dev/vdb
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to which you want to connect the server. You will be taken to the Block Storage(BM) Details page.
- Connected Server item, check the server and then connect. Mount the volume according to the guide below.
- Switch to root privileges
Code block. Switch to root privileges - Check Disk
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
Code block. Check disk - Create partition
# fdisk /dev/vdb
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-50331646, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-50331646, default 50331646):
Created a new partition 1 of type 'Linux' and of size 24 GiB.
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
# fdisk /dev/vdb
Command (m for help): n
Partition type:
p primary (0 primary, 0 extended, 4 free)
e extended
Select (default p): p
Partition number (1-4, default 1): 1
First sector (2048-50331646, default 2048):
Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-50331646, default 50331646):
Created a new partition 1 of type 'Linux' and of size 24 GiB.
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Code block. Create partition - Partition format setting (example: ext4)
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part
# mkfs.ext4 /dev/vdb1
mke2fs 1.46.5 (30-Dec-2021)
Writing superblocks and filesystem accounting information: done
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part
# mkfs.ext4 /dev/vdb1
mke2fs 1.46.5 (30-Dec-2021)
Writing superblocks and filesystem accounting information: done
Code block. Partition format setting - Volume Mount
# mkdir /data
# mount /dev/vdb1 /data
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part /data
# vi /etc/fstab
(add) /dev/vdb1 /data ext4 defaults 0 0
# mkdir /data
# mount /dev/vdb1 /data
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part /data
# vi /etc/fstab
(add) /dev/vdb1 /data ext4 defaults 0 0
Code block. Volume mount| Item | Explanation |
|---|
| cat /etc/fstab | This is the filesystem information file for the Linux system. It is used when the server starts. |
| df -h | Check the total disk usage mounted on a Linux system. |
| fdisk -l | Check partition information.- Physical disks are displayed as
/dev/sda, /dev/sdb, /dev/sdc with letters such as a, b, c
- Disk partitions are displayed as
/dev/sda1, /dev/sda2, /dev/sda3 with numbers such as 1, 2, 3
|
Table. Refer to the Mount command
| command | Explanation |
|---|
| m | Check the usage of the fdisk command. |
| n | Create a new partition. |
| p | Verify the updated partition information. |
| t | Change the system ID of the partition. |
| w | Save the partition information and exit the fdisk configuration. |
Table. Refer to the partition creation command (fdisk).
Windows operating system
Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
On the Block Storage(BM) List page, click the resource to connect the server. You will be taken to the Block Storage(BM) Details page.
From the Connected Server item, verify the server and then connect. Follow the guide below to attach the volume (Disk Online).
- Right-click the Windows Start icon and run Computer Management.
- In the Computer Management tree structure, select Storage > Disk Management.
- Check Disk
Disconnect Server (Umount, Disk Offline)
Connect to the server and perform the disconnect operations (Umount, Disk Offline), then you must disconnect the server from the Console. Follow the steps below.
Caution
If you disconnect the server from the console without performing the disconnect operations (Umount, Disk Offlline) on the server, a server state error (Hang) may occur. Be sure to perform the OS operations first.
Linux operating system
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to detach the server connection. You will be taken to the Block Storage(BM) Details page.
- After checking the server in the Connected Server item, connect. Follow the guide below to unmount the volume (Umount).
- Volume Umount
# umount /dev/vdb1 /data
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part
# vi /etc/fstab
(delete) /dev/vdb1 /data ext4 defaults 0 0
# umount /dev/vdb1 /data
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 252:0 0 24G 0 disk
├─vda1 252:1 0 23.9G 0 part [SWAP]
└─vda14 252:14 0 4M 0 part /
└─vda15 252:15 0 106M 0 part /boot/efi
vdb 252:16 0 24G 0 disk
└─vdb1 252:17 0 24G 0 part
# vi /etc/fstab
(delete) /dev/vdb1 /data ext4 defaults 0 0
code block. volume Umount
Windows operating system
Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
On the Service Home page, click the Block Storage(BM) menu. Navigate to the Block Storage(BM) List page.
On the Block Storage(BM) List page, click the resource to detach the server connection. You will be taken to the Block Storage(BM) Details page.
In the Connected Server item, verify the server before connecting. Follow the guide below to detach the volume (Disk Offline).
- Windows Start icon right-click, then run Computer Management
- In the Computer Management tree structure, select Storage > Disk Management
- Right-click the disk to be removed, then run Offline.
2 - Use Snapshot
You can create, delete, or recover a snapshot of a created Block Storage (BM). You can perform these actions on the Block Storage (BM) Details page and the Snapshot List page.
Create Snapshot
Users can create a snapshot at the desired point in time.
guide
A replica can delete the replication policy, set the snapshot size for all block storage within the volume group, and then create a snapshot.
To create a snapshot, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Click the resource to create a snapshot on the Block Storage(BM) List page. Navigate to the Block Storage(BM) Details page.
- Check the setting status of the Snapshot Capacity item.
- Snapshots can be created only when storage space has been secured by configuring snapshot capacity.
- For detailed information, refer to Modify Snapshot Capacity.
- Click the Create Snapshot button. The Create Snapshot popup opens.
- Click the Create button. It creates a snapshot of the current point in time.
- Click the Snapshot List page. You will be taken to the Block Storage(BM) Snapshot list page.
- Check the generated snapshot.
Caution
- If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
- If the usage rate within the snapshot capacity is high (around 90%), replication may be stopped.
- If there is a volume in the Volume Group with snapshot capacity not set, you cannot create a snapshot. Set the snapshot capacity for all volumes first.
- Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated via schedule), and if the maximum number is exceeded, no further snapshots can be created.
Reference
- The snapshot creation time is based on Asia/Seoul (GMT +09:00).
- If you want to automatically create snapshots using a schedule, set the snapshot schedule on the Block Storage(BM) Details page.
- For detailed information about the snapshot schedule, refer to Modify Snapshot Schedule.
- Capacity can be expanded only for the original volume that does not use the snapshot feature.
Recover Snapshot
Block Storage(BM) volumes can be restored from a snapshot. To restore a snapshot, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Block Storage(BM) List Click the resource to restore from a snapshot. Block Storage(BM) Details page will be opened.
- If a server has been added in the Connected Server item, connect to the server and then perform the disconnect tasks (Umount, Disk Offline).
- Click the Snapshot List page. Navigate to the Block Storage(BM) Snapshot List page.
- After checking the Snapshot name and Creation timestamp, click the More button of the snapshot you want to restore.
- Recover button, click it. The snapshot recovery popup opens.
- After verifying the snapshot name and creation time, click the Confirm button. Recover the Block Storage volume from the snapshot.
- Click the Details button. Navigate to the Block Storage(BM) Details page.
- Connection Server If a server has been added to this item, connect to the server and perform the connection tasks (Mount, Disk Online).
Caution
- Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the restored volume can be used after it is reconnected (Mount, Disk Online).
- After the snapshot recovery is completed, all snapshots created after the snapshot used for recovery are deleted.
- When restoring a snapshot, the volume is restored to that point in time.
- If you are using Volume Group(BM), you can perform snapshot recovery from the detail page of Volume Group(BM).
Create a recovery copy
You can create a recovery copy from a snapshot of a Block Storage (BM) volume. To create a snapshot recovery copy, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to restore from a snapshot. You will be taken to the Block Storage(BM) Details page.
- If a server has been added in the Connected Server item, connect to the server and then perform the disconnect tasks (Umount, Disk Offline).
- Click the Snapshot List page. Go to the Block Storage(BM) Snapshot List page.
- After confirming the Snapshot name and Creation timestamp, click the More button of the snapshot you want to create a recovery copy for.
- Click the Create Recovery button. The snapshot recovery creation popup opens.
- After entering the Recovery volume name, click the Create button. A popup notifying the creation of the recovery image will appear.
- Click the Confirm button. The recovery copy creation request is complete.
Caution
- Only one recovery copy can be created per original.
- A recovery copy is a separate volume created with the same capacity as the original, and it incurs additional costs.
- If you are using Volume Group(BM), you can create a recovery copy on the detail page of Volume Group(BM).
Delete Snapshot
You can select a snapshot to delete. To delete a snapshot, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to delete the snapshot. You will be taken to the Block Storage(BM) Details page.
- Click Snapshot List. It navigates to the Block Storage(BM) Snapshot List page.
- After confirming the Snapshot name and creation time, click the More button of the snapshot you want to delete.
- Click the Delete button. The snapshot will be removed from the Snapshot List page.
- After selecting the snapshots to delete from the snapshot list, you can click the Delete button at the top of the list to delete them all at once.
Reference
- Snapshots that contain snapmirror in the snapshot name cannot be deleted. snapmirror is included in the snapshot name when a replication is created.
- If you are using Volume Group(BM), you can delete snapshots from the detail page of Volume Group(BM).
3 - Use Replication
After creating a replica of the generated Block Storage(BM) in another location, you can synchronize it periodically. You can perform the tasks on the Block Storage(BM) Details page and the Replication page.
Reference
- The kr-south region does not provide Block Storage (BM) replication functionality.
Create Clone
You can create a replica volume in a different location.
Caution
Clones can only be created from the original volume.
To create a replica volume, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource for which you want to create a replica. You will be taken to the Block Storage(BM) Details page.
- Check the setting status of the Snapshot Capacity item.
- Replication can be created only when storage space is available through snapshot capacity configuration.
- For detailed information, refer to Modify Snapshot Capacity.
- Click the Create Clone button. The Create Clone popup opens.
- Enter the Replication location, Replication volume name, and Replication schedule, then click the Create button. It creates a replica with the same disk type.
- Replication Location: Select a location different from the original Block Storage(BM) volume.
- Replication Volume Name: Start with an English letter and use English letters, numbers, and special characters (
-) to enter 3 to 28 characters. - Replication interval: Select from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed using the interval below.
- Daily: every day 23:59:00
- Weekly: Every Sunday 23:59:00
- Monthly: 1st day of each month 23:59:00
- Click the Clone page.
You will be taken to the Clone page. - Check the replication information.
- When selecting the volume name of the source or replica, you are taken to the volume’s Block Storage(BM) Details page.
Reference
- When a replica is created, a copy with the same disk type is generated.
- After setting the snapshot size, you can create a replica, and the disk type of the created replica is the same as the original.
- If the snapshot capacity utilization is high (around 90%), replication may be stopped.
- After setting the snapshot capacity, volumes added to the Volume Group can be replicated at the group level on the Volume Group page.
- You can create one replica per volume, and data transfer charges apply for cross‑region replication.
- A volume created by cloning cannot be added to a Volume Group.
- If you are using a Volume Group, you can view replication information in the Volume Group (BM).
Edit replication policy
You can change the replication status by modifying the replication policy.
Caution
During replication, the replication interval and replication policy cannot be modified.
To modify the replication policy, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- On the Block Storage(BM) List page, click the resource to edit the replication policy. You will be taken to the Block Storage(BM) Details page.
- Click the Replication page. Go to the Block Storage(BM) Replication page.
- Click the Edit button of the Replication Policy. The Edit Replication Policy popup opens.
- Use: performs replication. If it is Paused, you can change it to Use.
- Pause: Temporarily stops replication. If use, you can modify to Pause.
- Delete: Delete the replica. If Paused, it can be changed to Delete, and after deletion, replication cannot be used again.
- Check the updated Replication Policy on the Block Storage(BM) Replication page.
Caution
- When deleting a policy, please note the following.
- After the policy is deleted, the replica will not be reverted to the original, and you cannot create a replica.
- After deleting the policy, you cannot connect to existing replicas, and you can only create new replicas.
- Data stored only in the replica after a pause will be deleted when replication is used again.
- When using a replication policy, replicas are in Read only state and cannot be modified. Unmount from all connected resources before using replication.
- You can mount on the connected server only when the replication policy is deleted or paused.
Edit replication cycle
You can change the synchronization interval between the original and the replica by modifying the replication interval.
Caution
During replication, Replication Cycle and Replication Policy cannot be modified.
To modify the replication interval, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Block Storage(BM) menu. You will be taken to the Block Storage(BM) List page.
- Click the resource to modify the replication interval on the Block Storage(BM) List page. You will be taken to the Block Storage(BM) Details page.
- Click the Replication page. Go to the Block Storage(BM) Replication page.
- Click the Edit button of Replication Cycle. Replication Cycle Edit popup opens.
- Replication interval: Select from 5 minutes, 1 hour, daily, weekly, monthly. Replication will be performed using the interval below.
- Daily: 23:59:00
- Weekly: Every Sunday 23:59:00
- Monthly: 1st day of each month 23:59:00
- Check the modified Replication Interval on the Block Storage(BM) Replication page.
4 - Use Volume Group
The Volume Group(BM) service allows you to configure up to 16 Block Storage(BM) volumes as a group, enabling the creation of consistent point-in-time snapshots and replications.
Users can create the service by entering the required information for the Volume Group (BM) and selecting detailed options through the Samsung Cloud Platform Console.
Create Volume Group (BM)
You can create and use a Volume Group (BM) service in the Samsung Cloud Platform Console.
To create a Block Storage, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- Click the Volume Group(BM) menu. Navigate to the Volume Group(BM) List page.
- On the Volume Group(BM) page, click the Volume Group(BM) Create button. You will be taken to the Volume Group(BM) Create page.
| Category | Required | Detailed description |
|---|
| Volume Group name | Required | Volume Group name- must start with an English letter and be 3 to 28 characters using English letters, numbers, and special characters (
-)
- cannot be modified after service creation
|
| target volume | Required | Add target volume to Volume Group- After clicking the Add button, select the target volume in the add target popup
- Target volume criteria
- Snapshot auto-creation, creation interval: Not used
|
Table. Volume Group (BM) Service Information Input Items
- Click the Create button.
- When creation is complete, check the created resources on the Volume Group(BM) List page.
Reference
- When adding a target volume, you can add the corresponding volume to the Volume Group (BM).
- Snapshot capacity: Set
- Automatic snapshot creation, creation interval: unused
- Clone: Unused
- You can add up to 16 target volumes.
Check detailed information of Volume Group (BM)
Volume Group(BM) service allows you to view and edit the full resource list and detailed information. Volume Group(BM) Details page consists of Details, Snapshot List, Replication, Operation History tabs.
To view detailed information about the Volume Group(BM) service, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource to view detailed information. It navigates to the Volume Group(BM) Detail page.
- Volume Group(BM) Details page displays status information and additional feature information, and consists of Details, Snapshot List, Replication, Tags, Operation History tabs.
| Category | Detailed description |
|---|
| Volume Group status | Volume Group status- Available: Creation complete, server connection possible
- Deleting: Service termination in progress
- Editing: Changing settings
- Error Deleting: Abnormal state during deletion
- Error: Abnormal state during creation
|
| Clone creation | Create a replica at another location- Replication is not possible if the snapshot size is not set or a replication policy already exists
|
| Create snapshot | Create a snapshot at a specific point in time |
| Service termination | Cancel service button |
Table. Status information and additional features
Reference
In the case of a recovery copy, the snapshot list and replication tabs are not displayed.
Detailed information
Volume Group(BM) List page allows you to view detailed information of the selected resource and edit the information if needed.
| Category | Detailed description |
|---|
| Service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform- In Volume Group (BM), it refers to the Volume Group SRN
|
| Resource Name | Resource Name- In Volume Group (BM), it refers to the Volume Group name
|
| Resource ID | Service’s unique resource ID |
| constructor | User who created the service |
| Creation date and time | Service creation timestamp |
| Editor | User who modified the service |
| Modification date | Date and time the service was modified |
| Volume Group name | Volume Group name |
| Category | Distinguish original status related to duplication |
| Storage Volume Group name | Volume Group name within the storage device- Identification information of the Volume Group used for analysis when failures or issues occur
|
| Snapshot schedule | Snapshot auto-creation interval- Schedule can be registered after setting snapshot capacity
- Click the edit button if you need to set a snapshot schedule
|
| Recovery copy | Snapshot name of the Volume Group- Displayed when a snapshot exists
- Click the name to go to the snapshot’s detail page
|
| target volume | Block Storage (BM) added to the Volume Group- Disk Type: Disk type of the volume
- Capacity: Capacity of the volume
- Snapshot Capacity: Capacity of the snapshot storage set for the volume
|
Table. Volume Group (BM) Detailed Information Items
Snapshot list
Volume Group(BM) resource list page allows you to view the snapshot of the selected resource.
| Category | Detailed description |
|---|
| Snapshot name | Snapshot name |
| Creation Date/Time | Snapshot creation time |
| Additional features > More | Snapshot management button- Restore: Restore volume from snapshot
- For details on snapshot restoration, see 스냅샷 복구하기 see
- Create restore point: Create a restore point from snapshot
- For details on creating a restore point, see 복구본 생성하기 see
- Delete: Delete snapshot
- For details on deleting a snapshot, see 스냅샷 삭제하기 see
|
Table. Snapshot list tab detailed information items
Caution
- When a snapshot is created in a Volume Group, the snapshot is created in Block Storage (BM).
- When using Volume Group snapshots, manage the snapshot capacity and count of the target volume.
- If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
- If the snapshot capacity usage is high (around 90%), replication may be stopped.
- Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated through scheduling), and if the maximum number is exceeded, no additional snapshots can be created.
- Snapshot recovery must be performed while all connected servers are disconnected (Umount, Disk Offline), and the restored volume can be used after it is reconnected (Mount, Disk Online).
Reference
- The snapshot creation time is based on Asia/Seoul (GMT +09:00).
- When using replication, snapmirror files cannot be deleted.
- When using a Volume Group, set the snapshot schedule on the Volume Group (BM) detail information screen. The created snapshots can be viewed in the Block Storage (BM) snapshot list.
Clone
Volume Group(BM) Resource List page allows you to view the replication information of the selected resource.
| Category | Detailed description |
|---|
| Replication Policy | User-configured replication policy |
| Replication cycle | Replication interval of the source set by the user |
| Replication status | Replication progress status according to policy settings |
| Lag Time | Time elapsed since the last successful replication- Available after the replica is created
|
| Volume information | Volume information for the source and replica- Classification: Indicates whether it is the original in replication
- Volume Group name: Name of the Volume Group of the source or replica
- Location: Location where the volume was created
- Permissions: User permissions of the volume set according to the replication policy
|
Table. Replication tab detailed information items
Caution
- If the snapshot capacity usage is high (around 90%), replication may be stopped.
Reference
- When a clone is created, a replica with the same disk type is generated.
- Replication can be created after setting the snapshot capacity.
- If you are using a Volume Group, view the replication information on the Volume Group (BM) resource list page.
- Replica Block Storage can modify the attached server when the replication policy is paused or deleted.
- Replica Block Storage can use the snapshot feature after the replication policy is deleted.
- If the replication policy is stopped or the replication status is completed, you can modify the policy and schedule on the replica.
Volume Group(BM) List page lets you view the tag information of the selected resource, and you can add, modify, or delete it.
| Category | Detailed description |
|---|
| Tag list | Tag list- You can view the Key, Value information of the tag
- Up to 50 tags can be added per resource
- When entering a tag, you can search and select from the list of previously created Keys and Values
|
Table. Volume Group (BM) Tag Tab Items
Work History
Volume Group(BM) Resource List You can view the operation history of the selected resource on this page.
| Category | Detailed description |
|---|
| Task History List | Resource Change History- Operation Time, Resource Type, Resource ID, Resource Name, Operation Details, Event Topic, Operation Result, View Operator Information
- Click the Advanced Search button to perform a detailed search
|
Table. Work History Tab Detailed Information Items
Volume Group(BM) Managing Resources
If you need to modify the settings of a created Volume Group (BM) or add or remove target volumes, you can perform the operation on the Volume Group(BM) Details page.
Edit Snapshot Schedule
You can modify the automatic snapshot creation interval. To modify the snapshot schedule, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. Navigate to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource to modify the snapshot schedule. You will be taken to the Volume Group(BM) Details page.
- Click the Edit button for the Snapshot Schedule item. The Snapshot Schedule Edit popup opens.
- Set the snapshot auto creation status and creation interval, then click the Confirm button.
- If you want to automatically create snapshots based on the Creation Cycle, select Automatic Creation as Enabled.
- Generation cycle can be selected daily, hourly, or weekly, day of week, hourly. Please select.
Caution
When using Volume Group snapshots, manage the snapshot capacity and count of the target volume.
- Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated through scheduling), and if the maximum number is exceeded, no additional snapshots can be created.
Reference
The snapshot schedule is based on Asia/Seoul (GMT +09:00).
Edit target volume
You can add or detach the target volume. To modify the target volume, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource to edit the target volume. You will be taken to the Volume Group(BM) Details page.
- If you are adding a target volume, click the Add button of the Target Volume item. The Add Volume popup window opens.
- When disconnecting a volume, click the Disconnect button in the Target Volume item.
- After selecting the volume you want to add, click the Confirm button.
Caution
If the replication policy of the Volume Group is enabled, the target volume cannot be modified.
Reference
- When adding a target volume, you can add the corresponding volume to the Volume Group (BM).
- Snapshot capacity: setting
- Automatic snapshot creation, creation interval: unused
- Clone: Unused
- You can add up to 16 target volumes.
Using Volume Group (BM) Snapshots
You can create, delete, or recover using snapshots for the created Volume Group (BM). You can perform these actions on the Volume Group (BM) Details page and the Snapshot List page.
Creating a Snapshot
Users can create a snapshot at the desired point in time.
guide
- A replica can delete the replication policy, set the snapshot size for all block storage within the volume group, and then create a snapshot.
- Recovery images cannot create snapshots.
To create a snapshot, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- From the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource to create a snapshot. You will be taken to the Volume Group(BM) Details page.
- Click the Create Snapshot button. The Create Snapshot popup window opens.
- Click the Confirm button. Generates a snapshot of the current point in time.
- Click the Snapshot List page. Navigate to the Volume Group(BM) Snapshot list page.
- Check the generated snapshot.
Caution
- When creating a snapshot in a Volume Group, a snapshot is also created on the connected target volume.
- Manage the snapshot capacity and number of snapshots for the target volume to use Volume Group snapshots.
- If the maximum number of snapshots or the snapshot space threshold (around 90%) is exceeded, older snapshots are deleted first.
- If the snapshot capacity usage is high (around 90%), replication may be stopped.
- Snapshots can be created up to a maximum of 1,023 (with up to 128 automatically generated via schedule), and if the maximum number is exceeded, no further snapshots can be created.
Reference
- The snapshot creation time is based on Asia/Seoul (GMT +09:00).
- The snapshot storage space is applied based on the settings you configured on the target volume’s Block Storage(BM) Details page.
- If you want to automatically create snapshots using a schedule, set the snapshot schedule on the Volume Group(BM) Details page.
- For detailed information about snapshot schedules, see Update Snapshot Schedule.
Recover Snapshot
You can restore all target volumes of the Volume Group(BM) from a snapshot. To restore from a snapshot, follow the steps below.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. Navigate to the Volume Group(BM) List page.
- Volume Group(BM) List On the page, click the resource to restore from a snapshot. Volume Group(BM) Details You will be taken to the page.
- Click the volume name of the volume added to the Target volume to go to the Block Storage(BM) Details page.
- If a server has been added in the Connected Server item, connect to the server and then perform the disconnect operations (Umount, Disk Offline).
- On the Volume Group(BM) Details page, click the Snapshot List page. You will be taken to the Volume Group(BM) Snapshot List page.
- After checking the Snapshot name and Creation time, click the More button of the snapshot you want to restore.
- Click the Recover button. The snapshot recovery popup will open.
- After verifying the Snapshot name and Creation time, click the Confirm button. The target volumes will be restored from the snapshot.
- Click the Detailed Information button. It navigates to the Volume Group(BM) Detailed page.
- Click the volume name of the volume added to the Target volume. It will navigate to the Block Storage (BM) Details page.
- If there is a server added in the Connection Server item, after connecting to the server, perform the connection tasks (Mount, Disk Online).
Caution
- Snapshot recovery must be performed when all target volumes on the connected server are unmounted (Umount, Disk Offline), and the recovered volume can be used after being remounted (Mount, Disk Online).
- After the snapshot recovery is completed, all snapshots created after the snapshot used for recovery will be deleted.
Create a backup
You can create a recovery copy from a snapshot of the target volume. To create a snapshot recovery copy, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource for which you want to create a recovery copy. You will be taken to the Volume Group(BM) Details page.
- From the Volume Group(BM) Details page, click the Snapshot List page. You will be taken to the Volume Group(BM) Snapshot List page.
- After checking the snapshot name and creation timestamp, click the More button of the snapshot for which you want to create a recovery copy.
- Click the Create Recovery button. The snapshot recovery creation popup opens.
- After entering Prefix, click the Confirm button. A popup indicating that a backup is being created will open.
- The recovery copy’s name is created as the entered Prefix value + original Block Storage name.
- Click the Create button. The backup creation request has been completed.
Caution
- Only one recovery copy can be created per original.
- A recovery copy is a separate volume created with the same capacity as the original, and it incurs additional costs.
Delete snapshot
You can select a snapshot to delete. To delete a snapshot, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource to delete the snapshot. You will be taken to the Volume Group(BM) Details page.
- Click Snapshot List. Navigate to the Volume Group (BM) Snapshot List page.
- After confirming the Snapshot name and creation time, click the More button of the snapshot you want to delete.
- Click the Delete button. The snapshot will be removed from the Snapshot List page.
Reference
When using replication, snapmirror files cannot be deleted.
Using replication for Volume Group (BM)
The created Volume Group (BM) can be synchronized at regular, consistent points after creating a replica at another location. You can perform tasks on the Volume Group(BM) Details page and the Replication page.
Create a Clone
You can create a replicated Volume Group and volume at a different location.
guide
Clones and recovery copies cannot create replicas.
To create a copy, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource for which you want to create a replica. You will be taken to the Volume Group(BM) Details page.
- Click the Create Clone button. The Create Clone popup opens.
- Enter Replication Location, Replication Volume Group, Replication Block Storage Name Prefix, and Replication Interval, then click the Create button. It creates a replica Block Storage volume with the same Volume Group and disk type as the source.
- Replication Location: Select a location different from the original Volume Group (BM).
- Clone Volume Group name: Start with an English letter and use English letters, numbers, and special characters (
-) to enter 3~28 characters. - Replication Block Storage Name Prefix: Start with an English letter and use English letters, numbers, and special characters (
-) to enter 3 to 28 characters.- A replica Block Storage (BM) is created with a volume name of ‘Replica Block Storage name Prefix + original Block Storage volume name’.
- Replication interval: Select from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed at the selected interval.
- Daily: daily 23:59:00
- Weekly: Every Sunday 23:59:00
- Monthly: 1st of each month 23:59:00
- Click the Clone page. You will be taken to the Clone page.
- Check the replication information.
- When selecting the Volume Group name of the original or replica, you will be taken to the Volume Group(BM) Details page.
Reference
- When creating a replica in a Volume Group, a replica Volume Group and Block Storage (BM) are created.
- The replica Block Storage has the same disk type as the original.
- You can create one replica per Volume Group, and data transfer charges apply for cross‑region replication.
Edit replication policy
You can change the replication status by modifying the replication policy.
Caution
During replication, you cannot modify the replication interval or replication policy.
To modify the replication policy, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Go to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource you want to modify the replication policy for. You will be taken to the Volume Group(BM) Details page.
- Click the Clone page. Navigate to the Volume Group(BM) Clone page.
- Click the Edit button of the Replication Policy. The Edit Replication Policy popup opens.
- Enabled: performs replication. If Paused, you can modify it to Enabled.
- Pause: Temporarily stops replication. If Use, it can be changed to Pause.
- Delete: Delete the replica. Paused can be changed to Delete, and after deletion you cannot use replication again.
- Check the modified Replication Policy on the Volume Group(BM) Replication page.
Caution
- When deleting a policy, please note the following.
- After the policy is deleted, the replica does not revert to the original, and you cannot create a replica.
- After deleting the policy, you cannot connect to existing replicas, and you can only create new replicas.
- After a pause, data stored only in the replica will be deleted when replication is used again.
- When using a replication policy, replicas are in Read only state and cannot be modified. Unmount from all connected resources before using replication.
Edit replication interval
You can change the synchronization interval between the original and the replica by modifying the replication interval.
Caution
You cannot modify the replication interval or replication policy while replication is in progress.
To modify the replication interval, follow these steps.
- Click the All Services > Storage > Block Storage(BM) menu. Navigate to the Service Home page of Block Storage(BM).
- On the Service Home page, click the Volume Group(BM) menu. You will be taken to the Volume Group(BM) List page.
- On the Volume Group(BM) List page, click the resource whose replication schedule you want to modify. You will be taken to the Volume Group(BM) Details page.
- Click the Clone page. Navigate to the Volume Group (BM) Clone page.
- Click the Edit button of Replication Cycle. The Edit Replication Cycle popup opens.
- Replication interval: Select from 5 minutes, 1 hour, daily, weekly, or monthly. Replication will be performed at the selected interval.
- Daily: 23:59:00
- Weekly: Every Sunday 23:59:00
- Monthly: 1st day of each month 23:59:00
- Check the modified replication interval on the Volume Group(BM) Replication page.
Cancel Volume Group (BM)
You can delete an unused Volume Group (BM).
Volume Group(BM) has no separate termination procedure, and it is automatically deleted when you disconnect all volumes in the target volume item.
Caution
Be careful, as it cannot be restored after cancellation.