Preparation for installation or upgrade
Review the following checklists before installing OpsCenter.
Table: OpsCenter installation and upgrade checklist for Windows lists the things you must check before you install OpsCenter on a Windows server.
Table: OpsCenter installation and upgrade checklist for Windows
Item | Task |
|---|---|
1. | Ensure that you install OpsCenter software on a compatible platform. |
2. | Ensure that no other installation is in progress while you install OpsCenter. In addition, Veritas recommends that you do not stop the installer forcefully while the OpsCenter upgrade is in progress. |
3. | If 8.3 file name creation is disabled on a Windows host, it is recommended that you enable it and restart the Windows host before installing or upgrading to OpsCenter components. If you install or upgrade to OpsCenter components on a Windows host where 8.3 name creation is disabled, then you must do the following:
|
4. | Ensure that the antivirus software is disabled before you install OpsCenter. |
5. | Ensure that your OpsCenter server is configured as a fixed host with a static IP address. |
6. | Ensure that the fully qualified domain name (FQDN) of your OpsCenter Server has no more than 44 characters. |
7. | For a new OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that after you install and start using OpsCenter, the database grows in size, and requires more space. |
8. | If you plan to upgrade OpsCenter, ensure the following: You should take care of these disk space requirements before you upgrade. |
9. | Before upgrading to OpsCenter, Veritas recommends that you take a hot backup of the OpsCenter database (without stopping OpsCenter) using the dbbackup utility. |
10. | If you plan to upgrade both the backup product like NetBackup, Backup Exec, or PureDisk and the OpsCenter components, it is recommended that you upgrade OpsCenter components first. By upgrading OpsCenter components before the backup product, OpsCenter can start collecting data from the backup product once it is added to the console. You must perform upgrades in the following order:
The above order also holds true if you plan to upgrade only OpsCenter and not the backup product. Always upgrade the OpsCenter Server first followed by the Agent and the View Builder. |
11. | If you plan to upgrade OpsCenter and have installed the OpsCenter database on a custom location, ensure that the free space on the drive where OS is installed is equal to or more than size of the current OpsCenter database. In case free space on the drive where OS is installed is less than size of the current OpsCenter database, use the following procedure before you upgrade:
|
12. | Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. See About communication ports and firewall considerations in OpsCenter. |
13. | Ensure that the name of the folder in which you install OpsCenter does not contain any special characters such as %, ~, !, @, $, &, ^, or #. |
14. | If a file called |
15. | Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters:
Check your respective OS documentation for more information on these parameters. |
16. | Install OpsCenter Server, Agent, and View Builder of the same versions. For example, Server 7.7 is compatible only with Agent 7.7 and View Builder 7.7. |
17. | Also in case OpsCenter components are installed on a dual stack IPv4 and IPv6 host, the default IP must be IPv4 and the hostname of the system must be configured accordingly. |
18. | In a clustered environment, first upgrade OpsCenter Server on the active node and then on the passive nodes. |
19. | To install OpsCenter on Windows 2008 or later version, you must log on as the official administrator. Users that are assigned to the Administrators Group but are not the official administrator cannot install OpsCenter in UAC-enabled environments. To allow users in the Administrators Group to install OpsCenter, disable UAC. |
Table: OpsCenter installation and upgrade checklist for UNIX lists the things you must check before you install OpsCenter on a UNIX server.
Table: OpsCenter installation and upgrade checklist for UNIX
Item | Task |
|---|---|
1. | Ensure that you install OpsCenter software on a supported platform. |
2. | Ensure that no other installation is in progress while you install OpsCenter. In addition, Veritas recommends that you do not stop the installer forcefully while the OpsCenter upgrade is in progress. |
3. | Ensure that your OpsCenter Server is configured as a fixed host with a static IP address. |
4. | Ensure that |
5. | Ensure that the fully qualified domain name (FQDN) of your OpsCenter Server has no more than 44 characters. |
6. | Ensure that ksh (Korn shell) is installed on the host where you want to install or upgrade OpsCenter Server. Warning: If you fail to install ksh before installation or upgrade, you may not be able to logon to OpsCenter user interface. |
7. | For OpsCenter installation on UNIX, a minimum space of approximately 2.5 GB is required at root folder before starting the installation process. This space is necessary for installing components like PBX, Perl, and VRTSvlic. In addition, the space is required to copy installation related logs at root location. If the space is not available at the root location, installation cannot proceed. |
8. | For a new OpsCenter installation, ensure that the database directory has at least 20 MB of available space. Note that once you install and start using OpsCenter, the database grows in size, and requires more space. |
9. | Ensure that the necessary ports are opened before you install OpsCenter on a hardened server. See About communication ports and firewall considerations in OpsCenter. |
10. | If you need to monitor a single master server, install OpsCenter on the NetBackup master server or media server (recommended). |
11. | Ensure that the name of the folder in which you install OpsCenter does not contain any special characters such as %, ~, !, @, $, &, ^, or #. |
12. | Ensure that the system on which the OpsCenter server is installed has valid values for the following OS parameters:
Check your respective OS documentation for more information on these parameters. |
13. | Ensure that the available disk space is at least two times the database size. This should be done before the upgrade. |
14. | Before upgrading OpsCenter, Veritas recommends that you take a hot backup of the OpsCenter database (without stopping OpsCenter) using the dbbackup utility. |
15. | If you plan to upgrade both the backup product like NetBackup, Backup Exec, PureDisk, or OpsCenter, it is recommended that you upgrade OpsCenter components first. By upgrading OpsCenter components before the backup product, OpsCenter can start collecting data from the backup product once it is added to the console. You must perform upgrades in the following order:
|
16. | If you plan to upgrade OpsCenter and have installed the OpsCenter database on a custom location, ensure that the free space on /tmp is equal to or more than the size of current OpsCenter database. In case the free space on /tmp is less than size of the current OpsCenter database, use the following procedure before you upgrade:
|
17. | If OpsCenter components are installed on a dual stack IPv4 and IPv6 host, the default IP must be IPv4 and the hostname of the system must be configured accordingly. |
18. | In a clustered environment, first upgrade OpsCenter Server on the active node and then on the passive nodes. |