Automatic Updates

Topics | How To | Support | Related Topics


Overview

CommServe Cache

Install Updates on CommCell Computers

Other Related Operations

Other Considerations

Related Reports


Overview

The Automatic Update feature allows for the quick and easy installation of updates in your CommCell, ensuring that the software is up-to-date. The feature includes a cache for holding update packages. Update packages can either be downloaded automatically to this cache or manually pushed to the cache using the CopyToCache tool from a Network Drive that contains the Service Pack or the individual updates downloaded from the customer support Web site. Once the update packages are available in the cache, the system provides several options to seamlessly install the updates to all the computers in the CommCell.

Updates can be automatically downloaded from the FTP site for downloading updates, loaded directly from the Service Pack, or individual updates can be downloaded from the customer support Web site.

The following diagram displays the update transport mechanism as explained above.


CommServe Cache

The CommServe cache directory is configured to serve as a holding area for update packages. This can either be a local drive on the CommServe or a shared network directory.

If the CommServe cache area resides on a local drive, the appropriate CommServe service is used to copy and then install updates locally on the appropriate CommCell computers. Both Windows and UNIX clients can install updates from a local CommServe directory.

If the CommServe cache directory resides on a share, this must be a shared location with permissions set to write to the directory. Client computers that are not in the same domain as the domain in which the CommServe cache is located, must have bidirectional trust in place.

Windows computers that have permissions to access the share can install updates directly from it, without the need to first copy them. UNIX computers can use this directory for installation after copying the updates to a local directory. However, if you wish to configure UNIX computers to install updates directly from a cache, a separate UNIX cache (i.e., an NFS Mount Path) must be created. If a UNIX share is configured, and an automatic download of UNIX updates from the FTP site has occurred, a copy of each UNIX update is put in the CommServe cache and then in the UNIX cache.

NOTES

For a detailed explanation of CommServe and UNIX cache, see Install Updates on CommCell Computers.

For step-by-step instructions, see:

Methods of Populating CommServe Cache

FTP Download

The FTP download operation downloads the updates from the FTP source site to the CommServe cache directory. This server name can be changed if your FTP site for downloading updates differs from the default location or if you would like to reroute the FTP transfer through an FTP proxy. If necessary you can also configure an HTTP proxy server to connect to the FTP server to download the updates. The FTP download can be scheduled or run on-demand. The software also provides you with the options to schedule FTP download operations during the install of the CommServe software.

FTP download operation will download updates based on the operating system of the clients currently available in the CommCell. Operating systems that are supported are:

  • Windows
  • Netware
  • Solaris
  • AIX
  • Linux
  • HP
  • Macintosh
  • Tru64
  • FreeBSD
  • IRIX

To verify the ability to transfer files using an HTTP proxy, try to connect to an FTP site using a proxy server through your web browser.

For step-by-step instructions, see:

  • You can verify whether an update is available from the FTP site as well as if the CommServe cache directory has enough space to download the update from the site in the Automatic Update Configuration dialog box. To initiate this dialog box, launch the Control Panel, and select Automatic Update Configuration.
  • If an FTP connection cannot be made, the CopyToCache tool can be used to copy the updates to the CommServe cache directory.

CopyToCache

CopyToCache is a stand-alone tool residing on the CommServe, which can copy one or more updates to the CommServe cache directory. This tool provides you with the ability to push the update packages from a Network Drive that contains the Service Pack or the individual updates downloaded from the customer support Web site. This tool can be especially useful if an FTP connection cannot be made.

CopyToCache will:

  1. Clean the CommServe cache directory
  2. Copy the updates to the cache directory and decompress the files.
If copying updates from a UNIX Service Pack, which is found on multiple CD-ROMs, be sure to copy all of the updates from all of the media to the cache directory before installing updates via automatic update. This will ensure successful completion.    

For step-by-step instructions, see Run CopyToCache.


Install Updates on CommCell Computers

Once copied to the cache directory, updates are available to be installed on your CommCell computers. Installing updates can be completed in several ways. The following sections describe each of these methods.

All Clients (Windows, UNIX and NetWare) store updates locally before installing them.

This is the default configuration. No additional configuration is required.

This options allows you to install updates from the CommServe Cache. See Initiate the Installation of Updates from a Client or MediaAgent Computer for step-by-step instructions to install updates. See Automatic Updates for comprehensive information on updates.

NOTES

Installing Automatic Updates in a clustered environment will differ from installing the updates in a non-clustered environment. For more information, see Clustered Environment Considerations.

 
Some or all Windows Clients install from the share.

The CommServe Cache must be configured on a network Share. (See Configure CommServe Cache Directory for step-by-step instructions.)

Some or all Windows Clients must be configured to get updates from the share. (See Configuring a Remote Client or MediaAgent to Receive Automatic Updates for step-by-step instructions.)

In this configuration, when the Install Updates job is run,

  • Windows Clients that are configured to get updates from the share run the update install program from the CommServe cache.
  • For Windows, UNIX & NetWare Clients that install updates from the local drive, the system automatically downloads (or copies) the appropriate update packages from the CommServe Cache to the configured local drive on the individual client computers before installing the updates. The update packages are deleted as soon as the updates are installed.
Some or all UNIX clients install from a UNIX cache.

UNIX cache must be configured on an UNIX share. (See Configure a Shared Unix Cache Directory for step-by-step instructions.)

Some or all UNIX Clients must be configured to get updates from the share. (See Configuring a Remote Client or MediaAgent to Receive Automatic Updates for step-by-step instructions.)

