Source:Hyper-V Configuration

From SEPsesam
Revision as of 12:12, 13 January 2020 by Dho (talk | contribs)
Other languages:

Template:Copyright SEP AG en

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Grolar/4.4.3 Beefalo. For previous documentation version(s), check Hyper-V archive.


Overview

This article describes prerequisites and configuration requirements for SEP sesam integration with Hyper-V. Note that the procedures introduced in this article are only the required configuration steps. For details on backup configuration, see Hyper-V Backup.

Prerequisites

Configuring a Hyper-V standalone server or cluster as a SEP sesam client

To protect your Hyper-V virtual machines, you must configure the Hyper-V server (for Hyper-V standalone server) or Hyper-V resource (not the physical Hyper-V nodes for Hyper-V cluster) as a SEP sesam client.

  1. From Main Selection -> Components -> Topology, select your location and click the New client button. The New client window opens.
  2. In the New client window, configure the following options:
    • Enter the Client name.
    • Select Windows from the Platform drop-down list and the relevant Windows version under Operating system.
    • Choose the Access mode for the SEP sesam server-client communication.
    • From the VM server type drop-down list, select Hyper-V-Server (for Hyper-V standalone server) or Hyper-V-Cluster (for Hyper-V cluster).
  3. Hyper-v-client.png

  4. Click OK to add the new client.

Automatically installing SEP sesam Client on all Hyper-V cluster nodes (Windows only)

Automatic installation of the SEP sesam client on all Hyper-V cluster nodes is available for Windows SEP sesam Server only. If you are using a Linux SEP sesam Server, you have to manually install the SEP sesam clients on the Hyper-V nodes.

Information sign.png Note
If you have installed SEP sesam Client version 4.4.3 Tigon V2 (4.4.3.48) on Windows cluster nodes, you should currently not use it due to a known issue with missing hyperv_import.dll. Hyper-V restore – import will fail if only the SEP sesam Windows Client package 4.4.3 Tigon V2 is installed on the Hyper-V standalone server or on Hyper-V cluster nodes. You should upgrade the SEP sesam Server and Client to the latest version during the regular upgrade process. For details on this issue, see 4.4.3 Tigon V2 (4.4.3.48).
  1. Copy the client installation package sesam-cli-4.4.3.XX-windows.x64.exe to the <SEPsesam>\var\work\packages folder on the SEP sesam Server.
  2. Open the Command Prompt in your Windows SEP sesam Server as an administrator: Type cmd into search, right-click the displayed Command Prompt option and select Run as administrator.
  3. Once the Administrator: Command Prompt window is opened, use the following command to install the SEP sesam client onto the Hyper-V cores. Note that the inserted [domain\]user must be a domain administrator with access to all Hyper-V nodes.
  4. sm_config_client -I cli -c <clientname> -u <[domain\]user> -p <password> Example cd "C:\Program Files\SEPsesam\bin\sesam" sm_config_client -I cli -c HyperVresource -u SEP\mm -p supersecret

The SEP sesam Client is installed on each Hyper-V core. If the Hyper-V cluster has four Hyper-V cores, the SEP sesam Client will be installed on all four Hyper-V cores. The Hyper-V nodes will be added to the same location as your Hyper-V resource as additional SEP sesam Clients with the state locked for backups (no licence required). To have all your data protected, do not delete the clients.

Once your Hyper-V standalone server or cluster is added as a SEP sesam client, create backup tasks for each VM, as described in Hyper-V Backup.

See also

Hyper-V BackupHyper-V Restore BeefaloHyper-V Restore Grolar