Veritas NetBackup OpsCenter upgrade

Veritas NetBackup OpsCenter upgrade

Pre-Checks:

1. OpsCenter should run on same version as Netbackup is running or should run on higher version. OpsCenter/OpsCenter Analytics must always be running the same or higher version.

2. Make sure that OpsCenter is compatible with Operating System and Netbackup.

3. OpsCenter should always run on a dedicated server and not on a NBU master

4. Ensure that all required ports are open on OpsCenter Server.

OpsCenter Port requirement:

Technote: https://www.veritas.com/support/en_US/article.100002391

Steps to Upgrade OpsCenter Analytics

1.    Backup OpsCenter Database

OpsCenter is shipped with a database backup script that performs backup of the database , the corresponding database password file, and the encryption key file without interrupting its operations, which is referred to as hot backup. On UNIX as well as Windows platforms, the script overwrites the existing database files before backing up or restoring them.

Note:

Regular file system backups are not sufficient for backing up the OpsCenter database. You must schedule periodic hot backups for the OpsCenter database to avoid losing any important data.

To back up the OpsCenter database

1. Log on to the OpsCenter database server host in one of the following ways:

Windows	As an administrator or user in the Administrator group
UNIX	root

2. Open the Windows command prompt or the UNIX console.
3. Run the backup script that is appropriate for your platform. Specify one of the following backup directories depending on your platform:

LINUX	/opt/SYMCOpsCenterServer/bin/dbbackup.sh /u01/backup/OpsCenter/

4. The backup script backs up the database files, database password files, and encryption key file in the backup directory that you specified.
5. Ensure the compatibility of the OpsCenter with the OS Version ad Bit.
6. Download OpsCenter installation file to the OS.
7. Run the installation and follow the process.

Note: OpsCenter should always run on a dedicated server and not on a NBU master

Documentation:

Backing up the OpsCenter database

Technote: https://www.veritas.com/support/en_US/doc/27537447-127427700-0/v28842080-127427700

Download OpsCenter:

Link: https://www.veritas.com/content/support/en_US/article.100019594.html 

How to Backup OpsCenter Database:

Link: https://www.veritas.com/support/en_US/doc/27537447-127427700-0/v28842080-127427700

Upgrading OpsCenter on UNIX

Use the following procedure to upgrade to OpsCenter software on UNIX hosts.
Note:

Veritas recommends that you do not cancel or interrupt the installation process once it is started.

To upgrade OpsCenter Server on UNIX

1. If you plan to upgrade your backup product and OpsCenter, ensure that you upgrade OpsCenter first. When upgrading OpsCenter, always upgrade the OpsCenter Server first followed by the Agent and then the View Builder.
2. Open a UNIX console and log on as root on the target host.
3. Mount the OpsCenter product DVD on the OpsCenter Server that you want to upgrade.
4. Untar OpsCenter_7.7_Unix.tar.gz
5. Cd /u01/share/soft/OpsCenter_7.7_Unix
6. Type the following command: ./install. Press Enter.
7. [root@em01 OpsCenter_7.7_Unix]# ./install

8. The Welcome message is displayed. Press Enter to continue.

9. The installer then checks if OpsCenter Server is installed on the system or not. It prompts you in case OpsCenter Server is already installed. The installer also examines the system for existing packages. 

10. The following prompt is displayed:

Where should the existing OpsCenter database and configuration files be backed up? 

An 'OpsCenterServer_backup' directory will be created within the directory that you specify to store these 

files. (/var/symantec/)

Type the directory name in which the existing OpsCenter database and configuration files can be saved and then press Enter.

To accept the default directory path (/var/symantec), press Enter.

11. The installer displays a list of components that will be installed or upgraded like PBX, OpsCenter Server, OpsCenter user interface and so on. Review this list and press Enter to continue.

12. The installer prompts you with the following question:

installOpsCenterServer is now ready to upgrade OPSCENTERSERVER.

Are you sure you want to upgrade OPSCENTERSERVER? [y,n,q] (y)

Press Enter to continue OpsCenter upgrade.

13. The installer prompts you with the following question:

Participate in the NetBackup Product Improvement program? [y,n,q] (y)

Press Enter if you want to participate in the NetBackup Product Improvement program or press n if you do not want to participate.

14. The installer prompts you with the following question:

Do you want to import users from <remote AT host name> to OpsCenter AT?

Press Enterto import users from the earlier OpsCenter versions.

For more details, refer to the About Importing Authentication Settings section.

If the import fails, you need to reset password of all OpsCenter(vx) users.

15. By default, in OpsCenter, the database is upgraded in the beginning. However, you can choose to first upgrade the OpsCenter software.

