4 4 3 Beefalo:Step 2: Clients
Step 2: Clients
You can configure a new client in the Main selection -> Components -> Topology -> New client.
Depending on the operating system of a client, either Windows, UNIX, VMS or NetWare platform is selected. You can select a location to which you want to add a new client from the drop-down list of configured locations.
The name of the client to be backed up (target client) is the hostname of this computer on a given network. The backup data may reside on the server (typical); on the client (Remote Device) either on second disk drive or tape; or the data may be sent over a LAN or WAN to a storage area network (SAN).
If there is a name server (DNS) in the network, SEP sesam automatically selects the TCP/IP address. Otherwise it must be entered in the etc/hosts file.
Operating system: Select the operating system version of the computer you are adding as a client.
Access mode: Select the relevant access method for the server-client communication.
- CTRL: Default access mode until version 220.127.116.11 Tigon V2.
- SMSSH: Default access mode as of version 18.104.22.168 Grolar. SEP sesam SSH-based control communication. SSL libraries include libmicrohttpd, libcurl, and libopenssl. See also FAQ: access permissions.
- PROXY: Access mode for a hypervisor or other systems without installed backup client. The data transfer is executed via vendor specific protocols; the client is accessed via the mandatory data mover. For details, see What is a SEP sesam data mover. The following protocols are supported: vSphere (vCenter Server), Citrix Xen Server, NetApp, NDMP and Novell SMS for NetWare 5.1/6.0/6.5.
- VIRTUAL: (introduced in v. 4.4.3 Beefalo) Access mode for a virtual machine (VM) without installed backup client where there is no direct remote access to this VM. Note that the VIRTUAL access mode is similar to PROXY, but is specifically intended to manage VMs as clients by allowing to configure ACLs for VMs. This means that administrator can allow explicit restore access to a virtual client while preventing access to the hypervisor server. For details on how to configure permissions (ACLs) for clients, see Using Access Control Lists.
- SSH: The communication mode SSH is based on a key-pair operation of the SSH implementation of the used operation system.
- RSH: Remote Shell; it is a historic old option and is rarely used.
VM server type: If the client should be managed as a VM server, select the relevant type. This enables, for example, browsing the virtual environment when creating backup tasks.
Notes: Additional comment.
|Edit this field only if a client is a SEP sesam Server or Remote Device Server (RDS).|
If there is an additional network for backups available, the resolvable and changed DNS-name of a second network card of the SEP sesam Server can be entered into a new line. If several network cards are available, they need to be known to the DNS otherwise the connection to SEP sesam Server will fail.
The network protocols for data transfer can be set by using the common prefixes ftp:// (default), http:// or https://. For each protocol one interface has to be added in the interfaces box separated by single spaces. One interface for the HTTP protocol http://<hostname>:11000 and one interface for the HTTPS protocol https://<hostname>:11088.
VM host and VM name: You have to specify a VM host and name if your client is a virtual machine.
There are two additional client-related options:
- Client is a virtual machine: Selecting this option allows you to edit the VM host (name of the VM Server) and the VM name. These values are used to identify the backup client as a VM in a virtual environment.
- Do not update this client (≥ 4.4.3. Beefalo V2): Checking this option allows you to exclude a particular client from being updated. This setting applies in general for all possible updates.
- Execution off: If a client needs to be excluded from the backup for technical or other reasons, you can deactivate it by checking this option.
|If this option is set, the client will not be backed up until it is unlocked again even if it is scheduled for backup.|
By default, SEP sesam uses random ports that are assigned by the operating system for its data connections. However, if you want to back up a client which is behind a firewall, you must manually define the ports. The available options depend on the client type. For details, see Topology: Firewalls.
Tab OS Access
When configuring a new client, you have to enter the credentials as an administrator to access the respective systems. You have to use DOMAIN\USER format for domain accounts or HOST\USER for local accounts.
Once all the options are set, click Create or OK. Clicking Create will leave the dialog window open, allowing you to quickly configure several clients one after another.
Then a new dialog box appears asking whether you want to create a new backup task for this client. Click Yes to create a backup task or No if you intend to configure your backup later. For details, see Standard Backup Procedure.
Your new client is displayed in the Topology content pane.
Additional tabs in the client properties
In the client properties two additional tabs are available for specifying additional settings. You have to double-click a relevant client to open its properties and specify additional settings.
Under the Permissions tab, you can add the relevant permissions for your client. For details, see Using Access Control Lists.
If you are configuring clients that must be backed up by special task types, additional settings must be specified. A fifth tab is available for the following task types: Micro Focus Open Enterprise Server (formerly Novell OES), VMware, Citrix XEN, MySQL, PostgreSQL, NetApp, RHV. For example, for Micro Focus OES or NetWare server backup you have to specify the login data for the eDirectory and select the appropriate data mover. For Micro Focus, this is a SEP sesam Micro Focus (formerly Novell) Client which is installed on Linux computer with Micro Focus Storage Management Services (SMS).
For more information on specific task type, see the respective wiki articles under Extensions.