Eighty per cent of all business data is stored on computers.

For a fixed monthly fee we can protect yours.
Securely - Simply. Affordably.

All backup files are compressed and encrypted before uploading to the Backup Server, the average compression ratio for text-based files is around 4:1. However, no further compression can be made on files that are already in compressed format (e.g. JPG, ZIP). In general, you can assume a 2:1 compression ratio when you are backing up a file set with a variety of file types.

TOP

The Online Backup Suite consists of 3 main modules:

• 1. The client software – Online Backup Manager (OBM)
• 2. The server software – Offsite Backup Server (OBS)
• 3. The replication server – Replication Server (RPS)

OBM is a client application with a user-interface for easy backup configuration. It allows users to upload selected files to the Backup Server and runs scheduled backup jobs. It also allows users to create different backup sets for different backup purpose. Besides file backup, OBM can backup a list of applications such as MS Exchange, MS SQL, Oracle, MySQL, Lotus Domino, and much more. OBM supports Windows 2000, XP, 2003, Linux, Mac OS X, etc. It is this software that users install on their own compyuters and servers.

OBS is a server application which store backup data from multiple OBMs backup accounts. It has a web-based Management Console for system administrators to manage the Backup Server, such as configuring system and backup account settings, and viewing backup statistics and reports. Users can also logon to this Management Console to manage their own backup account or restore their own backup data. OBS supports Windows, Linux and Mac OS platforms.

RPS is another server application running on a separate machine, it provides close to real-time backup for multiple OBSs. So even if one of the OBS failed, the RPS still has a copy of the backup data.

TOP

Try manually installing OBM on your Mac with the following instructions:

• 1. Download http://download.ahsay.com/support/obm50-mac.zip
• 2. Expand obm50-mac.zip into /Applications/OBM
• 3. Run "chmod -R 755 /Applications/OBM" using Terminal
• 4. Double-click the “Online Backup Manager” icon in /Applications/OBM folder

TOP

To manually install OBM on Windows, you’ll need to copy and zipping the program directory (e.g. C:\Program Files\OBM) from another machine with OBM installed. Then do the followings on the machine you wish to manually install:

• 1. Create the directory C:\Program Files\OBM
• 2. Unzip the OBM program directory archive to C:\Program Files\OBM
• 3. Run C:\Program Files\OBM\bin\install.bat
• 4. Run C:\Program Files\OBM\bin\Install-Scheduler.bat

TOP

Please do the followings to install OBM on SCO:

• 1. Install Java 1.4.x or above onto your SCO Unix box
• 2. Download obm-linux.tar.gz and expand it to $OBM_HOME (e.g. /usr/local/obm)
• 3. Delete $OBM_HOME/jvm and create a symbolic link from $OBM_HOME/jvm to the SCO Unix Java VM
• 4. Run $OBM_HOME/bin/BackupManager.sh to setup your backup set (or run $OBM_HOME/bin/Configurator.sh if you are under command line mode. Then use the OBS Management Console to setup your backup sources and other settings)
• 5. Run $OBM_HOME/bin/RunBackupSet.sh [BACKUP_SET_NAME] to run your backup
• 6. Run $OBM_HOME/bin/Scheduler.sh to start the backup scheduler

TOP

There are few things that could create errors during or after executing the installer.

• 1. Make sure there is enough disk space on the machine.
• 2. Make sure you do not have any anti virus software or PCanywhere running, as this may create problems with InstallAnywhere installers.
• 3. There are also problems with InstallAnywhere installers and Dell OpenManager. If OpenManager has installed on the target system, be sure to disable it before installing OBM.
• 4. Hardware could cause errors as well, try set your [hardware acceleration display setting] to off. There are problems with certain versions of Java running along with certain video cards.
• 5. This may only be a Java problem.

Also, if you are transferring this file from one machine to another, please be sure the file size is valid and you are transferring the file in binary mode.

Java Testing

Please try running any of the Swing demos that came with the Java runtime in 1.4.X and see if it hangs on Windows. In order to fix this problem, some knowledge base on the Internet suggested updating DirectX to at least DirectX 8.1. Most machines got this problem had DirectX 7.0 installed. (You can use the “dxdiag” command to find out the directX version)

SUN recommended two workarounds for certain video card issues

• 1. The following will pass properties to the installer's Virtual Machine: In Advanced Designer – Project -> Config -> Additional Arguments set that to "-Dsun.java2d.d3d=false -Dsun.java2d.noddraw=true" without the quotes.
• 2. Set the following lax property in your LaunchAnywhere for your application's JVM: lax.nl.java.option.additional=-Dsun.java2d.d3d=false -Dsun.java2d.noddraw=true

Add the same line to the uninstaller lax file, using a modify file action in your installer in post-install.

TOP

The encrypting key cannot be changed once you setup your Backup Set. This is necessary for the integrity of the Backup Set, making sure that backup data is only encrypted by one key. Otherwise, you will have problems remember two encrypting keys when you want to restore your files in the future.

You need to recreate your Backup Set if you really want to change your encrypting key.

Equally make sure you keep a record of your Encryrtion Key. Without it you will NOT be able to restore your data.

TOP

There are two encryptions being performed by OBM:

