4 4 3:Citrix XenServer Requirements and Configuration: Difference between revisions

From SEPsesam
(Marked this version for translation)
(Marked this version for translation)
 
(8 intermediate revisions by 2 users not shown)
Line 6: Line 6:


<!--T:2-->
<!--T:2-->
{{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo V2'']]|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix XenServer archive]]}}</div></translate>
{{Navigation_previous|link=[[Special:MyLanguage/Citrix_XEN_Server|Citrix documentation]]}}</div></translate>
 


<translate>=={{anchor|overview}}Overview== <!--T:3--></translate>
<translate>=={{anchor|overview}}Overview== <!--T:3--></translate>
Line 15: Line 14:
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5-->
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:5-->
[[File:SEP_next.png|45px|link=4_4_3_Grolar:Citrix_XenServer_Backup]]</translate>
[[File:SEP_next.png|45px|link=Citrix_XenServer_Backup]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6-->
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:6-->
See also: [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</translate>
See also: [[Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Citrix_XenServer_Restore|Citrix XenServer Restore]] – [[Citrix Hypervisor Single File Restore|Citrix Hypervisor Single File Restore]]</translate>
|}
|}


Line 34: Line 33:
|}</div>
|}</div>
<translate><!--T:11-->
<translate><!--T:11-->
This article describes requirements and configuration steps for SEP sesam integration with Citrix XenServer. Note that the procedures introduced in this article are the required configuration steps to set up Citrix XenServer SEP sesam integration. For details on Citrix XenServer integration key features and backup configuration, see [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]].
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== <!--T:12--></translate>
=={{anchor|requirements}}Requirements== <!--T:12--></translate>
* <translate><!--T:13-->
* <translate><!--T:13-->
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.</translate>
Check the [[SEP_sesam_OS_and_Database_Support_Matrix#Citrix|SEP sesam OS and Database Support Matrix]] for the list of supported Citrix XenServer versions.</translate>
* <translate><!--T:14-->
* <translate><!--T:14-->
SEP sesam Server v. 4.4.3 or higher. Citrix XenServer backup client is already included in all SEP sesam packages.</translate>
SEP sesam Server v. 4.4.3 ''Beefalo'' or higher. Citrix XenServer backup client is already included in all SEP sesam packages.</translate>
* <translate><!--T:15-->
* <translate><!--T:15-->
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]].</translate>  
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]].</translate>  
Line 47: Line 46:
*<translate><!--T:17-->
*<translate><!--T:17-->
In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.</translate>
In a cluster configuration where more XenServers are organized in a pool, the '''pool master''' XenServer must be configured as a ''SEP sesam Client''.</translate>
*<translate><!--T:54--> 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 [[Special:MyLanguage/4 4 3:Citrix_XenServer_Requirements_and_Configuration#NBD|Configuring NBD on network interfaces for CBT]].</translate>
{{<translate><!--T:18-->
{{<translate><!--T:18-->
note</translate>| <translate><!--T:19-->
note</translate>| <translate><!--T:19-->
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 a bond on the XenServer as well as on the backup server.</translate>}}
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.</translate>}}


<translate>=== {{anchor|data_mover}}SEP sesam data mover for Citrix XenServer (SDM-CX)=== <!--T:20-->
<translate><!--T:20-->
{{:Template:Data mover Citrix XenServer/en}}
=== {{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 == <!--T:21-->
<!--T:21-->
To protect your virtual machines, you must configure your XenServer as a SEP sesam Client. Make sure that the [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#requirements|prerequisites]] are met before starting with configuration. The options for configuring XenServer may differ slightly depending on your SEP sesam version.</translate>
== {{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 [[Special:MyLanguage/4 4 3:Citrix_XenServer_Requirements_and_Configuration#requirements|prerequisites]] are met before you begin the configuration. The options for configuring the XenServer may differ slightly depending on your SEP sesam version.</translate>
<ol><li><translate><!--T:22-->
<ol><li><translate><!--T:22-->
From '''Main Selection''' -> '''Components''' -> '''Topology''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</translate></li>
From '''Main Selection''' -> '''Components''' -> '''Topology''', select the relevant ''location'' and click the '''New Client''' button. The ''New Client'' window opens.</translate></li>
Line 62: Line 64:
<li><translate>
<li><translate>
<!--T:39-->
<!--T:39-->
Under ''Platform'' drop-down list, select the '''UNIX'''.</translate></li>
Under ''Platform'' drop-down list, select '''UNIX'''.</translate></li>
<li><translate><!--T:24-->
<li><translate><!--T:24-->
Under ''Operating system'' drop-down list, select the '''Citrix XenServer'''.</translate></li>
Under ''Operating system'' drop-down list, select '''Citrix XenServer'''.</translate></li>
<li><translate><!--T:25-->
<li><translate><!--T:25-->
As of SEP sesam v. 4.4.3, the only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</translate></li>
The only supported ''access mode'' is '''PROXY''', which is set by default when the Citrix XenServer operating system is selected.</translate></li>
{{<translate><!--T:26-->
<!--{{<translate><!--T:26-->
note</translate>|<translate><!--T:27-->
note</translate>|<translate><!--T:27-->
If you are using SEP sesam version ≥ 4.4.3, make sure that the '''PROXY''' access mode is selected. If the access mode ''CTRL'' is used, an error occurs when SEP sesam Server checks the connection to the SEP sesam XenServer client.</translate>}}
If you are using SEP sesam version ≥ 4.4.3, make sure that the '''PROXY''' access mode is selected. If access mode ''CTRL'' is used, an error occurs when SEP sesam Server checks the connection to the SEP sesam XenServer client.</translate>}}-->
<translate><!--T:28-->
<translate><!--T:28-->
[[image:Add_client_XenServer_Beefalo_V2.jpg|730px|link=]]</translate>
[[image:Add_client_XenServer_Beefalo_V2.jpg|730px|link=]]</translate>
Line 76: Line 78:
Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</translate></li>
Click the tab '''Citrix XenServer''' and enter ''root/admin'' credentials for XenServer.</translate></li>
<li><translate><!--T:30-->
<li><translate><!--T:30-->
Select a '''Data mover'''. The data mover must be the host name of the SEP sesam Server or RDS. For details on requirements, see the above section [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</translate></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 [[Special:MyLanguage/4_4_3:Citrix_XenServer_Requirements_and_Configuration#data_mover|SEP sesam data mover for Citrix XenServer (SDM-CX)]].</translate></li>
<translate><!--T:31-->
<translate><!--T:31-->
[[image:Add_client-account_XenServer_Beefalo_V2.jpg|730px|link=]]</translate>
[[image:Add_client-account_XenServer_Beefalo_V2.jpg|730px|link=]]</translate>
Line 86: Line 88:


<!--T:34-->
<!--T:34-->
SEP sesam uses the ''http'' protocol as a 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.  
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.  


<!--T:35-->
<!--T:35-->
Line 93: Line 95:
   -a http=https
   -a http=https


<translate>==={{anchor|NBD}} Configuring NBD on network interfaces for CBT=== <!--T:40-->


<translate>==={{anchor|NBD}} Configure NBD on network interfaces for CBT=== <!--T:40-->
<!--T:47-->
Starting from Version 4.4.3.84SP3, SEP sesam will no longer automatically enable NBD on all available network interfaces. NBD is required for the transport of CBT backups.
As of v. [[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.


<!--T:41-->
<!--T:41-->
To activate NBD on all network interfaces, connect to the Poolmaster via SSH and execute the following command
To activate NBD on all network interfaces, connect to the Poolmaster via ''SSH'' and execute the following command:</translate>
  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
  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


<!--T:42-->
<translate><!--T:42-->
This configuration may cause problems, when there are networks the SEP sesam Datamover cannot reach. Examples for such constellations are storage networks or a DMZ.
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:</translate>
 
<!--T:43-->
In that case further confuration is needed.
 
<!--T:44-->
The following commands can be used to accomplish this:


<!--T:45-->
<ul><li><translate><!--T:48--> to get a list of available interfaces</translate></li>
* to get a list of available interfaces
  xe network-list
  xe network-list
* to get the properties of a network
<li><translate><!--T:49--> to get the network properties</translate></li>
  xe network-param-list uuid=<network-uuid>
  xe network-param-list uuid=<network-uuid>
* to enable NBD for a specific interface
<li><translate><!--T:50--> to enable NBD for a specific interface</translate></li>
  xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd
  xe network-param-add uuid=<network-uuid> param-name=purpose param-key=nbd
* to disable NBD for a specific interface
<li><translate><!--T:51--> to disable NBD for a specific interface</translate></li>
  xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd
  xe network-param-remove uuid=<network-uuid> param-name=purpose param-key=nbd
* to deactivate NBD for all interfaces
<li><translate><!--T:52--> to deactivate NBD for all interfaces</translate></li>
  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 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
</ul>


<!--T:46-->
<translate><!--T:53-->
For further information consult the [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html| Citrix Hypervisor Documentation]
For more information, see [https://docs.citrix.com/en-us/citrix-hypervisor/networking/manage.html Citrix Hypervisor Documentation].


</translate>
<!--T:36-->
<translate>==Known issues== <!--T:36-->
==Known issues==
If you have problems with Citrix XenServer, check the [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].
If you have problems with Citrix XenServer, check the [[Special:MyLanguage/Troubleshooting_Guide#Citrix|Troubleshooting Guide]].


<!--T:37-->
<div class="noprint">
<div class="noprint">
=={{anchor|see also}}See also== <!--T:37-->
=={{anchor|see also}}See also==
[[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Special:MyLanguage/4_4_3_Grolar:Citrix_XenServer_Restore|Citrix XenServer Restore]]</div></translate>
[[Citrix_XenServer_Backup|Citrix XenServer Backup]] – [[Citrix_XenServer_Restore|Citrix XenServer Restore]] – [[Citrix Hypervisor Single File Restore|Citrix Hypervisor Single File Restore]]</div></translate>

Latest revision as of 12:29, 28 March 2023

Copyright © SEP AG 1999-2024. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

This is not the latest version of SEP sesam documentation and, as such, does not provide information on features introduced in the latest release. For more information on SEP sesam releases, see SEP sesam Release Versions. For the latest documentation, check Citrix documentation.

Overview

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.

Requirements

  • Check the 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 Hardware requirements for SEP sesam Client, SEP sesam Server or 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 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.

SEP sesam data mover for Citrix XenServer (SDM-CX)

A SEP sesam data mover (SDM-CX) is required to run a SEP sesam backup and restore in a Citrix XenServer environment. Normally nothing has to be done to make the SEP sesam Server itself work as a data mover without any customization. The only reason to change the data mover would be that the data stream received from the XenServer should not be processed by the SEP sesam Server but by an RDS. A data mover role for Citrix XenServer can be combined either with a SEP sesam Server, SEP sesam Remote Device Server or a SEP sesam Client. Any of these can serve as a SEP sesam data mover (SDM-CX) to transfer (send or receive) data between SEP sesam Server and Citrix XenServer. When Citrix XenServers are organized in pools, the SEP sesam data mover (SDM-CX) has to communicate directly with the pool master. When the backup starts, the pool master tells the SDM-CX on which Citrix XenServer the VM is located and forces a communication switch to the appropriate Citrix XenServer (mapping).

  • Any of the following SEP sesam components must be installed: SEP sesam Server, RDS or client.
  • A regular path backup has to work. For details on typical backup configuration, see Standard Backup Procedure.


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 prerequisites are met before you begin the configuration. The options for configuring the XenServer may differ slightly depending on your SEP sesam version.

  1. From Main Selection -> Components -> Topology, select the relevant location and click the New Client button. The New Client window opens.
  2. 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.
  3. Under Platform drop-down list, select UNIX.
  4. Under Operating system drop-down list, select Citrix XenServer.
  5. The only supported access mode is PROXY, which is set by default when the Citrix XenServer operating system is selected.

  6. Click the tab Citrix XenServer and enter root/admin credentials for XenServer.
  7. 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 SEP sesam data mover for Citrix XenServer (SDM-CX).

  8. Click OK to add the new client.

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

Configuring NBD on network interfaces for CBT

As of v. 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 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 Citrix Hypervisor Documentation.

Known issues

If you have problems with Citrix XenServer, check the Troubleshooting Guide.