agent
|
Sun StorageTek Backup Manager Release Notes |
The Sun StorageTek Backup Manager Release Notes contain important information about Sun StorageTek Backup Manager (SBM) release 1.0 software and information that was not available at the time the product documentation was published. Read this document so that you are aware of issues or requirements that can affect the installation and operation of the software.
The Release Notes consist of the following sections:
Sun StorageTek Backup Manager software helps you visualize and monitor storage backup environments from a central location. SBM provides valuable information by integrating backup reporting from vendor applications into asset reporting from Sun StorageTek tape libraries.
As the backup administrator, you can increase the reliability of your backup and tape environments by reviewing the data in SBM reports.
SBM is flexible and easy to use, both in smaller environments as well as large scale data centers.
TABLE 1 lists the system requirements for the Sun StorageTek Backup Manager software.
|
[Applicable to TSM Backup Agent only] Windows 2003 Standard or Enterprise Edition (recommended) w/ SP1 Windows 2003 Standard x64 or Enterprise x64 Edition (recommended) w/ SP1 |
|
Note: The SBM application requires jdk-1_5_0_09 (SPARC) or jdk-1_5_0_11 (x86) and is installed during preinstallation. |
|
|
Supported Tape Library Models (ACSLS or ACSLS High Availability: |
|
Backup Server Prerequisites: (Refer to the Sun StorageTek Backup Manager Installation Guide.) |
|
|
Backup Server Prerequisites: (Refer to the Sun StorageTek Backup Manager Installation Guide.) |
|
|
Note: The TSM Agent runs on a Windows server and communicates with backup server platforms that run Solaris 10 and Windows and 2000/2003. Backup Server Prerequisites: (Refer to the Sun StorageTek Backup Manager Installation Guide.) |
|
The following sections provide information about known issues and bugs filed against this product release:
A description of each known issue or bug is preceded by its Change Request (CR) number. If a recommended workaround is available for a bug, it follows the description.
CR 6632331, CR 6631122 -- In multiprocessor SPARC or x64 system environments, the Data Acquisition Agents might not be listed under Admin > Data Acquisition Agents > Configure Agents after you install the software.
Workaround -- Manually stop and restart the agents using the following procedure. (See "SBM Agent Control Commands" in the Sun StorageTek Backup Manager Administration Guide for a listing and description of the agent commands.)
1. Log in to the SBM server as root.
2. Run the following command to view the list of installed agents:
3. Disable all the agents installed using the svcadm disable agent_name command.
4. Restart each agent in the following order:
For example, to disable and enable the aggregator agent, enter the following commands:
After you restart each installed agent, the agents will be listed on the Admin > Data Acquisition Agents > Configure Agents page.
CR 6562379 -- All SBM agents and database processes are controlled by the Service Management Facility (SMF). You can stop and start these processes using the SMF utility. On reboot, SMF utility detects if these components are down and restarts them. For this release, starting and stopping the SBM application server is not controlled by SMF.
Workaround -- If the application server goes down, you must manually restart the application server as described in the following procedure.
1. Log in to SBM server as root.
su - sbmapp
3. Change to the following directory:
cd /opt/sbm/sbmapp/glassfish/bin
4. To start the application server, issue the following command:
./asadmin start-domain domain1
A messages informs you that the application server has started.
If the application server fails to start, contact Sun support.
CR 6571953 -- If you attempt to delete the SBM user accounts sbmapp, sbmdb, and sbm while the GlassFish server is running, problems will occur when you try to reinstall the SBM application.
The GlassFish server creates temporary files in the /tmp directory. If the accounts are deleted and re-created while GlassFish is running, GlassFish cannot map the SBM user account that owns the file with its corresponding UID value and fails to remove the temporary files.
Workaround -- Stop the GlassFish server before deleting the SBM user accounts.
CR 6566017 -- The installation process creates a user account for each of the major SBM components: sbm, sbmapp, and sbmdb. When you uninstall the SBM software, these accounts are not removed from the system.
Workaround -- Manually remove the sbm, sbmapp, and sbmdb accounts and the SBM install directory after all the components are removed. See the following procedure.
1. Log in as root to the SBM server.
2. Run the userdel command for each SBM user account.
# userdel -r sbm # userdel -r sbmdb # userdel -r sbmapp
3. Run the groupdel command for each SBM user account.
# groupdel sbm # groupdel sbmapp # groupdel sbmdb
CR 6585393 -- During testing, it was determined that use of the UNIX script command caused the GlassFish application server to shutdown unexpectedly.
Workaround -- Manually restart the application server as described in Starting the Application Server.
CR 6564216 -- The installation process does not detect if other instances of GlassFish server are installed on the system.
Workaround -- Before installing the prerequisite software, verify if any other instances of GlassFish servers are running in the environment. If an existing GlassFish server is running on the default port (4848), configure the SBM GlassFish server to run on another port, as described in the following procedure.
The following procedure shows the GlassFish server running on the default port 4848.
1. Log into the admin console of the GlassFish server.
http://SBM management server:4848
The defaults provided by GlassFish are user name: admin and password: adminadmin.
2. From the left menu tree, click Application Server.
3. To stop the GlassFish server, click Stop Instance.
4. Log into the SBM server using the sbmapp user account.
5. Go to the GlassFish server installation root directory located at:
/opt/sbm/sbmapp/glassfish
6. Edit the configuration file:
a. Open the file domain.xml, located in the GlassFish server installation root directory:
glassfish_ install_root_directory/domains/domain1/domains/domain1/config/
d. Review all port settings to make sure that all port values contain non-conflicting numbers.
e. Save and close the domain.xml file.
7. Restart the GlassFish server by issuing the following command:
glassfish_ install_root_directory/bin/asadmin start-domain
8. To verify the SBM application is running on the new port, log into the web server using the new HTTP listening port:
http://SBM management server:new_listening_port
For more information about the GlassFish server, see Chapter 1 (page 25) of the following document:
https://glassfish.dev.java.net/nonav/javaee5/docs/SJSASEEIG.pdf
CR 6583318 -- The application server becomes non-responsive if the database is the only SBM component to be reinstalled.
Workaround -- Manually stop and restart the application server as described in the following procedures.
1. Log into the SBM server as root.
su - sbmapp
3. Change to the following directory:
cd /opt/sbm/sbmapp/glassfish/bin
4. To stop the application server issue the following command:
./asadmin stop-domain domain1
A message informs you that the application server has stopped.
1. Log in to SBM server as root.
su - sbmapp
3. Change to the following directory:
cd /opt/sbm/sbmapp/glassfish/bin
4. To start the application server issue the following command:
./asadmin start-domain domain1
A messages informs you that the application server has started.
If the application server fails to start, contact Sun support.
CR 6580028 -- The tape library Statistics Report displays blank graphs for all libraries that are monitored by the ACSLS agent. The interface used by the ACSLS agent to extract information from the libraries does not support the gathering of the required statistical data.
CR 6574022 -- The tape library agent does not gather information related to partitioning. When reporting on a partitioned library, the SBM agent will report the correct configuration information; that is, a single partitioned library is reported as two separate libraries in the SBM data. However, no specific partitioning information is collected or reported on.
CR 6582320 -- The validation process considers all strings that contain the text “unix”, “sol” or “win” as valid. Because an exact comparison is not performed on the strings, incorrect values such as "unixttt" might be accepted and cause the agent to be incorrectly configured.
Workaround -- When specifying the operating system use the following rules.
For Windows Backup Master servers enter:
For UNIX master servers one of the following:
CR 6554287 -- Agents that collect data in remote mode must be named id_dsa or id_rsa. Naming identity keys other than the default names is not supported by the agents.
Workaround -- To successfully collect data remotely, you must configure the agents exactly as described in Appendix B of the Sun StorageTek Backup Manager Installation Guide.
CR 6573607 -- The SBM backup agents generate different error messages for the same error condition, depending on the backup master server platform that it is remotely communicating with.
"Error! Executing the '<command>' command on host '<host>' returned 'user id was not superuser (140)'. Check your configuration settings.“
where <command> is the remote command being executed on the backup master server <host>.
"no data returned for '<command>' command on host '<host>'. Possible configuration problem.
where <command> is the remote command being executed on the backup master server <host>.
CR 6580042 -- The Tape Library Details pages do not report on certain fields for tape libraries that are monitored by the ACSLS agent. The interface used by the ACSLS agent to extract information from the libraries does not gather the required statistical data. Fields that are not populated are as follows:
CR 6552209 -- If the ACSLS is not configured properly, the agent will become non-responsive. A non-responsive agent could be caused by:
Workaround -- Contact Sun Support for information about how to correct the problem. See Service Contact Information.
CR 6575319 -- In certain scenarios, an agent will switch to maintenance mode when you manually stop the agent using the Service Management Facility (SMF) command.
If a communication or configuration exists in the environment, the SMF cannot gracefully shut down the agent or the SSI processes. In this case, the agent will be put into maintenance mode.
Workaround -- Contact Sun Support for information about how to correct the problem.
CR 6581537 -- If communications problems exist between the SSI and ACSLS servers, the ACSLS agent might need restarting, and you need to be aware of certain shutdown/restart considerations.
Workaround -- Contact Sun Support for information about how to correct the problem. See Service Contact Information.
CR 6557532 -- If the NetWorker (Legato) agent is configured to connect to a client that does not exist, the agent will report the client as <SEVERE>.
Workaround -- The NetWorker backup administrator should check and correct the configuration problem on the backup master server.
CR 6573607 -- The SBM backup agents generate different error messages for the same error condition, depending on the backup master server platform that it is remotely communicating with.
"Error! Executing the '<command>' command on host '<host>' returned 'user id was not superuser (140)'. Check your configuration settings.“
where <command> is the remote command being executed on the master server <host>.
"no data returned for '<command>' command on host '<host>'. Possible configuration problem.
where <command> is the remote command being executed on the backup master server <host>.
From the Client Jobs Details page you can review the distribution of errors for the selected backup master server. The SBM application standardizes the Job Status numerical values for the success, partial, and failure states.
0 |
|
1 |
|
> 1 |
Each SBM backup agent reports its own unique set of error codes.
8100 |
|
8200 |
|
9100 |
|
9200 |
|
|
SBM reports the status code and error message exactly as it is supplied by the NetBackup product. For more information, see the vendor documentation. |
|
Every effort was made to collect data from NetBackup master servers as a non-root or administrator user, but several of the NetBackup commands require the user to be a superuser.
When these commands are attempted as a non-root or administrator user, an error is returned as shown in the following examples:
$ /usr/openv/netbackup/bin/admincmd/bppllist
user id was not superuser (140)
Adding the non-root user to the authorized.txt file (located in NetBackup_Install_Path/var) allows the user to run some of the NetBackup commands, but not all of them. The bppllist command that returned the “user id was not superuser (140)” was unaffected by the changes to the authorized.txt file.
The agent requires the policy list returned by bppllist to run most of the other commands that populate the backup agent tables.
Attempts to modify the authentication method files in NetBackup_Install_Path/var/auth caused problems in the environment, such as communication problems between the servers and clients, and caused all jobs to fail. This method of authorization and authentication is scheduled to be removed from the NetBackup software in the next major release (7.0). Veritas is transitioning to the Veritas Security Service (VxSS).
Attempts to install and configure the VxSS processes caused problems in the environment. When enabled, VxSS blocked root user access to the Administration Console on the NetBackup Master server. This would be unacceptable in all NetBackup environments. Even if it was possible to set up VxSS to allow a non-root user to issue commands, it would be environment-specific and the chances of adversely impacting the environment would be high.
Appendix B, Connecting to a NetBackup UNIX Master Server Using SSH, page 5
5. Set a password for the SBM user.
It is not necessary to set a password for the SBM user.
scp -p id_dsa.pub root@backup_masterserver_hostname:~/.ssh/id_dsa.pub.sbm Appendix D, Running the Uninstall Script, page 70
In addition to these release notes, the following documentation is posted on the Documentation web site at:
http://docs.sun.com/app/docs/prod/stortek.bumgr10
If you need help installing or using this product in the United States, call
1-800-USA-4SUN, or go to:
|
Copyright |
Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any.
Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.
Sun, Sun Microsystems, the Sun logo, Java, docs.sun.com, StorageTek, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
The OPEN LOOK and Sun
Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
U.S. Government Rights--Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
Copyright 2008 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, États-Unis. Tous droits réservés.
Sun Microsystems, Inc. possède les droits de propriété intellectuels relatifs à la technologie décrite dans ce document. En particulier, et sans limitation, ces droits de propriété intellectuels peuvent inclure un ou plusieurs des brevets américains listés sur le site http://www.sun.com/patents, un ou les plusieurs brevets supplémentaires ainsi que les demandes de brevet en attente aux les États-Unis et dans d’autres pays.
Ce document et le produit auquel il se rapporte sont protégés par un copyright et distribués sous licences, celles-ci en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a.
Tout logiciel tiers, sa technologie relative aux polices de caractères, comprise, est protégé par un copyright et licencié par des fournisseurs de Sun.
Des parties de ce produit peuvent dériver des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux États-Unis et dans d’autres pays, licenciée exclusivement par X/Open Company, Ltd.
Sun, Sun Microsystems, le logo Sun, Java, docs.sun.com, StorageTek, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux États-Unis et dans d’autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux États-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.
L’interface utilisateur graphique OPEN LOOK et Sun a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox dans la recherche et le développement du concept des interfaces utilisateur visuelles ou graphiques pour l’industrie informatique. Sun détient une license non exclusive de Xerox sur l’interface utilisateur graphique Xerox, cette licence couvrant également les licenciés de Sun implémentant les interfaces utilisateur graphiques OPEN LOOK et se conforment en outre aux licences écrites de Sun.
LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DÉCLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES DANS LA LIMITE DE LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE À LA QUALITÉ MARCHANDE, À L’APTITUDE À UNE UTILISATION PARTICULIÈRE OU À L’ABSENCE DE CONTREFAÇON.
Starting the Application Server