You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Description

This article describes the method to conduct an "Out of Place" full system restore from a File System Backup Client. An "out of place" full system restore takes a previous backup from one Cloud Server (the "source") and restores the entire file system (including OS and registry settings) to a different Cloud Server (the "target"). Any files with matching names and paths on the target Cloud Server will be overwritten server with the version of the files from the source sever's backup at the requested backup date.

NOTE - An out of place restore is typically initiated when you are testing various restore points that are available, in order to verify the best restore point for your circumstance.

Prerequisites:

P1.   This guide assumes that the Backup service has been enabled on the Server, that the File System Backup Client has been installed on the Server and that at least one Backup exists. For details see

         Cloud Backup - Introduction  

P2.   Full System Restores should be approached with the utmost care. Files with matching names and paths on the target server will be overwritten with the version of the files from the requested backup of the         source Cloud Server at the identified backup date.

 

P3.   The source Cloud Server is the server from which you are initiating the restore and from which the backup data will be obtained. This source server must be in a stopped state at the time the backup is                 requested. In addition, it must be enabled with either the Advanced or Enterprise service plan (and have been enabled as such at the time of the requested backup). Full system restores are not available             with the Essentials plan.
P4.    The target Cloud Server must also be enabled with either the Advanced or Enterprise service plan. Full system restores are not available with the Essentials plan. 

         The target Cloud Sever also must already be deployed with a compatible Operating System, with the Backup service enabled and the same type of File System Backup Client installed ("Windows File                    Agent" or "Linux File Agent") and visible as "Active"

P5.    The target Cloud Server must have enough space to accept the full system restore being requested. Failure to have enough space available so may result in an incomplete system restore.

P6.    

  •  On Linux system, after Restore completion, the IP address will remain the same on the target server as we don’t overwrite the target server’s IP address. 
  • On Windows system, after you reboot, you will need to use the new console access in CaaS to re-IP.

 

 

Solution:

  1. Identify the Server whose previous backup you wish to use as the source for an "out of place" Full System Restore in the Cloud Administrative UI and access the Cloud Backups dialog as described in How to Access Cloud Backup Functions in the Admin UI  

  2. The system displays the Backup dialog. Identify the File System Backup Client. It will either be called "Windows File Agent" or "Linux File Agent" depending on the Operating System of the Server. Click the green Restore icon on the right hand side.
  3.  

    The system displays the "Out of Place" Restore screen. The appearance of this screen depends on the running state of the server.

     

    Note that for a running Server the "In Place Restore" option will be selected. If you wish to restore a Backup to the same Server see How to Initiate a Full System "In Place" Server Restore 

  4. Click the calendar icon to select the Backup date you wish to restore the Server to:
  5.  

    The system will display the set of Servers suitable as targets for the Backup to be restored to. 

     

    Important Note: Remember that after restoration is initiated, files with matching names and paths will be overwritten on the target server with the version of the files at the identified backup date.

     

    Select the target Server.

    NOTE: If there are more than 30 potential target servers, the call to gather the list of target servers may "time out". If this occurs, an error message may display. In ths case, please contact Support to initiate the restore.


  6. When you have selected the desired target server.

    Click "Submit".

  7. A confirmation will be displayed by the system repeating the date you have selected. Click "Submit" to confirm your choice (which begins the restoration process) or "Previous" to return to the date selection screen.
  8. The Admin UI will return to the Backup Details screen. The restoration is displayed as a running Job in the row for the File System Backup Client ("Windows File Agent" in the example below). When complete the Job status will return to "None"; indicating that there is no job in progress for the Backup Client. 

    Note that the Job will appear for the File System Backup Client on the source Server.

  9. After restoration is complete, we recommend connecting to the target Server to ensure that you have restored to the correct point in time   
  10.  
    • On Linux system, after Restore completion, the IP address will remain the same on the target server as we don’t overwrite the target server’s IP address. 
    • On Windows system, after you reboot, you will need to use the new console access in CaaS to re-IP..

Related Articles:

  • No labels