The database upgrade process starts. In this process, the OpsCenter data is migrated to the new OpsCenter database version. The database process may take time depending on your database size.

The following message is displayed:

The database upgrade is in progress. This may take some time based on the database size. You can see the progress and current status in /var/tmp/(directory)/db/log/dbManager_<timestamp>_.log file.

After complete installation, the logs are copied to the following location:/var/VRTS/install/logs/LogDirectory/db/log

LogDirectory is generated during the upgrade progress.

16. The installer displays the OpsCenter packages that are installed. Depending on the installed packages, the following message may be displayed:

The following packages were found on the system. However the package

versions are older than the ones required by OpsCenter.

VRTSOpsCenterServer existing version was found on the system, 

but OpsCenter requires VRTSOpsCenterServer new version

VRTSOpsCenterGUI existing version was found on the system, 

but OpsCenter requires VRTSOpsCenterGUI new version

VRTSOpsCenterLegacyServer existing version was found on the system, 

but OpsCenter requires VRTSOpsCenterLegacyServer new version

The installer then uninstalls the older packages and installs new version of OpsCenter Server.

17. OpsCenter Server is installed. Configuration changes are made to the system.
18. All the OpsCenter processes are started. The following information is also displayed:

o    Web URL to access OpsCenter console

o    Location of install log and summary files.

Note:

After successful upgrade, OpsCenter database password is set to an auto-generated string, if the earlier password is still the default one, that is 'SQL'. Veritas recommends that you change the database password after the installation.

If you had changed the default password in the earlier version, you do not need to change it again. The installer retains the old password that you can use in the current version.

Decommissioning a media server

Decommissioning Netbackup Media Server

Following information about is decommissioning a NetBackup media server.

Your path through the nbdecommission wizard depends on how you respond to the wizard prompts. Depending on your environment and how you respond to prompts, the wizard may advise you to perform an action and then exit. To continue in the wizard, you must run the wizard again after you perform the advised action. You may have to exit and rerun the wizard several times.

If active jobs exist on the media server, you must cancel them before the command can begin to decommission the media server. Alternatively, you can wait until they finish.

The OldServer does not have to be up and responsive.
Veritas recommends that you preview the media server references before you decommission a media server.

The nbdecommission command logs to the standard NetBackup administrator commands log directory.
Two procedures exist, as follows:
1. Replace an old media server with a new media server
2. Decommission a media server.

To replace an old media server with a new media server
1. Run the nbdecommission command on the master server or on a media server that is not the object of this operation. The following is the command syntax:

On Windows:
install_path\NetBackup\bin\admincmd\nbdecommission -oldserver OldServer [-newserver NewServer] [-file decom_ops.txt]

On UNIX:
/usr/openv/netbackup/bin/admincmd/nbdecommission -oldserver OldServer [-newserver NewServer] [-file decom_ops.txt]
Replace OldServer with the name of the host to be decommissioned.

-newserver is optional. If you specify a new server, the new server becomes the default media server for the replacement operations. If you do not specify a new server, the wizard prompts you for the new server for each storage type that contains valid backup images. This method is useful if you want to move backup images to different media servers. For example, you can move backup images from tape storage to one media server and backup images from disk storage to another media server.
-file is optional. It writes the command operations to the specified file. Replace decom_ops.txt with a name that denotes its purpose or contents. Veritas recommends that you use the -file option to maintain a record of the command operations.

2. Follow the prompts and perform the requested actions.
For example, the command may make changes on the master server and on multiple media servers. You may be required to restart the NetBackup services on those servers so that the changes take effect.

To decommission a media server
a) Run the following command on the master server or on a media server that is not the object of this operation. The OldServer does not have to be up and responsive.

On Windows:
install_path\NetBackup\bin\admincmd\nbdecommission -oldserver OldServer

On UNIX:
/usr/openv/netbackup/bin/admincmd/nbdecommission -oldserver OldServer
Replace OldServer with the name of the host to be decommissioned.

b) Follow the prompts and perform the requested actions.

bphdb exit status = 5449: The script is not approved for execution

Registering authorized locations used by a NetBackup database script-based policy

To add an authorized location

    Open a command prompt on the client.
    Use nbsetconfig to enter values for an authorized location. The client privileged user must run these commands.

On UNIX:
root@erpddb01:/usr/openv/netbackup/bin/nbsetconfig
nbsetconfig>DB_SCRIPT_PATH = /export/home/oraprod/scripts
nbsetconfig>DB_SCRIPT_PATH = /export/home/oraprod/scripts/rmanfull.daily
nbsetconfig>
<ctrl-D>

Reference: NetBackup Support Knowledge base

Boot Virtual Machine from a CD

