Description

This article describes how to deploy a new "Snapshot Preview" Cloud Server from a Replicated Snapshot. Instructions for doing this on a Local Snapshot are at How to Create a "Snapshot Preview" Cloud Server from a Successful Historical Snapshot

For more information on Replicated Snapshots, see Introduction to Cloud Server Snapshots

Prerequisites:

  1. User must be Primary Administrator or have the Server role
  2. Snapshot Service is NORMAL in REPLICATED location
    1. NOT in either PENDING_MAINTENANCE or MAINTENANCE
  3. Snapshot must be a valid successful REPLICATED snapshot
  4. Each organization is limited to a maximum Number of Servers in SNAPSHOT_PREVIEW in a given location at a time
    1. So if Maximum has already been reached in replicated location, you will not be able to create a new Server from a Replicated Snapshot
  5. Primary NIC id must be valid
    1. Additional NIC ids must be valid 
  6. For each NIC associated with the Server, you must provide a NIC/VLAN pairing:
    1. NIC Id is valid and in the snapshot
    2. A corresponding VLAN Id in the Replicated data center must be provided and:
      1. All VLAN Ids must belong to the same Network Domain owned by the Organization in the Replicated Location
      2. The same Replication Location VLAN Id cannot be used for more than one NIC
      3. For all NIC's, If IPv4 address is provided:
        1. NIC Private IPv4 cannot be exclusively reserved on its corresponding VLAN in the Replicated Location
        2. NIC Private IPv4 cannot be system reserved on its corresponding VLAN in the Replicated Location
      4. If IPv4 not provided for a NIC, the system will try and use the historical Private IPv4 address from the replicated snapshot or that NIC
        1. snapshot address cannot be exclusively reserved on the corresponding VLAN in the Replicated Location
        2. snapshot address cannot be system reserved on its corresponding VLAN in the Replicated Location
        3. If snapshot address can't be used and there are no available IP addresses on the VLAN in the Replicated Location, the request will fail
  7. The Target Cluster on which you are creating the Snapshot Preview Server must support the Replicated Snapshot Configuration:
    1. Number of CPU (Min/Max)
    2. Amount of RAM (Min/Max)
    3. Size of the disk (Min/Max)
    4. Total Storage Size (Max only)
    5. Total Snapshot Server Size (Max only)
  8. If Target Cluster input is not provided and there is more than one cluster in the replicated location, the server will be assigned to the Default Cluster
  9. If Snapshot has Advanced Virtualization Settings:
    1. If the Source Image has Nested Hardware Virtualization set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
    2. If the Source Image has CPU Latency Sensitivity set to HIGH, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
    3. If Source Image has Numa Autosize numaAutosize set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
    4. If Source Image has Enable Host Info to VM Tools set to true, then the Target Cluster must be enabled to support Advanced Virtualization Settings. See How do I Identify Hardware Specifications and Capabilities Available in a Data Center Location
      1. For more information on Advanced Virtualization Settings, see Introduction to Advanced Virtualization Settings

