Archive:Topology 4.4

From SEPsesam
Revision as of 16:34, 11 December 2017 by Sta (talk | contribs) (Updated as proposed by KAD.)
<<<Back
Components
User Manual
Next>>>
Clients


Topology

Topology represents the SEP sesam backup environment including the hardware, computers, backup devices, etc.

All interconnected computers – SEP sesam clients and SEP sesam Servers – can be logically grouped into locations and sub-locations. You can use locations to group your clients according to their OS, data type, different geographical location, etc.

The menu item Topology shows all SEP sesam locations, clients, loaders and drives known to the Master Server as well as the media within the devices. By clicking the symbols they can be expanded into the subordinate structures via a function tree. Each client is assigned to a location and each loader and drive to a client. By marking (clicking on one of the tree components and clicking the switch properties), the user opens the entry screen for the components.

Such grouping enables large organizations at different locations to be managed and represented as a group with separate, centrally-managed units (using a tree-like structure). Locations can be hierarchically organized - multiple sub-locations can be summarized under one Location. In our example, we will create a new location HOME.

A Master Sesam at the highest level presents all currently accessible 'regular' SEP sesam computers. With a mouse click their individual data can be viewed.

A 'regular' SEP sesam server shows one node only, namely itself.

Topology overview 4.4.png


To create a new location independent of another location, start at Topology and click the button New Location.

A client is always assigned to and created within a location.

Location Properties

Locations are defined as a group of clients and/or further sub-locations. This should help to organize larger networks so that computers in a building, an external office etc. can be managed and represented in separate units.

New locations can be configured from a SEP sesam server or from an existing location (sub-location). SEP sesam sets up a tree-structure for all locations (e.g., USA-Colorado-Boulder-SEP Software) offering greater visibility.

New location.png


Name
Name of the location
in
Superordinated location (not editable)
Description
More exact description of the location
Contact
Contact person at this location
Note
Additional information

Client Properties

Clients are the computers in the network (including the SEP sesam Server) that you want to backup and restore.

The following screenshot shows the input fields and functions of clients.

Information sign.png Note
The client properties are slightly different if the client is already added and configured and you edit its properties, or if you are configuring a new client. The Platform and additional tabs for entering access options are only available when configuring a new client.
Topology client.png


Name
Enter the name of the client – this has to be the network host name of the computer. The name has to be resolvable either by DNS or hosts file.
Location
Predefined location. A client always has to be assigned to a location.
Platform
Select the relevant platform of the client: Windows, UNIX, VMS or NETWARE. Depending on the platform, tabs for special access parameters are displayed. The Platform option is only available when configuring a new client.
Access Mode
Select the access mode for the server-client communication.
  • CTRL: It is the default setting.
  • SMSSH: SEP sesam SSH-based control communication. See also FAQ.
  • PROXY: Use this option if there is no direct remote access to this backup client. The data transfer is executed via vendor specific protocols, the client is accessed via the mandatory DataMover. The following protocols are supported: vSphere (vCenter Server), Citrix Xen Server, NetApp and Novell SMS for NetWare 5.1/6.0/6.5.
  • SSH: The communication method 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.
Last Sesam Message
The most recent system status message for the existing client.
Notes
Optional comment by the user.
Interfaces
Only edit this field if the client is the SEP sesam Server or a Remote Device Server (RDS). If there is an additional network for backups, 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 back to the SEP sesam Server will fail. The network protocols for the data transfer can be set by using the common prefixes ftp://server (default), http://server:11000 or https://server:11443. In the backup tasks the defined interfaces may be chosen for the data transfer.
Note If several interfaces are enter, separate them with a return or a blank.
Sesam Version
This field shows the SBC (SEP sesam Backup Client) version of the installation.
Locked for backups
Option is used only in special cases, when you want to exclude a client from backup for technical or other reasons. Checking this option will deactivate your client from all scheduled backups until this option is set.
Note: If this switch is set the client can no longer be backed up until the setting is removed.
Client is virtual machine
It should only be selected if you are adding a virtual machine.

Firewalls

Topology client options.png


By default SEP sesam uses ports that are assigned randomly by the operating system for its data connections. If clients that are behind a firewall are to be saved these ports can be defined.

Access Options
The default communication port on the backup client is 11301. If a port other than 11301 is used, it must be configured in the client's sm. ini file. In this field, enter the port over which the client is reachable (e.g., -p 17301).
STPD Options
The STPD options are used to define the backports from the clients to the SEP sesam Server, e.g. 11003-11006. These ports are then used to carry data during backups and restores. For each backup that runs parralel 2 ports of a client are needed.
Listen Port
The default STPD-port for Remote Device Servers (incl. SEP sesam Server) is 11001.
Note: For more information about firewalls please check the Administrator Manual.
Wake on LAN
For more information see the How To.
VM Parameter
In future versions, this values will be used to define the affiliation of a backup client to a VM in a virtual environment.

Additional Properties

Information sign.png Note
A third tab is available for the following backup types: Microfocus Open Enterprise Server, VMware, Citrix XEN, MySQL, PostgreSQL, NetApp, REV.

The following example shows the options for the OES-Netware client. If you are trying to back up an OES-NetWare or a OES-Linux client, the SEP sesam data mover connects to the TSA provided by Novell. To communicate with the various TSA's you need the following information.

Topology NetWare Access.png


Account
User name authorized for communicating with the TSA's.
NetWare Password
NetWare user's password, that is communication with the TSA's.
Repeat Password
Enter the password again to make sure it is correct.
Data Mover
The data mover is the host where the SEP sesam Novell client with the normal base software patches is installed. SEP sesam Novell client is needed to start the communication between the SEP sesam Server and the running TSA. SEP sesam Novell client can be installed on any Linux machine running Novell Storage Management Services (SMS). The only requirement is that either the SEP sesam Client or the SEP sesam Server software is installed correctly. The resolved DNS SEP sesam Client or SEP sesam Server is then entered as the data mover. If special backup methods are used, the settings must be entered in the tabs within the masks and must be visible to the SysAdm.