The topics in this section discuss the activities that a system administrator will perform periodically in order to safeguard the test system, and to upgrade the system to a later software release or to a greater system capacity.
Most maintenance activities require that the system database is idle, which means stopping the TAS processes. When the TAS is stopped, no one can login to or use the test system. The TAS can be stopped using a delay timer and a message that notifies all of the active users that a shut down is pending, giving them time to complete their tests and save their work.
You can protect your system's test libraries and configuration information by making regular backups of the system database. Test results are not included in the backup. If you perform backups on a regular schedule, you can greatly reduce the lost time and lost information that can result from a hard drive failure or other catastrophic system failure.
Best practices:
Keep multiple backup copies so that at the last two backups are always available.
Always keep at least one recent backup on another platform or on a network share.
Backup the database immediately before installing an upgrade.
In the event of a hardware failure or database corruption, restore the system database from the latest "known good" system backup.
Your test system can be upgraded to a new software release, upgraded to a larger system capacity, or both at the same time. Any upgrade should be coordinated with your customer service representative.
A system software upgrade consists of installing the upgrade on the TAS, which upgrades the TAS system software and the Test Suite, installing a new license (if necessary), and upgrading each test server's software. A capacity upgrade consists of adding to the number of test servers recognized by the TAS or to the system's capacity and throughput by installing a new system license.
|
IMPORTANT: The first two digits of the software versions for the different system elements (TAS, test servers, and Test Suite) define the compatibility level of the software. For example, if you upgrade your TAS from version 1.3.0.6 to 1.3.1.0, the system will be operational as long as the test server and Test Suite versions begin with 1.3. |
Your test system comes with a pre-installed account on all platforms — cfguser — that is used to configure the test system's servers during installation, and is also used to login to the TAS Manager Console / TAS Manager Web UI. One Super User user account is also pre-installed on the system.
You should change the passwords for these accounts as part of the installation process, and can change them periodically to further secure your system. The defaults for these passwords can be found in your Installation Guide.
Related Topics