Вы находитесь на странице: 1из 12

Evaluation Checklist for VM Appliance

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.

Servergraph is installed with an evaluation license; typically up to a month, according to


when you download. We can provide an updated license file, extending the evaluation,
if necessary.
Please check that you are able to download and import the appliance (by opening the
OVF file, in ESXi) before requesting any extension.
Login accounts/password:
o root / changeme
o sguser / sguser (account Servergraph runs as)
o https: sg / sg
To change the login banner, edit /etc/motd.template and optionally /etc/motd (motd is
overwritten on restart).
After importing and booting the appliance, please check you can connect via https, to
display the Servergraph launchpad (the first page which loads after login).
The launchpad provides links to the Reports Builder, Admin Consoles, and searchable
documentation.
For Cloud Connector downloads, access the "ALL LINKS" page.
Because Rocket is currently not permitted to ship the TSM backup client, the appliance
will attempt to download the backup client using FTP. You will initially see a red 'warning'
banner across the launchpad, as the appliance attempts the download; if the download
fails, clicking the red banner will display instructions on how to add the backup client
manually (copy-paste, if possible).
o NOTE: The TSM backup client is ONLY required if TSM servers will be monitored
by Servergraph.
Reload the launchpad page occasionally (with F5, or Control-R)to see whether the
download has been successful; on success (after perhaps ten minutes), the red banner
will no longer be displayed.
The Admin Consoles require Java 7 to be installed on the client desktop; if you have only
Java 6 installed, you will see error messages indicating that Java 7 is required.

For help in configuring monitoring, or with any other questions,


please contact your Servergraph Sales Engineer or account manager

Tony.Heskett@rocketsoftware.com
Steve.Wright@rocketsoftware.com
James.Healy@rocketsoftware.com

Remote server requirements (device servers and any library managers)

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

Service Port (default)


ssh 22
http 80
https 443

Servergraph client requirements

The two administration consoles require Java SE 7 JRE.


Servergraph supports the following browsers:
Mozilla Firefox 3.5 and higher
Microsoft Internet Explorer 10 and higher
Google Chrome 17 and higher

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.

Set the SUPPRESSDUPMSG (suppress duplicate messages) option in the


DSMSERV.OPT file to NO.
REPORTRETRIEVE is enabled in dsmserv.opt for TSM version 7.1 and above.
Server IP address dsmadmc port User Accounting Method
name log location

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.

Server IP address SSH SSH Installation Path


name or User Password
hostname

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.

Server name IP address or MCDB Port MCDB User MCDB Passwd


hostname

5555 viewuser viewuser1


FastBack
This section can be deleted if you do not have FastBack in your environment.
Connection is made using SSH directly to the FastBack server. The Cygwin and related SSH
package must be installed on the FastBack 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.

Server IP address SSH user Installation path


name or
hostname

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.

Server name IP address or MS SQL Port MS SQL User MS SQL


hostname Password

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

IBM FlashCopy Manager for UNIX


This section can be deleted if you do not have FCM in your environment.
Connection is made using a direct SSH connection to the FCM environment.
The UNIX 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 Username Password Repository Path


hostname

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.

Server name IP address or Username Password


hostname

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.

Server name IP address or Username Password


hostname

Virtual Tape Libraries (VTLs)


Data Domain appliances
This section can be deleted if you do not have Data Domain in your environment.
Connection is made using SSH directly to the Data Domain appliance. The Data Domain user
must be part of the sysadmin group.
SSH 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 SSH user


hostname

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.

Server name IP address or SSH user


hostname
Databases
Oracle RMAN
This section can be deleted if you do not have Oracle RMAN in your environment.
Connection is made using a JDBC connection directly to the Oracle RMAN catalog database.
The Oracle password does not need to be provided to Rocket Software, but will have to be
available during the software installation and configuration.

Server IP address or DB Port DB Version DB user DB Name


name hostname

Library & Library Manager

TS3310, TS3500, TS4500


This section can be deleted if you do not have these libraries in your environment.
Connection is made using HTTP directly to the library host.

Server name IP address or


hostname
TSLM
This section can be deleted if you do not have TSLM in your environment.
Connection is made using SSH directly to a host running the ermmtool TSLM CLI utility. This
host may be the TSLM device itself, the Servergraph host if the tool was installed there, or any
other host with the ermmtool installed.
The SSH 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 SSH user/password


hostname

Other Applications / Appliances


NetApp appliance
This section can be deleted if you do not have NetApp in your environment.
Connection is made using SSH directly to the NetApp host.
The SSH 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 SSH user/password


hostname

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.

Customer Name: ____________________________________


PRINT
Customer Signature: ____________________________________
Customer Work Phone: ____________________________________

Company: ____________________________________

Date: ___________________________________