vm.cfg must be like this

disk = ['file:/OVS/running_pool/121_SRVAXIPMI180_RedHatES_51_Tomcat_DVLP/System.img,hda,w',
'file:/OVS/running_pool/121_SRVAXIPMI180_RedHatES_51_Tomcat_DVLP/Data.img,hdd,w',
'file:/OVS/iso_pool/"YOUR_ISO_GROUP"/rhel-5.1-server-x86_64-dvd.iso,hdc:cdrom,r',
]

or like this, it's depend where is your DVD_ISO

disk = ['file:/OVS/running_pool/121_SRVAXIPMI180_RedHatES_51_Tomcat_DVLP/System.img,hda,w',
'file:/OVS/running_pool/121_SRVAXIPMI180_RedHatES_51_Tomcat_DVLP/Data.img,hdd,w',
'file:/root/rhel-5.1-server-x86_64-dvd.iso,hdc:cdrom,r',
]

Oracle VM Using the P2V Utility

Using the P2V Utility

When you use the P2V utility, you are prompted for all required information.

To create a virtual machine image of a computer:

1. Insert the Oracle VM Server CDROM into the CDROM drive of the computer you want to image.

Note

This procedure is for 64-bit computers. If you want to convert a 32-bit host computer to a virtual machine template, you must use the Oracle VM 2.x CD.

2. Start the computer with the Oracle VM Server CDROM.
3. The Oracle VM Server installation screen is displayed.

At the boot:prompt, enter:

p2v

Press Enter.

4. The CD Found screen is displayed.

If you want to make sure the CDROM is error free, you can have the installer test it for errors. To test the CDROM, select OK and press Enter. The CDROM is tested and any errors are reported.

To skip media testing and continue with the installation, select Skip and press Enter.

5. The P2V Network Configuration screen is displayed.

Select your Ethernet driver from the list displayed.

If your computer uses DHCP to assign its IP address, select Automatically obtain via DHCP.

If your computer uses a static IP address, select Manually configure, and enter the IP address and netmask, gateway, domain and name server for your computer.

Select OKand press Enter.

6. The disk selection screen is displayed.

Select the disk partition(s) on the computer to include in the guest image. Select OK and press Enter.

7. The Other parameters for VM screen is displayed.

Enter information about the guest image for:

• VM (guest) name
• VM (guest) memory
• Number of virtual CPUs
• Console password. This is no longer required, but you must enter a value.

Select OKand press Enter.

8. A secure web server (HTTPS) is started. The IP address of the computer, and port number the web server is available on is displayed.

Open a web browser on another computer and enter the URL created using the information displayed on the computer running the P2V utility, for example

https://192.168.2.6/

You do not need to enter the port number as this is the default port number for HTTPs connections. A directory listing is displayed which contains the files created by the P2V utility. Take a note of the URLs for the vm.cfg and *.img files as you use them in the next step when importing the virtual machine into Oracle VM Manager.

Log in to Oracle VM Manager and import the guest using the import template feature. When you import the guest, you should add the URLs for each virtual disk image and the virtual machine configuration file on a new line in Template URLsfield in the Import Templatedialog, as shown below.

9. When the virtual machine template is added to the repository, you should terminate the P2V utility on the host computer. Press Control+C to terminate the P2V utility on the computer. Remove the Oracle VM Server CDROM from your CDROM drive. Restart the computer.

The guest image is created and available in the repository as a hardware virtualized virtual machine template.

Installing Oracle VM Manager

It takes approximately 8-15 minutes to complete the installation of Oracle VM Manager, depending on the performance of the Oracle VM Manager host, and the installation type you choose.

Before you begin the installation, download the Oracle VM Manager software from:

http://edelivery.oracle.com/oraclevm

This section describes the Oracle VM Manager installation process.

Note

If you want to install Oracle VM Manager in a virtualized environment, do not install it on Oracle VM Server (dom0) directly; install it into a virtual machine running on an Oracle VM Server.

Mounting the Oracle VM Manager Installation Media

Before you can run the Oracle VM Manager installer, you must mount the installation media. You can either burn the installation media to a CD and mount the CD, or mount the ISO file directly from the hard drive. Which ever way you choose to mount the installation media, you should perform this as the root user on the computer on which you want to install Oracle VM Manager.

• To install Oracle VM Manager from a CD, burn the Oracle VM Manager ISO file to a CD. Insert and mount the Oracle VM Manager CD using the following commands:

·         # mkdir mount-point

# mount /dev/cdrom mount-point

Where mount-pointrefers to the directory on which you mount the ISO file.

• To install Oracle VM Manager from a hard drive, locate the folder that contains the ISO file. Mount the ISO file to an existing directory using the following commands:

·         # mkdir mount-point

# mount -o loop OracleVM-Manager-version.iso mount-point

Where mount-pointrefers to the directory on which you mount the ISO file. For example:

# mkdir /OVMCD

# mount -o loop OracleVM-Manager-3.x.x.iso /OVMCD

You can find all the mounted files under the directory /OVMCD.

Note

The location of the mounted Oracle VM Manager ISO file should be accessible by the oracle user.

Running the Oracle VM Manager Installer

To install Oracle VM Manager, enter the mount point you created in above step for example, /OVMCD and start the installation with the runInstaller script as the root user:

# cd /OVMCD

# ./runInstaller.sh

A set of installer options are displayed:

Please select an installation type:

   1: Simple (includes database if necessary)

   2: Custom (using existing Oracle database)

   3: Uninstall

   4: Help

At the command prompt, enter 1 to perform a Simple installation or 2 to perform a Custom installation. If you already have Oracle VM Manager installed and want to uninstall it, select 3 to Uninstall.

Simple Installation (includes database if necessary)

The Simple installation option should be used if you do not have an existing Oracle Database installed or if you would like to keep Oracle VM Manager running independently of any existing Oracle Database.

The Simple installation option installs MySQL Enterprise Edition, MySQL Enterprise Edition Backup, Oracle WebLogic Server, Oracle Application Development Framework (ADF), Java, and Oracle VM Manager on the local system. The following example shows the Simple installation process.

Note

If you have an existing MySQL installation on the system where you intend to install Oracle VM Manager you should backup your databases and uninstall it. Oracle VM Manager requires exclusive use of MySQL due to the specific tuning parameters that it applies to the configuration. Oracle VM Manager uses MySQL Enterprise Edition on a non-standard port. The licensing of the MySQL Enterprise Edition provided with Oracle VM Manager grants exclusive use to Oracle VM. You must not use the MySQL server provided for any other purpose. If MySQL is installed as a result of a previous installation of Oracle VM Manager the installation prompts you to provide the hostname, root password and port number that was used in the previous installation.

Example 4.1. Simple Installation

# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer

Oracle VM Manager Installer log file:

  /tmp/filename.log

Please select an installation type:

1: Simple (includes database if necessary)

2: Custom (using existing Oracle database)

3: Uninstall

4: Help

   Select Number (1-4): 1

The installation process starts, and the following is displayed:

Starting production with local database installation ...

Verifying installation prerequisites ...

One password is used for all users created and used during the installation.

Enter a password for all logins used during the installation:

Enter a password for all logins used during the installation (confirm):

Enter a system-wide password that can be used when creating accounts for all of the components within the Oracle VM Manager installation. This password will be used for your MySQL install, WebLogic and Oracle VM Manager itself. You will need to confirm your password after you have entered it.

Verifying configuration ...

Warnings may occur if not all recommendations are met.

The installer provides a final option to continue or to abort the installation process. Enter 1 to continue. Progress of the installation is output on your screen step by step, as shown below:

Start installing the configured components:

   1: Continue

   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database Software...

Installing Database Software...

Retrieving MySQL Database 5.5 ...

Unzipping MySQL RPM File ...

Installing MySQL 5.5 RPM package ...

Configuring MySQL Database 5.5 ....

Step 2 of 9 : Java ...

Installing Java ...

Step 3 of 9 : Database schema ...

Creating database 'ovs' ...

Creating user 'ovs' for database 'ovs'...

Step 4 of 9 : WebLogic ...

Retrieving Oracle WebLogic Server 11g ...

Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...

Retrieving Oracle Application Development Framework (ADF) ...

Unzipping Oracle ADF ...

Installing Oracle ADF ...

Installing Oracle ADF Patch...

Step 6 of 9 : Oracle VM  ...

Retrieving Oracle VM Manager Application ...

Extracting Oracle VM Manager Application ...

Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...

Creating Oracle WebLogic Server domain ...

Starting Oracle WebLogic Server 11g ...

Configuring data source 'OVMDS' ...

Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...

Deploying Oracle VM Manager Core container ...

Deploying Oracle VM Manager UI Console ...

Deploying Oracle VM Manager Help ...

Granting ovm-admin role to user 'admin' ...

Set Log Rotation ...

Disabling HTTP and enabling HTTPS...

Configuring Https Identity and Trust...

Step 9 of 9 : Oracle VM Manager Shell ...

Retrieving Oracle VM Manager Shell & API ...

Extracting Oracle VM Manager Shell & API ...

Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...

Extracting Oracle VM Manager Upgrade tool ...

Installing Oracle VM Manager Upgrade tool ...

Retrieving Oracle VM Manager CLI tool ...