• 1. Encryption of backup data - This is being done by 128-bit symmetric key encryption (AES, TripleDES, TwoFish). 256-bit is not available because it requires too much CPU and it is not really required. (128-bit is currently being used by most banks)
• 2. Encryption of backup traffic - This is being done by 1024 bit RSA public key encryption. The strength of the encryption depends on the key size you use when you generate your CSR before submitting to your CA. 1024 bit is what is being used by most CAs.

TOP

By selecting the “User Login Password as Encrypting Key” option when creating a backup set, OBM will set your login password as the encrypting key for the backup set. Once set, even if you change your login password afterward, the encrypting key will remain as your original password. In other words, if you have changed your login password, you still need to use the original password to decrypt and restore the backup set.

If the encrypting key is forgotten or lost, the backup set can never be restored. It is not possible to restore without the key.

You can find out the encrypting key from the corresponding OBM, please refer to EncryptingKey.jpg

TOP

Please do the followings to install OBM on AIX:

• 1. Install Java 1.3.x or above (Java 1.4.2 or above recommended) onto your AIX box
• 2. Download obm-linux.tar.gz and expand it to $OBM_HOME (e.g. /usr/local/obm)
• 3. Delete $OBM_HOME/jvm and create a symbolic link from $OBM_HOME/jvm to the AIX Java VM
• 4. Run $OBM_HOME/bin/BackupManager.sh to setup your backup set (or run $OBM_HOME/bin/Configurator.sh if you are under command line mode. Then use the web interface to setup your backup sources and other settings)
• 5. Run $OBM_HOME/bin/RunBackupSet.sh [BACKUP_SET_NAME] to run your backup
• 6. Run $OBM_HOME/bin/Scheduler.sh to start the backup scheduler

TOP

You can either run OBM on a Linux version of Sun Java JDK (performance might not be optimized) or on a FreeBSD native Java SDK.

Please do the following for the Linux version of Sun Java JDK option:

• 1. Install Linux binary compatible port to the FreeBSD machine
• 2. Install the Linux version of Sun Java 1.4.2 or above JDK onto the FreeBSD machine
• 3. Create a symbolic link from $OBM_HOME/jvm to $JAVA_HOME (installed in previous step)
• 4. Run $OBM_HOME/bin/RunBackupSet.sh [BACKUP_SET_NAME] to run your backup
• 5. Run $OBM_HOME/bin/Scheduler.sh to start the backup scheduler

Please do the following for the FreeBSD native Java SDK option:

• 1. Install Linux binary compatible port to the FreeBSD machine
• 2. Install the Linux version of Sun Java 1.4.2 or above JDK onto the FreeBSD machine
• 3. Compile the FreeBSD native Java 1.4.2 SDK using the JDK compiler installed in the previous step
• 4. Install the FreeBSD native Java 1.4.2 SDK onto the FreeBSD machine
• 5. Create a symbolic link from $OBM_HOME/jvm to $JAVA_HOME (installed in previous step)
• 6. Run $OBM_HOME/bin/RunBackupSet.sh [BACKUP_SET_NAME] to run your backup
• 7. Run $OBM_HOME/bin/Scheduler.sh to start the backup scheduler

TOP

To connect OBM to OBS through Microsoft ISA Server, please do the following to enable [Web Proxy] service on the ISA Server:

• 1. Open [Start] -> [Programs] -> [Microsoft ISA Server] -> [ISA Server Management]
• 2. On the left panel, select [Microsoft Internet Security and Acceleration Server] -> [SERVER] -> [Configuration] -> [Networks]
• 3. On the top menu, select [Action] -> [New] -> [Network]. Enter a “Network Name” (e.g. Internal) and define the IP address range for your internal network (e.g. 192.168.1.0 - 192.168.1.255)
• 4. Double click the new network that should now be added to on the bottom panel
• 5. Select the [Web Proxy] tab
• 6. Check both [Enable Web Proxy clients] and [Enable HTTP] checkboxes and choose a [HTTP port] for the web proxy service
• 7. (Optional) Press the [Authentication] button, check the [Basic] checkbox and the [Require all users to authenticate] checkboxes if you want to enable and enforce proxy authentication
• 8. Press the [OK] button to make the changes and press the [Apply] button to apply the changes
• 9. Open [Online Backup Manager] from the system tray and press the [Options] button
• 10. In the [Proxy Seting] section, select the [Proxy] radio button
• 11. Enter the hostname/IP address of the ISA server in the [Proxy Address] text field and the TCP port for web proxy service on your ISA Server in the [Port] text field
• 12. Press the [OK] button to connect to the server

If you run into any problems connecting to the OBS from OBM using ISA Server, please do the following to check if your request is being blocked:

• 1. On the left panel of [ISA Server Management], select [Microsoft Internet Security and Acceleration Server] -> [SERVER] -> [Monitoring]
• 2. Then select the [Logging] tab that appears on the right panel3. Click the [Edit Filter] link and create a filter with the following values:
  • ? [Log Record Type] equals [Web Proxy Filter]
  • ? [Destination IP] equals [The IP address of Offsite Backup Server]
• 3. Press the [Start Query] button
• 4. Open [Online Backup Manager] again and try connecting to the OBS using the same procedure above.

Check if there are any errors generated in the log table.

TOP