Renaming a chunk to a nonexistent device
To rename a chunk to a nonexistent device, specify the new path name, but restore the storage spaces after you install the physical device. This option is useful if you need to rename a chunk and it is convenient to perform a cold restore before you install the new device. When the new chunk device is ready, you can perform a warm restore of a storage space onto it.
About this task
You can combine renaming chunks with existing devices and renaming chunks with nonexistent devices in the same rename operation. This example shows how to rename a single chunk to a nonexistent device name.
The following table lists example values for the chunks
used in this example.
Storage space | Old chunk path | Old offset | New chunk path | New offset |
---|---|---|---|---|
sbspace1 | /chunk3 | 0 | /chunk3N | 0 |
To rename a chunk to a nonexistent device:
Procedure
- Rename the chunk with the following command: onbar -r -rename -p /chunk3 -o 0 -n /chunk3N -o 0
- When you see the following prompt, enter y to
continue:
The chunk /chunk3N does not exist. If you continue, the restore may fail later for the dbspace which contains this chunk. Continue without creating this chunk? (y/n)
The chunk /chunk3 is renamed to /chunk3N, but the data is not yet restored to /chunk3N.
- Perform a level-0 archive.
- Add the physical device for /chunk3N.
- Perform a warm restore of sbspace1 with the onbar -r sbspace1 command.
- Perform a level-0 archive.