Servergraph 7.5
Use this pre-installation checklist to verify that you are prepared and that the server that you
plan to use for the evaluation meets the needed minimum requirements. Please note that this
checklist is ONLY for evaluation of 2 TSM instances and a limited selection of other server
types. Larger sites will require additional resources.
Review the requirements for the system that Servergraph will run on and for the systems with
which Servergraph will communicate. Please check off the box for each Servergraph
requirement, and then sign, date and attach the updated document to the related case
on the Rocket Support Portal (http://www.rocketsoftware.com/support).
VM Appliance Information:
Rocket Software - Servergraph VMware appliance
7.5 build
This VM appliance is built on CentOS 6.5, and is suitable for use with VMware ESXi 4 to
5.5.
The appliance uses about 4GB disk space when first installed, with a 50GB sparsely
provisioned disk.
One CPU and 4GB RAM is allocated; this should be fine to monitor a couple of TSM
instances as a proof of concept, but is generally low for normal Production use.
If there is no DHCP server available on the network to which you connect the appliance,
the boot scripts are unable to assign an address; you will have to set an address
manually (or enable DHCP on the network, and reboot).
The IP address is generally configured via DHCP, and is reported in the login banner
after a restart.
To set an IP address manually (if you have a network which is functional, but which does
not have a DHCP server)
o log in to the appliance console as root;
o then run system-config-network to assign a static address, netmask, default route
and DNS server.
Tony.Heskett@rocketsoftware.com
Steve.Wright@rocketsoftware.com
James.Healy@rocketsoftware.com
Use the worksheets below to setup communication between Servergraph and your TSM server.
For fresh installations, please fill in the connection details tables.
For upgrades or migrations, you only need to include any modified or new
configurations. Otherwise, you can leave these tables blank.
Servergraph host port requirements
Backup Applications
TSM Servers
You have met the following requirements for your TSM server:
SSHD is running on all TSM servers. The Servergraph Sales Engineer will establish
a new passwordless DSA key on the Servergraph machine that will be used for
communication with the TSM servers; but WILL NOT set-up the SSH program on the
TSM servers.
'set accounting on' is enabled and you know location of the TSM accounting log and
have a user account with read access that the Servergraph sales engineer can use
to transfer the log.
There must be an existing non-ROOT user account on each TSM server used for
data collection (SSH, FTP).
You know the DNS name of TSM servers that are being monitored.
If you want Servergraph to report on retrieve and restore messages from the Activity
Log, you must enable the REPORTRETRIEVE option in the DSMSERV.OPT file. The
default for this option is NO.
Enter the server name, library name, and number of slots for each library that will communicate
with Servergraph.
Server name Library name Slot count
(Optional) If you are using ACSLS, please fill out the following information.
SSHD must be installed and running on the ACSLS server. Your Servergraph sales engineer
sets up passwordless SSH to run ACSLS commands remotely and send data back to
Servergraph.
Server name ACSLS server DNS of ACSLS SSH user
name
NetBackup
This section can be deleted if you do not have NetBackup in your environment.
Connection is made using SSH directly to the NetBackup server. The Cygwin and related SSH
package must be installed on the NetBackup server. The SSH password does not need to be
provided to Rocket Software, but will have to be available during the software installation and
configuration.
Note: You can also use Telnet and FTP connections.
Server IP SSH SSH NETBACKUP_ADMINCMD NETBACKUP_VOLMGR
name address User Password value value
or
hostname
NetWorker
This section can be deleted if you do not have NetWorker in your environment.
Connection is made using SSH directly to the NetWorker server. The Cygwin and related SSH
package must be installed on the NetWorker server. The SSH password does not need to be
provided to Rocket Software, but will have to be available during the software installation and
configuration.
Avamar Appliances
This section can be deleted if you do not have Avamar in your environment.
Connection is made using a direct connection to Avamars built-in Postgres DB. The default
values are defined in the table below.
The MCDB account password does not need to be provided to Rocket Software, but will have to
be available during the software installation and configuration.
CommVault Simpana
This section can be deleted if you do not have CommVault in your environment.
Connection is made using a direct connection to CommVaults built-in Microsoft SQL DB. The
default values are defined in the table below.
The MS SQL account password does not need to be provided to Rocket Software, but will have
to be available during the software installation and configuration.
Veeam Appliances
This section can be deleted if you do not have Veeam in your environment.
Connection is made using a direct connection to Veeams built-in Microsoft SQL database. The
default values are defined in the table below.
The MS SQL account password does not need to be provided to Rocket Software, but will have
to be available during the software installation and configuration.
Server name IP address or MS SQL Port MS SQL User MS SQL
hostname Password
1433
Rocket iCluster
This section can be deleted if you do not have iCluster in your environment.
Connection is made using a direct Telnet session to the iSeries environment.
The account password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration.
IBM BRMS
This section can be deleted if you do not have BRMS in your environment.
Connection is made using a direct FTP session to the iSeries environment.
The account password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration.
FalconStor applications
This section can be deleted if you do not have FalconStor in your environment.
Connection is made using SSH or Telnet directly to the host running the FalconStor console.
The SSH/Telnet password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration. It is required to also have the
credentials to log in to the FalconStor application.
Server name IP address or SSH user/password FS user/password
hostname of the
console
ProtecTIER appliances
This section can be deleted if you do not have ProtecTIER in your environment.
Data is retrieved using the PTCLI tool. Servergraph accesses this tool locally if installed, or
remotely using SSH if available on a different system.
If using SSH, its password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration.
The PTCLI profile is the path to the users profile, as in the following command, in bold:
./ptcli ServerVersion --loginFile /path/to/myprofile
Server name PTCLI profile IP address or SSH user (if not local)
hostname (if not
local)
Sepaton appliances
This section can be deleted if you do not have Sepaton in your environment.
Connection is made using SSH directly to the Sepaton appliance.
The SSH password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration. Typically, Sepaton appliances only
come with a root account.
Please sign and date below then attach the completed document to an email and send it
back to your assigned Rocket Servergraph Sales Engineer or Account Executive for
review.
Company: ____________________________________
Date: ___________________________________