restore
Restores the local cluster or the entire
cluster system.
Modes
Privileged EXEC mode
Usage Guidelines
A prompt appears to choose between restoring the Entire cluster or the Local cluster.
If the system detects that any blades to be restored are not in service, it prompts for confirmation of the blades' IP addresses before proceeding with the restore operation.
Examples
The following example shows how to restore the Entire cluster.
device# restore Number Created on Patch Version File Size ------- ----------------------------- ----------------------------- ----------------------------- 1 2025-03-13 02:32:22 GMT 7.1.1.0.203 2.6GB 2 2025-05-07 06:50:04 GMT 7.1.1.0.307 4.2GB 3 2025-05-07 08:31:51 GMT 7.1.1.0.367 4.5GB % This cluster has internet connectivity. Before restoring the backup, ensure there are no duplicate clusters with the same configuration running, as this could lead to conflicts. Please ensure the backup is available on all nodes in the cluster; otherwise the restore process will fail. Please choose a backup Number to restore or 'No' to cancel: 3 This action will reboot the system. Do you want to restore the "entire cluster" or only the "local blade" Option Description -------- ------------------------------------------------------------------ Entire Triggers the restore process on all blades. Local Triggers the restore process on the current blade only. Exit Cancels and exits. Enter your choice [Entire/Local/Exit]: Entire Not all blade(s) are in-service, try to force restore cluster using remote command The following blade IPs will execute the restore operation using each blade's respective backup. Blade IP: 11.11.0.11 Blade IP: 11.11.0.10 Please confirm these IP address all correct and perform the restore? (or input 'no' to cancel)? [confirmed/no] confirmed Starting to restore current system, and then reload system if successfully trigger restore process Remote restore cluster with 20250507083151 2025-05-15 05:24:44 1: 11.11.0.11 Status: CHECKING OK 2: 11.11.0.10 Status: CHECKING OK 2025-05-15 05:24:46 1: 11.11.0.11 Status: RESTORING 2: 11.11.0.10 Status: RESTORING 2025-05-15 05:30:40 1: 11.11.0.11 Status: RESTORING OK 2: 11.11.0.10 Status: RESTORING OK
The following example shows how to
restore the Local
cluster.
device# restore Number Created on Patch Version File Size ------- ----------------------------- ----------------------------- ----------------------------- 1 2025-03-13 02:32:22 GMT 7.1.1.0.203 2.6GB 2 2025-05-15 07:58:58 GMT 7.1.1.0.203 2.6GB 3 2025-05-15 09:30:16 GMT 7.1.1.0.385 3.1GB % This cluster has internet connectivity. Before restoring the backup, ensure there are no duplicate clusters with the same configuration running, as this could lead to conflicts. Please ensure the backup is available on all nodes in the cluster; otherwise the restore process will fail. Please choose a backup Number to restore or 'No' to cancel: 3 This action will reboot the system. Do you want to restore the "entire cluster" or only the "local blade" Option Description -------- ------------------------------------------------------------------ Entire Triggers the restore process on all blades. Local Triggers the restore process on the current blade only. Exit Cancels and exits. Enter your choice [Entire/Local/Exit]: Local Starting to restore current system, and then reload system if successfully trigger restore process 3209347 blocks All services are down. Make sure all other services are Online before any operations. Execute "#show service" to show other services. 6443798 blocks 3209347 blocks 1 block Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.10.0-1062.rks_7.1.1.0.5.el7.x86_64 Found initrd image: /boot/initramfs-3.10.0-1062.rks_7.1.1.0.5.el7.x86_64.img done rks-boot: saved_entry=rootfs3-94cfeba3-b366-41dc-b97d-d912b32e7b01 Rebooting.
History
| Release version | Command history |
|---|---|
| 3.5.1 | This command was introduced. |
| 7.1.1 | This command is modified. |