Extracting Oracle VM Manager CLI tool...

Installing Oracle VM Manager CLI tool ...

Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...

Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...

Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...

Enabling Oracle VM Manager service ...

Shutting down Oracle VM Manager instance ...

Restarting Oracle VM Manager instance ...

Waiting for the application to initialize ...

Oracle VM Manager is running ...

Oracle VM Manager installed.

Please wait while WebLogic configures the applications... This can take up to 5 minutes.

When the installation is complete a summary similar to the following is displayed:

Installation Summary

--------------------

Database configuration:

  Database type               : MySQL

  Database host name          : localhost

  Database name               : ovs

  Database listener port      : 49500

  Oracle VM Manager schema    : ovs

Weblogic Server configuration:

  Administration username     : weblogic

Oracle VM Manager configuration:

  Username                    : admin

  Core management port        : 54321

  UUID                        : 0004fb00000100008e2c477634f634c9

Passwords:

There are no default passwords for any users. The passwords to use for Oracle VM Manager,

Database, and Oracle WebLogic Server have been set by you during this installation. In

the case of a default install, all passwords are the same.

Oracle VM Manager UI:

  https:/hostname:7002/ovm/console

Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual

machine's console.

For more information about Oracle Virtualization, please visit:

  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important

Make sure you delete the temporary configuration file created during the installation:

/tmp/ovm_configid

This file is useful for debugging installation issues, but does contain some sensitive information that may present a security issue if left in place.

Warning

Some performance degradation may be noted when installing onto an Oracle Linux system using an EXT4 formatted filesystem. This is the result of the default mount parameters for EXT4 on an Oracle Linux installation. In order to ensure that your installation performs optimally, the /etc/fstab must be edited to provide alternate mount options for the mount point where Oracle VM Manager is installed. Mount options for an EXT4 filesystem should be specified as: rw,noatime,data=writeback,barrier=0,nobh.

Custom Installation (using existing Oracle database)

The Custominstallation option allows you to use an existing local or remote Oracle Database as the Oracle VM Manager database repository. During the Custominstallation process, you need to set the users and passwords to use in order to connect to the database, the SID that should be used within the Oracle Database to load the Oracle VM Manager schema, the username and password to be used for the Oracle WebLogic Server, and the password for the admin user account in Oracle VM Manager. The following example shows the Custominstallation process.

Example 4.2. Custom Installation

# ./runInstaller.sh

Oracle VM Manager Release 3.x.x Installer

Oracle VM Manager Installer log file:

  /tmp/ovm-manager-3-install-date-id.log

Please select an installation type:

1: Simple (includes database)

2: Custom (using existing Oracle database)

3: Uninstall

4: Help

   Select Number (1-4): 2

The installation process starts, and the following is displayed:

Starting production installation ...

Verifying installation prerequisites ...

Oracle Database Repository

==========================

Use an existing Oracle database 

When prompted, enter the following information

Enter the Oracle Database hostname [localhost]:

Enter the Oracle Database System ID (SID) [ORCL]:

Enter the Oracle Database SYSTEM password:

Enter the Oracle Database listener port [1521]: 

Enter the Oracle VM Manager database schema [ovs]:

Enter the Oracle VM Manager database schema password:

Enter the Oracle VM Manager database schema password (confirm):

Oracle Weblogic Server 11g

==========================

Enter the Oracle WebLogic Server 11g user [weblogic]:

Enter the Oracle WebLogic Server 11g user password:

Enter the Oracle WebLogic Server 11g user password (confirm):

Oracle VM Manager application

=============================

Enter the username for the Oracle VM Manager administration user [admin]:

Enter the admin user password:

Enter the admin user password (confirm):

Verifying configuration ...

Start installing the configured components:

   1: Continue

   2: Abort

   Select Number (1-2): 1

You have the option to continue or abort the installation. Enter 1 to continue. You may be prompted again to either abort or continue the installation in case certain components are already present on your system. Progress of the installation is output on your screen step by step, as shown below:

Start installing the configured components:

   1: Continue

   2: Abort

   Select Number (1-2): 1

Step 1 of 9 : Database ...

Installing Database ...

Database installation skipped ...

Step 2 of 9 : Java ...

Installing Java ...

If an existing Oracle VM Manager database schema is found in the database, the following is displayed:

Step 3 of 9 : Database Schema ...

An existing OVM database was found.  How should the install proceed?

   1: Use the existing OVM database

   2: Remove the existing OVM database and create a new OVM database

   3: Abort

   Select Number (1-3): 1

Enter 1 - 3, depending on your requirements. In this example, the existing schema is retained.

Alternatively, if no existing Oracle VM Manager database schema is found in the database, the schema is created.

