Skip to content

Latest commit

 

History

History
73 lines (49 loc) · 4.12 KB

r1soft-cdp-bare-metal-restore-procedures.md

File metadata and controls

73 lines (49 loc) · 4.12 KB
copyright lastupdated keywords subcollection
years
2017, 2024
2024-11-19
bare-metal

{{site.data.keyword.attribute-definition-list}}

Restoring your server from an R1Soft® image

{: #restoring-your-server-from-an-r1soft-image}

Use this procedure to complete a restore to public or private {{site.data.keyword.BluVirtServers_full}} or {{site.data.keyword.BluBareMetServers_full}}. Use this process if a server failure causes data or OS loss. This process restores all file system blocks that are backed up (including the OS and any files that were not excluded from backups). {: shortdesc}

Do not use this process if the restoration of a subset of files is the objective. To restore only the files, see R1Soft® Wiki{: external}.

Before you begin

{: #byb-restore-r1soft}

  • Go to your console's device menu.
  • Make sure that you have any necessary account permissions and device access. Only the account owner, or a user with the Manage users Classic infrastructure permission, can adjust the permissions.

Restoring your virtual device

{: #restoring-your-virtual-device}

  1. From the Device list, click into the device that you want you restore.

  2. Click the Actions menu and choose Boot from image you get a list of private images.

  3. Choose Public images from the menu.

  4. Select the appropriate R1Soft® agent boot image for your version of R1Soft® server (example: serverbackup-bootcd-agent-6.14.2.iso) and click Boot from this image.

  5. From the Device Details page for the server that you are restoring, click Actions > KVM Console.

  6. After the console is up and the image boots, you will see a Debian bootloader screen with some options. Press the Enter key to boot from the default option.

  7. After the OS boots, type sudo Ceni and press Enter to set up networking for the ISO.

    Use your virtual server networking information. {: tip}

  8. Choose Yes to configure the networking.

  9. Enter networking configuration details from device details in the Control portal.

  10. Choose Yes when prompted to restart networking.

  11. Optionally, type passed root to set a root password for SSH logins and type service ssh start to allow SSH login. This step might be useful if your KVM console is slow.

  12. Type service cdp-agent restart (This command starts the Continuous Data Protection for Files agent if it isn't already running).

Restoring your bare metal device

{: #restoring-your-bare-metal-device}

  1. From the Device list, click into the bare metal server that you want you restore.

  2. Click the Actions menu and select Bare metal restore.

    Configuring the Tivoli Continuous Data Protection for Files agent and networking takes about 10 minutes after the ISO boots. You don't need to log in to or adjust the ISO after it boots. {: note}

  3. After 10 minutes, confirm that the CDP and networking started successfully by testing the agent with the R1soft® SBM.

Using Bare Metal Restore for Windows-based servers

{: #using-bare-metal-restore-for-windows-based-devices}

When you use Bare Metal Restore for a Windows server, the restore process generally takes longer when compared to Linux-based devices. So, keep the following information in mind.

  • The estimated time to mount a Windows ISO can take 4 or more hours.
  • This extended time can affect your overall Recovery Time Objective (RTO). Make sure that your recovery plan minimizes disruption.

If the estimated wait time of 4 or more hours does not align with your recovery needs, you can manually mount the R1Soft ISO. Then, you can proceed with the restore without waiting for manual intervention.

To help reduce the time that it takes to recover your Windows server, use the following steps to manually mount the R1Soft ISO.

  1. Refer to the manual ISO mounting instructions.
  2. Download the R1Soft Live ISO from R1Soft live ISO download{: external}.