View source for Source:Citrix XenServer Requirements and Configuration/en

<noinclude><div class="noprint"><languages />
<br />

=={{anchor|overview}}Overview== 

</div></noinclude>This article describes the requirements and configuration steps for SEP sesam integration with Citrix XenServer. Note that the procedures introduced in this article are the configuration steps required to set up Citrix XenServer SEP sesam integration. For details on Citrix XenServer integration key features and backup configuration, see [[Citrix_XenServer_Backup|Citrix XenServer Backup]].

=={{anchor|requirements}}Requirements== 
* Check the [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS and Database Support Matrix]] for the list of supported Citrix XenServer versions.
* SEP sesam Server v. 4.4.3 ''Beefalo'' or higher. Citrix XenServer backup client is already included in all SEP sesam packages.
* Check [[Special:MyLanguage/SEP_sesam_Requirements#hardware|Hardware requirements]] for [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]], [[Special:MyLanguage/SEP_sesam_Glossary#SEP_sesam_Server|SEP sesam Server]] or [[Special:MyLanguage/SEP_sesam_Glossary#RDS|RDS]]. 
*Each XenServer must have a dedicated '''management interface'''.
*In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.
*Ensure that Network Block Device (NBD) is enabled on your Citrix XenServers. The NBD protocol is used for publishing block devices over TCP and is required for transporting CBT backups. For details, see the section [[#NBD|Configuring NBD on network interfaces for CBT]].
{{note| The backup traffic always goes over the management interface of the XenServer. Make sure you get good network performance, for example 2x 10 Gbit network interfaces as bond on both the XenServer and the backup server.}}

=== {{anchor|data_mover}}SEP sesam data mover for Citrix XenServer (SDM-CX)===
{{Source:SEP_sesam_DataMover/Data_mover_Citrix_XenServer}}

== {{anchor|configuration}}Configuring XenServer as a SEP sesam Client ==

To protect your virtual machines, you must configure your XenServer as a SEP sesam Client. Ensure that the [[#requirements|prerequisites]] are met before you begin the configuration. The options for configuring the XenServer may differ slightly depending on your SEP sesam version.
<ol><li>From '''Main Selection''' -> '''Components''' -> '''Clients''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</li>
<li>In the ''New Client'' window, enter the '''management interface DNS name of the pool master'''.  If you fail to enter the correct DNS name of the pool master, browsing XenServer environment will not work.</li>
<li>Under ''Platform'' drop-down list, select '''UNIX'''.</li>
<li>Under ''Operating system'' drop-down list, select '''Citrix XenServer'''.</li>
<li>The only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</li>
[[image:Add_client_XenServer_Apollon.jpg|730px|link=]]
<br clear=all>
<li>Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</li>
<li>Select a '''Data mover'''. The data mover must be the hostname of the SEP sesam Server or RDS. For details on requirements, see the above section [[#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</li>
[[image:Add_client-account_XenServer_Apollon.jpg|730px|link=]]
<br clear=all>
<li>Click '''OK''' to add the new client.</li></ol>

=== {{anchor|https}}Selecting ''https'' instead of ''http'' connection === 

SEP sesam uses ''http'' protocol as the default connection to ensure better performance when transferring data from XenServer to SEP sesam Server. Backups over ''https'' can cause up to 98% CPU load on XenServer. 

However, you can change the protocol to the secure ''https'' (secure with SSL) connection by specifying the ''https'' protocol under '''Backup task''' -> '''Properties''' -> '''Options''' tab -> '''Backup options''' as follows:

  -a http=https

==={{anchor|NBD}}Configuring NBD on network interfaces for CBT=== 

As of v. [[Special:MyLanguage/SEP sesam Release Versions|4.4.3.84 SP3]], SEP sesam no longer automatically enables Network Block Device (NBD) on all available network interfaces. NBD is required for transporting [[Special:MyLanguage/SEP_sesam_Glossary#CBT|CBT]] backups.

To activate NBD on all network interfaces, connect to the Poolmaster via ''SSH'' and execute the following command:
 for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-add uuid=$uuid param-name=purpose param-key=nbd ; done

This configuration may cause problems if there are networks the SEP sesam data mover cannot reach. Examples of such constellations are storage networks or a DMZ. In this case, the further configuration might be needed by using the following commands:

*to get a list of available interfaces
 xe network-list
*to get the network properties
 xe network-param-list uuid=<network-uuid>
*to enable NBD for a specific interface
 xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd
*to disable NBD for a specific interface
 xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd
*to deactivate NBD for all interfaces
 for uuid in $(xe network-list | grep uuid | cut -d":" -f 2); do xe network-param-remove uuid=$uuid param-name=purpose param-key=nbd ; done


For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html Citrix Hypervisor Documentation].

<noinclude>{{Copyright}}</noinclude>