Content / Solution:

  1. From the Home page, select the Data Center where the Server from which you want to deploy a new Snapshot Preview Server from a Replicated Snapshot is located:


  2. The Data Center Dashboard will be displayed. Select the Network Domain where the Server is located:


  3. The Network Domain dashboard will be displayed. Click on the Replication Enabled Server:


  4. The Server dashboard will be displayed. Click on the Snapshots tab, then click on the Replicated tab, to display the Replicated Snapshots:


  5. Click on the gear menu button, and select Deploy Server from Replicated Snapshot from the drop-down menu:


  6. The Deploy Server from Replicated Snapshot dialog will be displayed:

    Note: The Data Center will be automatically populated and cannot be changed. You will also see the Snapshot ID of the Replicated Snapshot from which you are going to deploy a new Server and the Name of the Parent Server, from which the Replicated Snapshot was taken. 

  7. Select the Network Domain on to which the Replicated Snapshot will be deployed from the drop-down menu:

    Note: If the Snapshot is currently on Archived storage, the process to create a Snapshot Preview Server may be a long-running process!

  8. The Deploy Server from Replicated Snapshot dialog will expand. Fill out the form with the desired information:

    • Data Center - Will be auto-populated

    • Network Domain - Select the desired Network Domain
    • Server Name - The Server Name is a descriptive name that will appear with the Cloud Server when viewing Servers in the administrative interface. It has no impact on the Server's functionality, machine name, or host name. Therefore, Server Names are not required to be unique.

    • Choose your Network target(s) for the Server deployment:

    • VLAN(s) - Select the VLAN(s) with which the Server should be associated.

      • Note: The Network Domain where the Replicated Snapshot Server will be deployed must have the same amount (or greater)  of VLANs as the Source Network Domain. 

    • NIC ID - Identifies the Primary and any subsequent NICs
    • IPv4 Address - Enter the desired IPv4 address or leave it blank to have an IP address assigned automatically by the system. When specifying an IP address, the proposed IP address cannot be in use on another cloud resource, Exclusively Reserved or fall into the "reserved" ranges on the VLAN. For more details, see Introduction to IP Addressing in MCP 2.0

    • Connect NIC(s) on Deploy - Select if you want the NIC(s) to be connected or not. For more information on NIC Connectivity, see Introduction to Cloud Server NICs in MCP 2.0

      • Note: Because the Snapshot Preview server is from a historical snapshot of the original server and is provisioned to the same VLANs as the original server, there is a high likelihood of IP conflict if the original server is runningWe recommend creating Snapshot Preview Servers with the NICs in a disconnected state and connecting them only after you are sure it will not cause a problem.
    • Preserver MAC Address(es) - - By default, the NIC MAC Addresses of the new "Snapshot Preview" server will differ from those that were assigned to the server from which the Historical Snapshot was taken. If either your Guest OS or your application is sensitive to the MAC address settings, select this option to keep the MAC addresses the same as the server from which Snapshot originated. However, by preserving MAC addresses, you may create a MAC address conflict. For more details, see:

    • Cluster - If the Data Center is enabled with User-Manageable Clusters, you can select the desired Cluster from the drop-down menu. Otherwise, the default Cluster will be utilized.

    • Add/Update Tag to List - Optionally add Tags to the Server. For more information on tagging, see Introduction to Tagging, Tag Keys and Tag Values

  9. Once complete, click the Review button:


  10. Review the Replicated Snapshot Server's Specifications. If you need to make any changes, you can press the Back button. Otherwise, click Deploy:


  11. The system will display a message indicating that the operation is in progress:


  12. You will have to navigate to the Replication Location Data Center to view the progress of the deployment. See Navigating the Network Domain Dashboard in a MCP 2.0 Data Center. Once you have navigated to the Replication Location Data Center, Click on the Servers tab to see the Replicated Server's deployment progress:


  13. When the Replicated Snapshot Server has been deployed, the system will display a success message:


  14. At this point, the Replicated Snapshot Server is in Preview Mode:

    Note: You can choose to migrate it to a full server or wait two hours and it will be automatically migrated to a full (normal) Cloud Server. For more information about Preview Servers, see Introduction to Cloud Server Snapshots

    Migrate to Normal Server

    For instructions on how to Migrate the Snapshot Preview Server to a normal Server, See How to Migrate a "Snapshot Preview" Server to a Normal Cloud Server

    Specific configurations may need additional configuration changes to work after creation from a Snapshot

     Specific configurations may need additional configuration changes to work after creation from a Snapshot. Specifically:

    Snapshot Preview Servers from Archived Snapshots

    If you request a Snapshot Preview Server from a Snapshot which is on Archival Storage, and there is not enough space on the local storage to bring the Snapshot back, the Snapshot Preview Server will fail, and the failure will be noted in the Administrator Log. See How to View an Administrator Logs Report