Migrating the SGD ENS Datastore

If you read the previous blogs about using the command line, you may think that by using the "tarantella object list_contents" and "tarantella object list_attributes" commands then you can simply walk the ENS datastore tree and archive the contents. And then use the "tarantella object new" commands to import them into a new SGD server. Well, you could but here's another way:

Stop the SGD server

# tarantella stop; sleep 30; tarantella stop --kill

Create an archive of the desired ENS.
```
# cd /<install-dir>/var
```
Note: <install-dir> Is a placeholder, indicating the installation directory. The default for SGD is /opt/tarantella. CPIO implementations differ based upon version and platform. Below are two example commands. Please choose the one most appropriate with your environment, and verify correctness via man page.
```
  LINUX   # find ens | cpio -ocv -C 1024 -F /tmp/sgd_ens.cpio
  Solaris # find ens | cpio -ocv -C 1024 -O /tmp/sgd_ens.cpio
```
This file, '/tmp/sgd_ens.cpio' may now be copied to the target server that you'd like to restore it on.
If you are planning to restore or migrate this ENS over a 'fresh' SGD install that maintains the default application objects, it may be beneficial to save the existing DNS for future troubleshooting. To do so:
```
          # cd <install-dir>/var
          # mv ens ens.<SGD version>.default
```
With the original ENS archived, and the SGD server stopped, you will now want to restore the archive in the same <install dir>/var/ directory
```
          # cd <install-dir>/var 
```
```
  LINUX   # cpio -icdumv < /tmp/sgd_ens.cpio
  Solaris # cpio -icdumv < /tmp/sgd_ens.cpio
```
Once the transplanted ENS has been restored on the server, it is necessary to remove ens/.object file. This forces SGD to 'reindex' the ENS on it's next startup.
```
    # rm <install dir>/var/ens/.object 
```
Start the server:
```
          # tarantella start
```

It may be useful to someone.

-FB

Comments:

If I read this correct this only will work when performed on the same system. For example a migrating the objects from an SSGD version to a minor version updated SSGD version. Or after a reinstall of SSGD. Can this also be used to 'copy' the objects from one system to an other? Does this also work for a mayor version update? BTW I am sure this post will be usefull :)

Posted by Remold Krol on July 13, 2007 at 01:39 PM BST #

Although not formally supported, this procedure has been used for many years by the Tarantella and SGD support teams to assist customers working to migrate from complicated environments, with a long track record of success. This is particularly useful for environments where there is *not* a supported upgrade path from an existing installation, as might occur when the deployment platform has been deprecated from the 'supported hosts' list, or the entire deployment is moving to new hardware, kernels, and environments. Still: Use with caution, and verify there are no reports of ENS corruption or object errors before deploying in a production environment.

Posted by Fat Bloke on July 13, 2007 at 03:07 PM BST #

The Fat Bloke Sings: Thoughts from a Fat Bloke

About this weblog

Your Current Location

Up to 10 Recent Entries

Feeds

Categories

Other Blog Features

Search

Bookmarks