Disaster Recovery Options

If we have a situation with our data synchronizer server and it is down or unuseable.
1. Can we bring up a new Suse 11 sp2 server.
2. Patch it to the latest versions.
3. Change the IP and name to be as the OLD server was.
4. Install Datasychronizer and configure as a new install, but matching settings from the old original server.
5. Put the same certificates (Mobility.pem and server.pem to /var/lib/datasync/webadmin/ and /var/lib/datasync/webadmin/webadmin/)
6. Configure the new server to see the LDAP Group that has the members we want that server to host.

I am assuming at this point the Datasynchronizer server will populate the databases with email and the devices will still be pointing the old server (name and IP) and certs.
And after a period of time everything will build and the devices will pick up the messages as it builds.
Except for the Downtime to build the server and the time to build the users messages and appointments the user would be unaware of anything.

Can someone evaluate my potential DR strategy and let me know of any potential oversights?
  • Hi
    Your approach basically works, however there is one caveat to this.
    With ActiveSync the device maintains a one to one relationship with the server account and the state. Means the device expects the account to be in a certain state.
    If you reinstall (the same also happens if you re-initialize an account btw.) then we have seen some Android devices choking on this. iOS generally has no problem and simply does a full resync.
    For the Android devices the user needs to remove and re-add the account on the device.
    - Kai
  • Very good article here on backing up datasync: https://www.novell.com/documentation/datasynchronizer1/datasync1_admin/?page=/documentation/datasynchronizer1/datasync1_admin/data/bqtk8ri.html

    Based on the above I wrote a script to automate the backups that runs nightly hope it will help:

    #!/bin/bash
    # back up Novell Synchronizer system
    # this file was based on instructions from Novell:
    # Novell Doc: Novell Data Synchronizer System Administration Guide - Backing Up Your Synchronizer System
    # Look up pg_dump documentation for pw info
    # This started with the simple commands to backup the database and files for DataSync
    # It will now back up the files that Novell says you need to as well as dumping the DB
    # from postgres.
    # I have also added a dated folder to back the files up to and a clean up line
    # that will remove anything older than 7 days at the end (this retention can be changed
    # by changing the number in the find cmd at the end of the file)
    # Set the variable BACKLOC accordingly and you should be all set.
    # CG Jan21/2013

    FOLDATE=`date %m-%d` #Date in MM-DD format for folder naming
    DUMP=/usr/bin/pg_dump
    ZIP=/usr/bin/bzip2
    BACKLOC="/where_you_want_the_backups_to_go/" #Change this variable to adjust the folder for backup
    FULLPATH="$BACKLOC$FOLDATE"
    TAR=/bin/tar
    CP=/bin/cp
    FIND=/usr/bin/find
    USERNAME=datasync_user
    #Create the current backup directory
    /bin/mkdir $BACKLOC$FOLDATE

    # Dump and BZIP the postgres SQL databases, put them into the BACKLOC folder
    $DUMP -U $USERNAME mobility > $FULLPATH/mobility.out
    $DUMP -U $USERNAME datasync > $FULLPATH/datasync.out
    $ZIP $FULLPATH/mobility.out
    $ZIP $FULLPATH/datasync.out

    # Tar and GZ the files NOVELL says to back up for the synchronizer
    $TAR -czvpf $FULLPATH/vardatasync.tgz /var/lib/datasync
    $TAR -czvpf $FULLPATH/optdatasync.tgz /opt/novell/datasync
    $TAR -czvpf $FULLPATH/etcdatasync.tgz /etc/datasync

    # This will clean up the backups, default is 6 which means you will always have 7 days of backups in the BACKLOC
    $FIND $BACKLOC -maxdepth 1 -mtime 6 -exec /bin/rm -rf {} ';'

    echo "Backup Completed at `date`"