Upgrading to 1.7 from 1.6.5.4

Upgrade instructions are in the release notes: http://www.couchbase.org/wiki/display/membase/Membase+Server+1.7

That should preserve all the buckets and data on a node.

Let us know if you have issues after following the instructions.

Cheers,

Frank

Frank, thank you I visited the link you referenced and followed the upgrade steps on another dev machine running membase server 1.6.5.

1. Downloaded membase-server-community_x86_64_1.7.0.setup.exe
2. Turned off all applications that use Membase.
3. Ensured the Disk Write Queue size was 0.
4. On my single node, I ran mbbackup and copied each membase bucket into a backup folder. Also copied the config.dat file into the same folder.
5. Ran membase-server-community_x86_64_1.7.0.setup.exe

As the help document you referenced states in step 5: "The previous upgrade command will stop membase, install 1.7.0, upgrade configuration files and data records, uninstall the previous version, and restart the membase server."

The setup mentioned that it would do these things, so I proceeded.

Install was going smoothly when the message: "Cannot open dbdir file for reading" appeared. I clicked OK (that's all I could do). The install proceeded until completion.

At completion the installation opened the localhost:8091 site with the page stating: "CONGRATULATIONS You have successfully installed the Membase Server. This wizard will help you configure your cluster."

This is the point where I wonder if the upgrade was successful because clicking 'setup' takes me to the Configure Server window where it gives me the choice to start a new cluster or join a cluster now. I would think, if the upgrade was successful, I would not get this page, but be taken to the normal Membase page where I can view and manage my existing buckets.

Perusing the C:\Program Files\Membase\Server directory, the data\ns_1 directory is empty. There is not config directory as there was previously. There is a 'var\lib\membase directory containing my previous data files, a config directory with the config.dat, a data, logs, mnesia and tmp directory. Are these my previous files? Do I need to move/copy them elsewhere in order for Membase 1.7 to recognize that I have a previous cluster (single) set up on this machine?

Can I restore the backup I made before the 1.7 upgrade somehow?

Your help would be much appreciated. Thank you.

Yeah, having the upgrade go back to the initial configuration congratulations screen is not expected.

You should be able to restore the backup -- just reinstall, configure a bucket the same way you had before, and use mbrestore.

But, if I might ask you for a few things to help debug this -- can you provide any config.dat files that you find so that we can take a look and see what the root cause might be?

Thanks,
Steve

At the moment you see the pop up, you can copy back all your backup data file to old data directory, and click ok to proceed.

Or at the moment, run the following command under the membase bin directory:
mbupgrade.exe -c backup_directory_that_contains_config.dat -d myoutput.txt

Frank, another detail that I think may point to what is causing the issue, at least on my local dev machine.

After the problem described above, I unstalled version 1.7 and reinstalled 1.6.5.4.

I then stopped the service, copied the config.dat file and the data files back into their proper places from the backup I had performed earlier.

I then restarted the membase service and opened localhost:8091. I was greeted once again with the Congratulations screen. I checked the data\ns_1 folder only to find it empty! The data files that I had copied there previously were now missing.

That got me thinking.. I know that it's important that the IP address of the machine being restored on must be identical to the ip address of the original machine. And as I recalled, because of issues with developing on a machine with a non static ip address (DHCP) I had previously unregistered and re-registered membase to the ip address 127.0.0.1.

So, I performed the re-registering steps again (127.0.0.1) and copied the backup files back to their original places again and restarted Membase. Sure enough, the buckets had been restored and membase was back to normal.

So, what I am guessing is that during the setup process for membase 1.7, there is an issue with restoring the config and data files because the new (1.7) install is registered with the machines local ip address by default instead of 127.0.0.1.

Hopefully that gives you some insight as to how I can upgrade (on my dev machine) from version 1.6.5.4 to 1.7 when I have membase registered to 127.0.0.1 instead of the machines local IP address.

p.s. Because the servers in our production environment have static IPs, membase is registered to those IPs, so I do not believe that the same installation/upgrade problem with 1.7 will surface there. What do you think?

Hi,
Yep, having stable IP's during the upgrade should do the trick and I also see Farshid's added this to jira...

http://www.couchbase.org/issues/browse/MB-4022

Cheers,
Steve