Step 3 of 9 : Database Schema ...

Creating database schema 'ovs' ...

Step 4 of 9 : WebLogic ...

Retrieving Oracle WebLogic Server 11g ...

Installing Oracle WebLogic Server 11g ...

Step 5 of 9 : ADF ...

Retrieving Oracle Application Development Framework (ADF) ...

Unzipping Oracle ADF ...

Installing Oracle ADF ...

Step 6 of 9 : Oracle VM  ...

Retrieving Oracle VM Manager Application ...

Extracting Oracle VM Manager Application ...

Installing Oracle VM Manager Core ...

Step 7 of 9 : Domain creation ...

Creating Oracle WebLogic Server domain ...

Starting Oracle WebLogic Server 11g ...

Configuring data source 'OVMDS' ...

Creating Oracle VM Manager user 'admin' ...

Step 8 of 9 : Deploy ...

Deploying Oracle VM Manager Core container ...

Deploying Oracle VM Manager UI Console ...

Deploying Oracle VM Manager Help ...

Granting ovm-admin role to user 'admin' ...

Set Log Rotation ...

Disabling HTTP and enabling HTTPS...

Configuring Https Identity and Trust...

Step 9 of 9 : Oracle VM Manager Shell ...

Retrieving Oracle VM Manager Shell & API ...

Extracting Oracle VM Manager Shell & API ...

Installing Oracle VM Manager Shell & API ...

Retrieving Oracle VM Manager Upgrade tool ...

Extracting Oracle VM Manager Upgrade tool ...

Installing Oracle VM Manager Upgrade tool ...

Copying Oracle VM Manager shell to '/usr/bin/ovm_shell.sh' ...

Installing ovm_admin.sh in '/u01/app/oracle/ovm-manager-3/bin' ...

Installing ovm_upgrade.sh in '/u01/app/oracle/ovm-manager-3/bin' ...

Enabling Oracle VM Manager service ...

Shutting down Oracle VM Manager instance ...

Restarting Oracle VM Manager instance ...

Waiting 15 seconds for the application to initialize ...

Oracle VM Manager is running ...

Oracle VM Manager installed.

Please wait while WebLogic configures the applications... This can take up to 5 minutes.

When the installation is complete a summary similar to the following is displayed:

Installation Summary

--------------------

Database configuration:

  Database host name          : localhost

  Database instance name (SID): MYDB

  Database listener port      : 1521

  Application Express port    : 8080

  Oracle VM Manager schema    : ovs

Weblogic Server configuration:

  Administration username     : weblogic

Oracle VM Manager configuration:

  Username                    : admin

  Core management port        : 54321

  UUID                        : 0004fb0000010000cc1b57e39ff77ea9

Passwords:

There are no default passwords for any users. The passwords to use for Oracle VM

Manager, Database, and Oracle WebLogic Server have been set by you

during this installation. In the case of a demo install, all passwords are the

same.

Oracle VM Manager UI:

  https://myserver.example.com:7002/ovm/console

Log in with the user 'admin', and the password you set during the installation.

Please note that you need to install tightvnc-java on this computer to access a virtual

machine's console.

For more information about Oracle Virtualization, please visit:

  http://www.oracle.com/virtualization/

Oracle VM Manager installation complete.

Please remove configuration file /tmp/ovm_configid.

Important

Make sure you delete the temporary configuration file created during the installation:

/tmp/ovm_configid

Performing a Silent Install

The Oracle VM Manager installer can be installed silently, without any intervention. An installation configuration script can be used to provide the installation options, and a set of command line options are available for the installation parameters. The configuration script is written in YAML. Structure is shown through indentation (one or more spaces). Sequence items are denoted by a dash, and key value pairs within a map are separated by a colon. Structure is shown through indentation (one or more spaces) and key value pairs within a map are separated by a colon.

The following example silently performs a Custom install.

Warning

Always provide the absolute path to the configuration file. The installer cannot process a relative path and will simply terminate the installation process.

Example 4.3. Silent install using configuration file

The command to run the silent production installation using a configuration file is:

./runInstaller.sh --config=/path/config.yml --installtype=Custom --assumeyes

The configuration file used in this installation example (config.yml) installs a local MySQL database. Replace the password entry with your own password.

db:

      install       : Yes

      host          : localhost

      sys_password  : password

      port          : 49500

      sid           : ovs

      mgmt_port     : 8080

      user          : ovs

      password      : password

webLogic:

      install       : Yes

      user          : weblogic

      password      : password

java:

      install       : Yes

ADF:

      install       : Yes

OVMCore:

      install        : Yes

      user           : admin

      password       : password

OVMConsole:

      install       : Yes

