Upgrading the sdb.db to a newer AppGate version.

Description:

The normal pocedure for upgrades it to apply an AppGate Upgrade (.agu) file. The upgrade will take care of upgrading the content of the sdb.db file. Another approach to upgrades is to implement a totally new and parallell system and migrate users. A problem with this approach that your sdb.db file will not be handled for you automatically, and you can not simply coopy it from an old system to a new.

The solution is to copy sdb.db and convert it using the agdbconvert program on the new AppGate system.

Copy the sdb.db

Use the AppGate Console -> System settings -> File transfer to copy the file /var/opt/appgate/database/sdb.db from old system. Use another console on the new system and copy it to /tmp

Conversion and activation

Start a terminal window on the new system, become root and do as follows:

# cd /tmp
# agdbconvert -i sdb.db -o sdb.db.converted

Before activation of the new sdb.db you should make a copy of the original and working one, in case there is a problem.

# cd /var/opt/appgate/database
# cp sdb.db sdb.db.orig

Activation of the new is done simply by moving it into place. The AppGate system will detect that there is a new sdb.db file and will try to reload it. Use the logcat -f to get a continous log and wait for the automatic reload.

# cp /tmp/sdb.db.converted sdb.db
# logcat -f

In 5-15 seconds the reload should take place and you should watch the log for a success or fail message. If it succeed you are done. If it failed it will normally tell you what was wrong with the new file. You may attempt to fix it by a manual edit on the file or you may revert to the working sdb.db.orig.