Contents |
The Sesam backup environment including the hardware, computers, backup devices, etc is referred to as Topology .
These interconnected computers (clients and servers), which can be grouped into locations and sub-locations as well as the storage devices ( loaders, drives ), which are available for Sesam locally or attached to clients (Remote Device).
The menu item Topology shows all 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 related 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.
A Master Sesam at the highest level presents all currently accessible usual Sesam computers. With a mouse click their individual data can be viewed.
A 'usual' Sesam server shows one node only, namely itself.
To create a new location independent of another location, start at Topology and click the button New Location .
A client is always related to and created within a location.
Note The parameters of the server cannot be edited here.
Location is 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 Sesam server or from an existing location (sub-location). Sesam sets up a tree-structure for all locations(e.g. USA-Colorado-Boulder-SEP Software) offering greater visibility.
Clients are defined as computers in the network from which data are to be saved. The computer on which Sesam is installed is called the server .
If a client is not available for backups (e.g. because of a shutdown), the SysAdm can select the check box locked for backups and prevent unnecessary access (locked clients are marked with off under Topology). If an unavailable client is not locked, the SEPuler will continue to look for it to perform the scheduled backup.
Warning: Once selected locked for backups the client will no longer be backed up, even if on the event calendar. The SysAdm must remove the check to reestablish the backup schedule.
Note If several interfaces are entered, separate them with a Return or a Blank.
| Note: |
|
If the switch is set from this time forward the client can no longer be backed up, until the setting is removed. Even if the client is part of the pre-established backup schedule. |
Normally when initiating backups of clients Sesam uses the ports randomly provided by the operating system. However, this is not allowed if the client is located behind a firewall.
If there is a firewall in place a port range can be pre-determined by using the command sm_ctrlc for communication with the clients:
Access Options input -o port=firstport-lastport
Another method to connect through the firewall is to configure a Singleport connection ( -s ), where Sesam uses only one port (by default 11301).
Note: This must not be done for Remote Tape Servers.
The return ports from client to the Sesam server are placed in STPD Options , e.g. 11003-11005. The data can now be transferred over these ports. Each parallel backup requires two separate ports. For each additional parallel running backup from a client you will need to assign a further 2 ports, e.g. 11003-11007).
Listen Port
Note: Further information regarding Firewalls can be found in the Admin Handbook.
In the event you are trying to backup 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 will need the following information.
Our sales team would be happy to assist you!
Browse and discover videos by SEP.