OVMShell:

      install       : Yes

onFailure:

      cleanup       : No

OVMUpgrade:

      install       : Yes

Configuring the NTP Service

When an Oracle VM Server is discovered in Oracle VM Manager, NTP (Network Time Protocol) is automatically configured and enabled to ensure time synchronization. Oracle VM automatically configures the Oracle VM Manager host computer as the NTP source for all Oracle VM Servers under its control, unless other NTP servers are configured in the user interface or CLI.

If you do not set up your own list of NTP servers, and want to use the Oracle VM Manager host computer to provide NTP time synchronization services, NTP must first be installed and configured on the Oracle VM Manager host server. Make sure that your Oracle VM Manager host is either registered with the Unbreakable Linux Network (ULN) or configured to use Oracle's public YUM service.

To configure NTP on the Oracle VM Manager host:

1. Install the NTP package.

# yum install ntp

When NTP is installed, configure it to both synchronize with upstream servers and provide time services to the local network, where the Oracle VM Servers reside.

2. Enable upstream synchronization by defining the upstream time servers in the ntp.conf file.

Oracle Linux uses three public NTP servers as upstream time sources by default. Check with your network administrator if time services are provided on the corporate network and, if necessary, replace the default entries with the names or IP addresses of your NTP servers.

Use your favorite text editor to modify /etc/ntp.conf. Search for these entries:

# vi /etc/ntp.conf

server 0.rhel.pool.ntp.org

server 1.rhel.pool.ntp.org

server 2.rhel.pool.ntp.org

3. Configure downstream access for the Oracle VM Servers in your local network. To do so, disable the default "noquery" option for the Oracle VM Server management network.

Again in the /etc/ntp.conffile, search for this entry:

#restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

Remove the # character at the start of the line to uncomment this entry. Replace 192.168.1.0 with the network address of your Oracle VM Server management network. You may also need to adjust the netmask (255.255.255.0). Once you have finished editing, save the /etc/ntp.conffile.

4. Start the NTP service and set it to launch automatically upon boot.

5.  # service ntpd start

# chkconfig ntpd on

6. When NTP is running, check upstream synchronization. The ntpq command should output something similar to this example:

7.  # ntpq -p

8.   

9.       remote           refid      st t when poll reach   delay   offset  jitter

10.==============================================================================

11.lists2.luv.asn. 203.161.12.165  16 u   25   64    3    3.495   -3043.1   0.678

12.ns2.novatelbg.n 130.95.179.80   16 u   27   64    3   26.633   -3016.1   0.797

 sp1.mycdn.fr    130.234.255.83  16 u   24   64    3    4.314   -3036.3   1.039

13. Test downstream synchronization from another server in the management network to ensure that NTP services are working. Note that it may take several minutes before your NTP server is able to provide time services to downstream clients. Begin by checking the stratum level of your server:

14.# ntpq -c rv

15. 

16.assID=0 status=c011 sync_alarm, sync_unspec, 1 event, event_restart,

17.version="ntpd 4.2.4p8@1.1612-o Tue Jul  6 21:50:26 UTC 2010 (1)",

18.processor="x86_64", system="Linux/2.6.32-200.19.1.el6uek.x86_64",

19.leap=11,  stratum=16 , precision=-20, rootdelay=0.000,

20.rootdispersion=1.020, peer=0, refid=INIT,

21.reftime=00000000.00000000  Thu, Feb  7 2036 17:28:16.000, poll=6,

22.clock=d21d4a96.a26c5962  Fri, Sep 16 2011 14:09:58.634, state=0,

23.offset=0.000, frequency=0.000, jitter=0.001, noise=0.001,

stability=0.000, tai=0  

If the server is showing stratum=16, wait a few minutes and try again. It may take up to 15 minutes for an NTP server to stabilize sufficiently to lower its stratum level.

Downstream clients will not synchronize with a server at stratum level 16. Once the stratum level has dropped, log in to an available Linux host in your management network, not running Oracle VM Manager, and issue the following command:

# ntpdate -d manager.hostname

[...]

16 Sep 13:58:25 ntpdate[1603]: step time server 192.168.1.1 offset 3.009257 sec

This command runs ntpdate in debug mode, in which case the availability of the remote time server is checked. If the debug run ends in a line similar to the one in this example, the test is successful. In case the stratum level is still too high, the error message "Server dropped: strata too high" is displayed.

When you have confirmed with these tests that NTP is working properly for your environment, you should not need to check this again.

Caution

NTP communicates over UDP port 123. Ensure that no firewall is blocking this traffic.

Installing and Configuring Virtual Machine Console Utilities