In this configuration, when the Install Updates job is run,

  • UNIX Clients that are configured to get updates from the UNIX share run the update install program from the UNIX share.
  • Windows Clients that are configured to get updates from the share run the update install program from the CommServe cache.
  • For Windows, UNIX & NetWare Clients that install updates from the local drive, the system automatically downloads (or copies) the appropriate update packages from the CommServe Cache to the configured local drive on the individual client computers before installing the updates. The update packages are deleted as soon as the updates are installed.

NOTES

NetWare clients are by default configured to store updates locally before they are installed.

Clustered Environment Considerations

The procedure for installing Automatic Updates on a cluster will vary depending on whether or not the CommServe is installed on the virtual node in the cluster.

See either of the following as appropriate for step-by-step instructions:


Other Related Operations

Client Computer Groups

Automatic updates can be installed exclusively on client computer groups in your CommCell. Since your CommCell may not require the installation of updates on all clients, this option provides you with the ability to better control the update management of the clients in your CommCell environment.

For step-by-step instructions, see Configure Client Group Update Install.

Job Controller

The Download Update operation and the Install Update operation is displayed as a job in the Job Controller. The jobs can be suspended, resumed or killed. You can also view the details of the specific update job.

(For more information on job control, see Job Controller.)

The Job Manager stores the job status of each client chosen for Automatic Updates. The different types of job status are as follows:

Client Job Status Description
To Be Updated Initial state of the client. It also means Automatic Update needs to be run on this client.
Already Updated All updates are installed on the machine (As per the PatchInfo table in the database).
Jobs Running Before attempting InstallUpdates on the remote machine, and after copying updates remotely on the machine, if check for running jobs was found to be true, this status is set.

Note: The cache on the client is not cleaned here; the next automatic update will clean the client cache before attempting a fresh remote copy of updates.

Low Cache Space Set if the cache directory on the client machine has insufficient space
Unreachable Client Set if the client cannot be reached.
Upload in Progress Indicates remote copy of updates to the client machine is in progress.
Update in Progress Indicates Server has sent automatic update request to client
Update Succeeded Set after updates are successfully installed on the machine.
Update Failed Indicates installation of updates on the client machine failed.
Status Unknown Intermittent state set by the server if it is not able to get the status of the client before the timeout period. This is later reset to Update Succeeded, Update Failed or Failed to Update Database by the client. It may remain in this state if InstallUpdates on the client side either crashed or quit before even setting the status on the server.
Skipped for Reboot Set if the client requires reboot.
CommServe is at Lower Service Pack Level If CommServe is at lower Service Pack level, then installation of higher Service Pack on client machine is installed.
Failed to Update Database If setting client update information in the database fails. This signifies installation went fine, but database is out of sync; this can be corrected by running CommCell summary report.
Scheduled Reports are Running Set if some reports are running in the background for the CommServe; the job will be retried after the restart interval. The job can be retried by killing the reports from the Windows task manager, if required.
Vault Tracker Jobs are Running Set if vault tracker jobs are running in the background for the CommServe; the job will be retried after the restart interval. The job can be retried by killing the vault tracker process from the Windows task manager, if required.
Detected Reserved Resources Set if there are resources that are not released/freed, like tape drives, libraries, etc., for the MediaAgent being updated. Release the resources manually, and try again.

Events

Events are generated in the Event Viewer of the CommCell Console that indicate whether or not a FTP download of updates was initiated, has succeeded, or has failed. Events are also generated when an update installation was initiated, has succeeded, or has failed.

For more information about the Event Viewer, see the Event Viewer.

Alerts and Monitoring

Alerts can be configured from the CommCell Console to alert a user about the status of the download update and install update jobs. An alert will be generated if an FTP download of updates has succeeded, or has failed. Alerts are also generated when an update installation was initiated, has succeeded, or has failed.

To configure alerts, see Alerts and Monitoring.

Other Considerations

When using the automatic update feature, keep the following considerations in mind:

VERITAS and PolyServe Cluster

Depending on your cluster type, you are required to create and use the appropriate custom batch files in order to use the Automatic Updates feature under certain circumstances.

These batch files must be designed to find the physical node containing the services and to shut down and then restart the Services.

NOTES

The following procedure is relevant only to installs on a VERITAS cluster. For information regarding installs on a PolyServe cluster, consult your Software Provider. Also, the contents of the scripts displayed are merely an example of what you might use; be sure to create and use scripts that are suitable to your environment. Also, be sure to consider other services in your environment when creating and using these scripts.

  1. On your computer, navigate to the shared resource in the software installation folder.
  2. Navigate to the <install directory>\Base folder for the virtual machine.
  3. Create the appropriate batch file with the name "StopServiceGroup.bat" (you must assign this name to the file) to shut down the Services. For example:

set active=

hares -value GXCVD_002 LastOnline > hares.out

for /f  %%i in (hares.out) do set active=%%i

hares -offline GXEvMgrC_002 -sys %active%

hares -offline GXCVD_002 -sys %active%

exit 0

  1. Create the appropriate batch file with the name "StartServiceGroup.bat" (you must assign this name to the file) to start the Services. For example:

set active=

hares -value GXCVD_002 LastOnline > hares.out

for /f  %%i in (hares.out) do set active=%%i

hares -online GXCVD_002 -sys %active%

hares -online GXEvMgrC_002 -sys %active%

exit 0

  1. Before the Automatic Updates feature is scheduled to run, be sure to run the StopServiceGroup.bat batch file and then the StartServiceGroup.bat batch file.

Related Reports

Administrative Job Summary Report

The Administrative Job Summary Report displays a summary of all or select Administrative jobs.

Download Updates Summary Report

The Download Updates Job Summary Report displays a summary of all or select Administrative jobs.

Install Updates Summary Report

The Install Updates Job Summary Report displays a summary of all or select Administrative jobs.


Back to Top