Subscribe

Upgrading from 3.2 to 3.7.1 - Part 2

Hello everyone ... here is part 2 and it failed :-(

We thought we had an upgrade working but the new OM instance started complaing that the database is not to the correct schema level.  I have attached some sample output we have tried.  I will get more into in the next several days, currently customer is back to running on 3.2

BACKGROUND

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

The new OM host is a VM system with two "harddrives" - a C: and a D: ( C: is nearly full ), so OM was installed on D:

We copied the monitor db and log file from old server and copied it to the new server with 3.2 installed.  It picked up the database and started working with it, everything looked good.  So we installed 3.7.1 on top of it and after a couple of hours processing, it was working fine.  Then after less than 24 hours, the database stop working ( we would have to consult with log files ).  As we attempted to restart the database, it complained it was not upgraded correctly, please try again.  Here we go

We attempted to upgrade the database and ran into the problem with "C:\Program Files....".  We searched the entire options list, looking for "C:\" instances and changed the "perfArchiveDir".  Other than this one option, all paths pointed to D:\ ... what is odd that some of the option paths show a "/" and a "\"; Windows only recognizes the "\" for directory paths.

D:\Program Files\Network Appliance\DataFabric\DFM\bin>dfm options set perfArchiv
eDir="D:/Program Files/Network Appliance/DataFabric/DFM/perfdata/"
Error: perfArchiveDir: Path must be absolute.

D:\Program Files\Network Appliance\DataFabric\DFM\bin>dfm options set perfArchiv
eDir="D:\Program Files\Network Appliance\DataFabric\DFM\perfdata"
Changed performance advisor archive directory to D:\Program Files\Network Applia
nce\DataFabric\DFM\perfdata.
You must now start the server service:

        dfm service start server

NOTE: You must first move all of the perf data to the new directory,
         BEFORE starting the server, otherwise the perf data will be lost.



D:\Program Files\Network Appliance\DataFabric\DFM\bin>dfm upgrade

Depending on the size of the monitored network and the age of the
DataFabric Manager installation, this command may take between
many minutes and several hours to complete.
Please be patient...

Stopping services before upgrade...
Restarting the DataFabric Manager Database service in bulk update mode...
Executing post database upgrade logic.
Removing defunct counter groups.
Initializing new counter groups.
open failed No such file or directory
Failed to create C:\Program Files\Network Appliance\DataFabric\DFM\perfdata\perf

_16_45_0
can't get handle to clog file 'perf_16_45_0'.
could not obtain lock on counter group vFiler Basic, for host apollo.na.gilead.c
om.
Failed to execute post db upgrade logic: Initializing new counter groups.
Failed to execute post db upgrade logic.
Error: Access Violation
The instruction at 0x0054147d tried to read memory at 0x00000020.
Unable to free SQL environment.

We also attempted a proper backup and restore operation.  We switched on the old host and used the DFM BACKUP CREATE command from 3.2 and it produced a backup file called flcdfm01old.bak.zip.  We copied it to the new server and attempted a restore and it failed ( the spaces you see in the command line are the result of a word wrap ).

D:\Program Files\Network Appliance\DataFabric\DFM\bin>dfm backup restore -k f:\f cdfm01old.bak.zip Please do not interrupt this operation with CTRL-C.

Previous database upgrade did not succeed.

Restore database from a good backup copy or run 'dfm upgrade' command again.

Error: Unable to start service eventd as database schema is not up to date.

Error: Failed to start service: eventd

Error: Unable to start service monitor as database schema is not up to date.

Error: Failed to start service: monitor

Error: Unable to start service scheduler as database schema is not up to date.

Error: Failed to start service: scheduler

Previous database upgrade did not succeed.

Restore database from a good backup copy or run 'dfm upgrade' command again.

Error: Could not create directory C:\Program Files\Network Appliance\DataFabric\ DFM\perfdata.

Error: Could not rename all restore targets.

Restore operation failed, reverting...  rollback succeeded.

D:\Program Files\Network Appliance\DataFabric\DFM\bin>



Re: Upgrading from 3.2 to 3.7.1 - Part 2

Just copying the monitordb and log files is not sufficient, you need to

copy the perfdata as well to the new install.

However, recommended way is to use proper backup created by "dfm backup"

command. Proper backup that you had should have got restored without

issues. Restore takes care of upgrading as well.

I think it would be better to open a case with NGS to resolve this.

-Ravindra

Re: Upgrading from 3.2 to 3.7.1 - Part 2

I agree with Ravindra that opening a support case, and uploading the database backup would be better.

In the mean time, if you would like to try - i have one comment:

Looks like the restore operation was tried on the setup where the first upgrade failed. Since the 'dfm upgrade' command crashed in the middle, it could have some left over files/folders.

You should uninstall DFM, remove the installation folder (D:\Program Files\Network Appliance\DataFabric\) and then try the 'dfm backup restore' on a
fresh installation of 3.7.1.

Thanks,

Raj.

Re: Upgrading from 3.2 to 3.7.1 - Part 2

Hello Ravindr, Raja, and others

I am passing along the advice to install a new copy of DFM, since these are VM hosts, it is easy to create a new VM for this purpose.  This also opens up a couple of more questions.

1 ..  They deploy a standard set of VMware machines, in this case two virtual drives ( C: for the OS and a D: for data and apps ).  My question is ... it should be okay to install a copy of DFM 3.7.1 on the D: and restore a backup copy of a 3.2 DFM database that lived on a C: previously.  When we perform this new backup and restore using the DFM commands, we should not have any problems with which harddrive the application or database will be put on.

2 .. Because the versions of DFM are far between, the command syntax for executing the backup should be as follows?

- DFM3.2Host> dfm backup create <filename> <path>

- DFM3.2Host> dfm backup create dfmdatabase32 c:\temp

Does the 3.2 backup create command create a single file or a group of files?

copy the dfmdatabase32 file / archive to new server, then

- DFM371Host> dfm backup restore <path> <filename>

- DFM371Host> dfm backup restore d:\temp dfmdatabase32

Thanks for your help, Emanuel