The processing time (in seconds) described here is estimated on the assumption that one snapshot operation is performed while no I/O is issued and no other operation is being performed. Estimate the processing time based on the table below.
-
The processing time for restoration and deletion varies depending on totalCapacity [MiB] and snapshotConcordanceRate [%] of the volume.
-
The processing time for PrepareAndFinalize and Prepare includes the time required for S-VOL creation.
-
The processing time for restoration might be about twice as long as the time described in the table below depending on the target generation of restoration and the amount of differential data between the copy-source volume and the copy-destination volume of restoration. To restore data from a generation other than the latest one or from a generation of S-VOL to which data is written, estimate the processing time by doubling it.
-
If the load of the copy processing of restoration has a high impact on I/O, the copy processing might be stopped by the storage controller. If the copy processing does not progress even if the storage node is not overloaded, collect the dump log file for the storage node and contact customer support.
-
A maximum of 500 restore operations can be requested at the same time in a system. This upper limit is set because the time required for restoration may take long due to the match rate or suppression of copy processing. If more than 500 restore operations are requested, the KARS06143-E message will be returned, and the restore operations will fail.
|
totalCapacity [GiB] |
snapshotConcordanceRate [%] |
Prepare and take a snapshot (PrepareAndFinalize) [sec] |
Prepare(Prepare) [sec] |
Take a snapshot (Finalize) [sec] |
Restore [sec] |
Delete [sec] |
|
|---|---|---|---|---|---|---|---|
|
Data reduction disabled |
Data reduction enabled |
||||||
|
51200 |
100 |
36 |
38 |
0 |
9727 |
10778 |
1350 |
|
16384 |
100 |
14 |
13 |
0 |
3723 |
3572 |
573 |
|
4096 |
100 |
8 |
8 |
0 |
961 |
903 |
162 |
|
1024 |
100 |
7 |
6 |
0 |
241 |
229 |
54 |
|
256 |
100 |
6 |
6 |
0 |
61 |
64 |
29 |
|
128 |
100 |
8 |
6 |
0 |
60 |
34 |
22 |
|
128 |
75 |
- |
- |
- |
2583 |
1431 |
44 |
|
128 |
50 |
- |
- |
- |
5045 |
2911 |
74 |
|
128 |
0 |
- |
- |
- |
9729 |
6214 |
101 |
|
-: Not available |
|||||||
You can delete all snapshot volumes (S-VOL or P/S-VOL) created from the P-VOL by running the snapshot deletion command with the volume ID of the P-VOL and true specified for masterVolumeId and snapshotTree (for the REST API) and for --master_volume_id and --snapshot_tree (for the CLI).
The deletion time can be calculated as follows:
Number of snapshot volumes1 x deletion time per volume [sec] + snapshot configuration deletion time [sec] + 600 seconds2
1. Number of all the S-VOLs or P/S-VOLs that were created from the specified P-VOL.
2. Waiting time for copy stop processing required only when conflict with snapshot copy processing within the system occurs.
The deletion time per volume and snapshot configuration deletion time vary depending on the size of the P-VOL as follows:
|
Size of the P-VOL [GiB] |
Deletion time per volume [sec] |
Snapshot configuration deletion time [sec] |
|---|---|---|
|
128 |
10 |
4 |
|
256 |
10 |
4 |
|
1024 |
10 |
4 |
|
4096 |
11 |
10 |
|
8192 |
11 |
15 |
|
16384 |
15 |
32 |
|
32768 |
19 |
64 |
|
51200 |
24 |
92 |
|
65536 |
29 |
107 |
|
98304 |
41 |
161 |