The manual for our software can be downloaded here:
Where can I find the log files on a client machine
Windows 2000, XP, 2003:
- C:\Documents and Settings\Administrator\.obm\log
- C:\Program Files\GBDataOBM\log
- C:\Program Files\GBDataOBM\AUA\log
- C:\Documents and Settings\All Users\Application Data\GBDataOBM\CDP\log
Windows Vista:
- C:\Users\Administrator\.obm\log
- C:\Program Files\GBDataOBM\log
- C:\Program Files\GBDataOBM\AUA\log
- C:\Users\All Users\GBDataOBM\CDP\log
Linux / Unix:
- ~/.obm/log & /usr/local/obm/log
- /usr/local/obm/aua/log
Mac OS X:
- ~/.obm/log & /Applications/GBDataOBM/log
- /Applications/GBDataOBM/aua/log
The client log on a GBDataACB client machine can be found under the following directories:
Windows 2000, XP, 2003:
- C:\Documents and Settings\administrator\.acb\log
- C:\Program Files\GBDataACB\log
- C:\Program Files\GBDataACB\AUA\log
- C:\Documents and Settings\All Users\Application Data\GBDataACB\CDP\log
Windows Vista:
- C:\Users\administrator\.acb\log
- C:\Program Files\GBDataACB\log
- C:\Program Files\GBDataACB\AUA\log
- C:\Users\All Users\GBDataACB\CDP\log
Mac OS X:
- ~/.acb/log & /Applications/GBDataACB/log
- /Applications/GBDataACB/aua/log
Lost user password or encrypting key
Lost of User Password:
In the case where your user password is lost, you can retrieve it by requesting the “forgotten password” email from our secure web portal. The password provided in the email will actually be a hashed version of the user password, the actual password is never stored on the GBDataOBS server for security reason.
The hashed password provided in the email can then be used to login to the GBDataOBM / GBDataACB client software, however, the hashed password cannot be used to decrypt data. Even if the encrypting key configured to be the same as the user password.
In the case where the backup set encryption setting is set to default (to use password as the encrypting key), you will need the actual password to decrypt any data backed up. This includes data previously backed up and also data that is backed up in the future for existing backup sets.
Loss of Encrypting Key:
In the case where your encrypting key is lost, there will be no way to restore data from the corresponding backup set. You must create a new backup set and then backup the data again in order have a restorable copy of the data. Since the encrypting key is never sent to the GBDataOBS server, thus, the encrypting key is not retrievable if lost.
If the encrypting key is lost, then the following steps must be performed to ensure that data backed up in the future can be restore and decrypt:
- Delete all backup sets where the encryption key is lost
- Create new backup sets for the affected data
- Backup the data immediately
We would like to stress that it is very important to keep a record of your user password and encrypting key.
Missed Scheduled Backups
Missed Scheduled Backups
Firstly, we would just like to clarify that missed backups might NOT necessarily be problems. End-users might have their PC/server switched off, hibernated or in standby mode when the schedule is due to run. Or network could be unavailable or be cut off during the scheduled time. We have also seen cases where the system clocks of the client machine and that of OBS are off by 12 hours, so client ran the backup job at noon while OBS was expecting a backup at mid-night, which didn’t happen and thus triggered a missed backup alert.
If the missed backup is not normal, outlined below are some guidelines on how to troubleshoot and resolve the issue:
Error with the setting “ Run scheduled backup on computers named …”
Log on to the Secure Web portal.
Please ensure that the “Run scheduled backup on computers named” for the backup set has been populated properly (see screen shot below)
Error with User Name
At the Client PC
Check if the home.txt has been populated correctly. The home.txt is located in:
C:\Program Files\GBDataOBM
You should see at least one entry pointing to a .obm folder that is accessible by the local scheduler service, e.g. C:\Documents and Settings\administrator\.obm. Rectify the home.txt if this is not the case.
Error with Scheduler not running
At the Client PC
Check if the scheduler service is running by inspecting the client side scheduler log. It is located in: C:\Documents and Settings\USER\.obm\log\Scheduler\debug.log
This log contain every detail on what the scheduler is doing.
(i) If the schedule is working fine it should contain entries like these once every hour:
——————————————-
[2007/02/14 12:43:23] [info] [Thread][Reloader] Loading profile from server …
[2007/02/14 12:43:23] [info] [LocalProfile.loadFromServer] Loading profile from server …
[2007/02/14 12:43:23] [info] [LocalProfile.loadFromServer] Loaded profile from server.
[2007/02/14 12:43:23] [info] [FileBackupSet (1137740358682)] Next backup will run in 0 hr 36 min 37 sec
[2007/02/14 12:43:23] [info] [ExchangeBackupSet (1138115138125)] Next backup will run in 80 hr 16 min 37 sec
[2007/02/14 12:43:23] [info] [Thread][Reloader] Loaded profile from server.
——————————————-
Otherwise, try restarting the scheduler service. If it still doesn’t work, try re-installing the OBM/scheduler. (In XP; start, Control Panel, double click on “Administrative Tools”, then “services”. Look for the line “Online Backup Scheduler (GBData online backup manager)”. It should be set to automatic and already be started)
If you are on Windows 2000, the scheduler service could stall at times due to the instability of Windows 2000′s Services. A workaround is to write a batch job to restart the scheduler periodically.
(ii) If the scheduler service is running fine, check whether you see something like the following at the scheduled backup time:
——————————————-
[2007/03/09 17:00:00] [info] Scheduler version= 5.2.1.0
[2007/03/09 17:00:00] [info] OS Name= Windows XP
[2007/03/09 17:00:00] [info] Java vendor=’Sun Microsystems Inc.’ version=’1.4.2_10′
[2007/03/09 17:00:00] [info] ComputerName= ComputerA
[2007/03/09 17:00:00] [info] [FileBackupSet (1137740358682)] Wake Up …
[2007/03/09 17:00:00] [info] [FileBackupSet (1137740358682)] This backup job will run to its completion.
[2007/03/09 17:00:00] [info] [FileBackupSet (1137740358682)] Start running backup
How do I set-up GBData backup software to backup Microsoft Exchange Server 2007?
1. Download and install the latest version of our online backup software . This can be found here:
2. Download and install Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 (ExchangeMAPICdo.exe)
3. Download the 32-bit Java Runtime Environment: obm55-x64-i386ext.zip
4. Expand the zip file downloaded in three above into C:\Program Files\GBData Manager
5. Start the GBData Manager application in 32bit mode:
- i. (v5.5) Run C:\Program Files\GBData OBM\bin\RunOBC32.bat
6. Create a new backup set by selecting [Backup Setting] -> [Add] -> [MS Exchange Mail Level Backup]
7. Follow the instructions of the backup set wizard to complete the configuration of the new mail level backup set
8. Perform the mail-level backup immediately by selecting [Backup], or let the backup job to be performed at its scheduled time.
Further information:
Please note that, for the backup of the information store (server level), you need to utilize the 64bit mode of GBData Manager. To run GBData Manager in 64bit mode, please start GBData Manager by double clicking on the system tray icon.
On the other hand, for the backup of the individual emails (mail-level), you need to utilize the 32bit mode of GBData Manager. To run GBData Manager in 32bit mode, please:
- i. (v5.5) Run C:\Program Files\GBData Manager\bin\RunOBC32.bat
For backup job that is performed by the scheduler services, the RunMailBackup.bat script that is located at C:\Program Files\GBData Manager\bin\ will automatically select the correct Java Virtual Machine to be ran.

