Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

There are two options for restoration:

1. Restore existing VPS

Execute the following command on a slave node:

Code Block
/scripts/ftp-restore

Then just follow instruction prompted.


2. Restore terminated/non-existing VPS

• KVM

Expand
  1. Create new VM from SolusVM with the same resource or larger than the terminated one.
  2. Each VM's will have 3 backup files in the backup server:


    # 
    Backup file: VSERVERID-kvm-kvmID-1.bz
    # VM config file: kvmID.xml
    # LVM config file: config-VSERVERID.dat

  3. Rename the backup files with new vserverID & kvmID

    # newvserverID-kvm-newkvmID-1.bz
    # newkvmID.xml
    # config-newvserver ID.dat

    For example, consider 121 as new ververID & kvm131 as new kvmID

    # 121-kvm-kvm131-1.bz
    # kvm131.xml
    # config-121.dat

  4. Once renamed the files, edit the XML and config.dat files to update the new VM's kvmID and LVM path in it.
  5. Run the restoration script /scripts/ftp-restore on a slave node.

...

Expand
  1. Create a new VPS with the same resources or larger than terminated one.
  2. Connect to the backup server over SSH.
  3. Find the backup of VPS - its format name is ID-vz-VMID-1.tgz, for example 203-vz-108-1.tgz.
    Where ID - ID of VPS in SolusVM > Virtual Servers, VMID - VMID of VPS in SolusVM > Virtual Servers.
  4. Rename the backup - change ID and VMID according to these values of the created VPS in step 1.
  5. Connect to the slave node onver SSH.
  6. Restore VPS using the new ID with restoration script:

    Code Block
    languagebash
    # /scripts/ftp-restore



2. Restore existing VPS

Execute the following command on a slave node:

Code Block
/scripts/ftp-restore

Then just follow instruction prompted.