There are two types of virtual machine consoles in Oracle VM Manager: the VNC console used to connect virtual machines in x86-based server pools, and the serial console used to connect to virtual machines in both x86-based and SPARC-based server pools. This section discusses installing the prerequisite software and any configuration required to use both console types.

Oracle VM Server VNC Console for x86

Oracle VM Manager uses a secure tunnel to protect the virtual machine console (remote connection utility) data across the network. Oracle VM Manager does not communicate directly with the VNC client, but rather connects via an SSH-encrypted tunnel on port 69xx (where xx is based on the guest to which it is connecting).

Any firewall between the client and Oracle VM Manager needs port 15901 to be open. Any firewall between the Oracle VM Manager and the Oracle VM Servers needs ports 6900 and above open; one port for each virtual machine on an Oracle VM Server. For example, if you have 100 virtual machines on an Oracle VM Server, you should open ports 6900-6999 (100 ports) on any firewall between the Oracle VM Server and Oracle VM Manager.

To connect to a virtual machine's VNC console in Oracle VM Manager, you should have a VNC viewer installed somewhere in your environment, either:

• On the Oracle VM Manager host computer
• On the client computer
• On both the Oracle VM Manager host computer and the client computer

The virtual machine VNC console feature uses the client instance of a VNC viewer, if one exists, to connect to a virtual machine's console. If a VNC viewer is not found on the client computer, a request is sent to the Oracle VM Manager host computer to display the VNC viewer.

It is preferred that you install TightVNC on the Oracle VM Manager host computer. You can get the latest TightVNC package from:

http://oss.oracle.com/oraclevm/manager/RPMS/

Install TightVNC with the command:

# rpm -ivh tightvnc-java-version.noarch.rpm

Packages are also available at Oracle's public YUM repository:

• TightVNC (Oracle Linux 5): http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/x86_64/tightvnc-java-1.3.9-4.noarch.rpm
• TightVNC (Oracle Linux 6): http://public-yum.oracle.com/repo/OracleLinux/OL6/addons/x86_64/tightvnc-java-1.3.9-4.noarch.rpm

On the client computer you use to connect to Oracle VM Manager it is recommended that you install RealVNC. Oracle recommends RealVNC on the client computer as it renders quickly, has better keyboard support, and has less mouse control issues compared to other VNC clients. The RAS proxy applet used to view the screen or console of a virtual machine looks for RealVNC by default. If you have multiple VNC viewers on your client computer, you can configure which one is used from the virtual machine console in Oracle VM Manager. See Connecting to a Virtual Machine for more information on using and configuring the VNC client.

If you are using a Linux-based operating system on your client computer, you can also install TightVNC as above on your client computer and it is automatically discovered when you connect to a virtual machine using the console feature in Oracle VM Manager.

Oracle VM Server Serial Console for x86 and SPARC

You cannot use the standard VNC console to connect to virtual machines on a SPARC-based server pool. Instead, use the serial console. The serial console can also be used to connect to virtual machines running on x86-based server pools. The serial console behaves differently to the VNC-based x86 console, and the console must be displayed using the Java Telnet Application (JTA2) package installed on the Oracle VM Manager host computer. You can get the latest JTA2 package from:

http://oss.oracle.com/oraclevm/manager/RPMS/

Install JTA2 with the command:

# rpm -ivh jta-version.noarch.rpm

Packages are also available at Oracle's public yum server:

• JTA (Oracle Linux 5): http://public-yum.oracle.com/repo/EnterpriseLinux/EL5/addons/x86_64/jta-2.6-1.noarch.rpm
• JTA (Oracle Linux 6): http://public-yum.oracle.com/repo/OracleLinux/OL6/addons/x86_64/jta-2.6-1.noarch.rpm

See Connecting to a Virtual Machine for more information on using the serial console to connect to virtual machines in SPARC-based server pools.

Installation Logs

If any errors occur during installation, check the Oracle VM Manager installation log file:

/tmp/ovmm-installer.selfextract_id/ovm-manager-3-install-date.log

When the installation is complete, the installation log is copied to:

/tmp/ovm-manager-3-install-date.log

Installation Directories

The locations of the Oracle VM Manager components are listed below.

Component

Location

MySQL	/u01/app/oracle/mysql/data
MySQL Enterprise Backup	/opt/mysql/meb-3.8/ Backups stored in: /u01/app/oracle/mysql/dbbackup
Java	/u01/app/oracle/java
Oracle WebLogic Server 11g	/u01/app/oracle/Middleware/
Oracle ADF	/u01/app/oracle/Middleware/
Oracle VM Manager application	/u01/app/oracle/ovm-manager-3/
Oracle WebLogic Server domain	/u01/app/oracle/ovm-manager-3/machine1/base_adf_domain