Feb 22

Restore OVM 3.x Manager with MySQL database

Mount OVM Manager CD
Run the runInstaller.sh -u {UID of OLD Manager}

Restoring the MySQL Database for Oracle VM Manager

To restore the database to one of the available backups, the manager and the database need to shutdown, for example as the root user execute the following commands:

# service ovmm stop; service ovmm_mysql stop
To initiate the restore, as the oracle user, use the RestoreDatabase.sh command located in the /u01/app/oracle/ovm-manager-3/ovm_shell/tools, for example:

# su – oracle
$ bash /u01/app/oracle/ovm-manager-3/ovm_shell/tools/RestoreDatabase.sh
AutoFullBackup-10222012_162543
INFO: Expanding the backup image…
INFO: Applying logs to the backup snapshot…
INFO: Restoring the backup…
INFO: Success – Done!
INFO: Log of operations performed is available at:
/u01/app/oracle/mysql/dbbackup/AutoFullBackup-10172012_122920/Restore.log

IMPORTANT:

As ‘root’, please start the OVM Manager database and application using:
service ovmm_mysql start; service ovmm start

The RestoreDatabase.sh script expects the name of the directory for a particular backup directory. You do not need to specify the full path to the backup directory as this is already specified in the DBBACKUP variable.

Once you have restored the database, restart the database and manager as the root user:

# service ovmm_mysql start; service ovmm start

IMPORTANT:

Make sure your time is correct! I spent 2 hours troubleshooting login issues to new environment and it was the TIME@@!@!!!!!

 

Feb 20

Install VMWare Workstation on Fedora 20 64bit 

There was a problem compiling the modules for VMWare Workstation to work on Fedora 20. Turns out there was / is a bug with netfilter.

From https://wiki.archlinux.org/index.php/VMware

$ curl http://pastie.org/pastes/8672356/download -o /tmp/vmware-netfilter.patch
$ cd /usr/lib/vmware/modules/source
# tar -xvf vmnet.tar
# patch -p0 -i /tmp/vmware-netfilter.patch
# tar -cf vmnet.tar vmnet-only
# rm -r vmnet-only
# vmware-modconfig --console --install-all

Feb 20

VirtualBox install on Fedora 20 64bit

Since I always forget the details, here is how to install VirtualBox on Fedora 64bit

  • Download and install VirtualBox
  • Install the following required packages for /etc/init.d/vboxdrv to setup correctly
    • yum install kernel-headers kernel-devel dkms
  • Next run the /etc/init.d/vboxdrv setup
  • You should see the following output

/etc/init.d/vboxdrv setup
Stopping VirtualBox kernel modules [ OK ]
Uninstalling old VirtualBox DKMS kernel modules [ OK ]
Trying to register the VirtualBox kernel modules using DKMS[ OK ]
Starting VirtualBox kernel modules [ OK ]

 

start Virtualbox

Feb 17

OVM 3 Mass Upgrade

Doing a mass upgrade on OVM 3.1.1 using Cisco UCS Manager. 10 servers at a time!

ovm 3, upgrade

Feb 04

Weblogic startup scripts using “UpStart”

I previously wrote on how to create weblogic startup scripts using standard init.d scripting. There is an even easier way to do things now. Why not use upstart, which is an event based replacement for the /sbin/init daemon.

Simply create a file “wlnode.conf” and put it in the /etc/init directory. This will start the Weblogic Nodemanager. You will need to modify based on your installation of course.

1st Weblogic Server

/etc/init/wlnode.conf

start on runlevel [345]
# console output
exec /bin/su - oracle -- /u01/app/oracle/middleware/user_projects/domains/DEV_domain/bin/startWebLogic.sh

Now you want the Weblogic Admin to start as well? Create a file called wladmin.conf

/etc/init/wladmin.conf

start on runlevel [345]
# console output
exec /bin/su - oracle -- /u01/app/oracle/middleware/user_projects/domains/DEV_domain/bin/startWebLogic.sh

Do you have any instances? You can start them too. Create a file called wlinstance1.conf

/etc/init/wlinstance1.conf

start on runlevel [345]
exec /bin/su - oracle -- /u01/app/oracle/middleware/user_projects/domains/DEV_domain/bin/startManagedWebLogic.sh instance1

To start and stop and find status, simply run “start wlnode”, “stop wlnode” and “status wlnode” using whatever you named your config file in /etc/init.

If you have a cluster setup, then you need to make sure the node manager is running and configured correctly on the second server. Once that is setup, you can add the following Upstart config files to bring everything up.

Second Weblogic Server

/etc/init/wlnode.conf

start on runlevel [345]
# console output
exec /bin/su - oracle -- /u01/app/oracle/middleware/user_projects/domains/DEV_domain/bin/startWebLogic.sh

/etc/init/wlinstance2.conf

start on runlevel [345]
exec /bin/su - oracle -- /u01/app/oracle/middleware/user_projects/domains/DEV_domain/bin/startManagedWebLogic.sh instance2 http://centos.my.lan:7001

This is just a quick example and much more can be done using UpStart!