Backing Up the Store

This section describes the example use case.

In this example, let us consider a secure KVStore that is deployed on 2 storage nodes with capacity 3 and replication factor 2. The storage nodes are on the host phoenix581601 at ports 8000 and 7000. Let us call the storage nodes as storage node 1 (sn1) and storage node 2 (sn2).

You can check the topology of this store by pinging it using the runadmin utility. This will help you identify the name of the store, the replication masters and the running status of the store.

kv->ping

Output:

Pinging components of store mystore based upon topology sequence #112
100 partitions and 2 storage nodes
Time: 2025-05-14 07:21:38 UTC   Version: 25.1.1
Shard Status: healthy: 3 writable-degraded: 0 read-only: 0 offline: 0 total: 3
Admin Status: healthy
Zone [name=Cloud id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]   RN Status: online: 6 read-only: 0 offline: 0 maxDelayMillis: 0 maxCatchupTimeSecs: 0
Storage Node [sn1] on phoenix581601: 8000    Zone: [name=Cloud id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]    Status: RUNNING   Ver: 25.1.1 2025-01-09 18:45:42 UTC  Build id: f6749f469c66 Edition: Enterprise    isMasterBalanced: true        serviceStartTime: 2025-05-14 06:04:25 UTC
              Admin [admin1]                            Status: RUNNING,MASTER              serviceStartTime: 2025-05-14 06:04:52 UTC         stateChangeTime: 2025-05-14 06:04:51 UTC            availableStorageSize: 2 GB
              Rep Node [rg1-rn1]         Status: RUNNING,REPLICA sequenceNumber: 1,156 haPort: 8011 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:44:04 UTC              stateChangeTime: 2025-05-14 06:44:46 UTC delayMillis: 0 catchupTimeSecs: 0
              Rep Node [rg2-rn1]         Status: RUNNING,MASTER sequenceNumber: 1,456 haPort: 8012 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:44:34 UTC              stateChangeTime: 2025-05-14 06:44:37 UTC
              Rep Node [rg3-rn1]         Status: RUNNING,MASTER sequenceNumber: 1,392 haPort: 8013 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:45:05 UTC              stateChangeTime: 2025-05-14 06:45:08 UTC
Storage Node [sn2] on phoenix581601: 7000    Zone: [name=Cloud id=zn1 type=PRIMARY allowArbiters=false masterAffinity=false]    Status: RUNNING   Ver: 25.1.1 2025-01-09 18:45:42 UTC  Build id: f6749f469c66 Edition: Enterprise    isMasterBalanced: true        serviceStartTime: 2025-05-14 06:28:18 UTC
              Admin [admin2]                            Status: RUNNING,REPLICA              serviceStartTime: 2025-05-14 06:33:02 UTC         stateChangeTime: 2025-05-14 06:33:02 UTC            availableStorageSize: 2 GB
              Rep Node [rg1-rn2]         Status: RUNNING,MASTER sequenceNumber: 1,156 haPort: 7011 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:44:17 UTC              stateChangeTime: 2025-05-14 06:44:45 UTC
              Rep Node [rg2-rn2]         Status: RUNNING,REPLICA sequenceNumber: 1,456 haPort: 7012 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:44:49 UTC              stateChangeTime: 2025-05-14 06:44:53 UTC delayMillis: 0 catchupTimeSecs: 0
              Rep Node [rg3-rn2]         Status: RUNNING,REPLICA sequenceNumber: 1,392 haPort: 7013 availableStorageSize: 323 GB storageType: HD              serviceStartTime: 2025-05-14 06:45:17 UTC              stateChangeTime: 2025-05-14 06:45:23 UTC delayMillis: 0 catchupTimeSecs: 0

You can see that the name of the store is mystore and it has 3 shards. The replication masters are rg1-rn2, rg2-rn1 and rg3-rn1. The store is in Running state.