|
1.2. What is
the recommended bandwidth?
1.1. How do I run OBM with Microsoft ISA 2004?
1.4. How do I install OBM on FreeBSD?
1.5. How do I install OBM on SCO Unix?
1.6. How do I install OBM on AIX?
1.7. The Windows version of OBM installer
hangs, what could be the problem?
1.8. The Installer doesn’t seem to work. How can I manually install OBM
on Windows?
1.9. The Installer doesn’t seem to work. How can I manually install OBM
on Mac?
1.10. Error occurred when Installing OBM on
Novell.
1.11. Are there any command line tools for OBM?
1.12. How does OBM detect changes in files? Does it use the Archive bit?
Some tape backup software resets the Archive bit. Would this affect OBM
when backing up the same data?
1.11. Does OBM copy the same set of files
regularly?
1.14. Transfer Block Size is 128Kb by
default. Is there a reason for this?
1.15. How can I backup a huge data set over the
Internet?
1.16. What is the best way to restore a huge data
set?
1.17. Does In-File Delta backup require a temporary
working directory?
1.18. What is the average compression
ratio?
1.19. Can I change my encrypting key?
1.20. If the “Use Login Password as Encrypting Key”
option was selected when creating the backup set. Why I cannot restore
the backup data with my most current login password?
1.21. What kind of encryption used by OBM?
1.22. When select the backup option “local hard
drive” to backup to external hard drive, it fails in the middle of the
process, why?
1.21. Scheduled backup jobs are not running on my
Windows machine, why?
1.24. I am having problems with my scheduled backup,
why?
1.25. I cannot get proxy authentication to work with OBM,
why?
1.26. Can I backup an entire Operating System?
1.27. When setting up a Microsoft SQL Backup Set, I
cannot list the available SQL servers, what can I do?
1.28. Why are the Microsoft SQL Server databases
missing from the backup source list?
1.29. How to set the recovery model of a MS SQL
database to FULL?
1.30. Windows network map drive connections are not
stable, why?
1.31. There is an error when backing up files on a
remote NetWare server, what can I do?
1.32. What are the advantages and disadvantages of
backing up multiple computers using a single backup account?
1.31. How to find out which version of the client
software the user is using?
1.34. Does the OBM upgrade the installation of Java
on a client machine, or does it install a separate copy for its own use?
1.35. After upgrading OBS, do I have to upgrade all the OBM
as well? And do I need to transform/migrate their current data?
1.36. Is it possible to do incremental or differential backups with MySQL?
1.37. How does the “Remove retention files for
overlap policy” under Advanced Retention Policy work?
1.38. What is incremental backup and how does
In-File Delta work?
1.39. How does the “Auto” block size work under
In-file Delta settings?
1.40. What happens when we do In-File Delta backup
on a directory?
1.41. Does OBM have to stop the application when
doing online backups?
1.42. What are Off-line backup, Logout backup
reminder and Local backup features?
1.41. Why is my OBM running backup once every hour?
1.44. How do I disable “logout backup reminder”?
1.45. How do I upgrade OBM from V4.5 on Linux?
1.46. How do I change the .obm path for Novell?
1.47. The MS SQL or MS Exchange database backup job stores 2 copies of
the spooled database file in the "temporary directory" (tagged with
different datetimes). This has taken up extra disk space, is this
necessary?
1.48. What do I have to do in order to backup open
files?
1.49. How does Volume Shadow Copy work?
1.50. In Windows, when OBM is creating Shadow Copy Set, it gets the
“[ERROR] E_UNEXPECTED” error, what can I do?
1.51. How to backup Oracle 7.1.4 on NetWare?
1.52. How do I backup NTFS permission?
1.51. How do I restore NTFS permission?
1.54. How do I backup file permission in Linux?
1.55. How do I restore file permission in Linux?
1.56. How do I remove OBM completely from my Windows
machine?
1.57. Does OBM work with dial-up connections?
1.58. The OBM crashes when opening [Backup Source]
of a Lotus Domino/Notes backup set, what can I do?
1.59. How do I restore a machine from my SystemState backup?
It really depends on what
kind of data to be backed up, e.g. for personal file backups, the daily
data transfer should be limited, while MS Exchange backup could be
significant. You may want to use this white paper regarding
online backup speed as a
reference.
^Back
to 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]
1.
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 panel1. 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]
1.
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.
^Back
to 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
1.
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
1.
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
^Back
to 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)
1.
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
^Back
to top
Please do the
followings to install OBM on AIX:
1.
Install Java 1.1.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)
1.
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
^Back
to 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.
1.
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.
^Back
to 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
1.
Run C:\Program
Files\OBM\bin\install.bat
4.
Run C:\Program
Files\OBM\bin\Install-Scheduler.bat
^Back
to 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
1.
Run "chmod -R 755 /Applications/OBM" using Terminal
4.
Double-click the “Online Backup Manager” icon in /Applications/OBM folder
^Back
to top
Some users would have
problems when trying to install OBM on Novell Netware Client version.
(The machine had met all the system requirements: Netware v5.1 and
Netware Java v1.1.1). User could receive the following error message
during installation.
Exception in thread "main"
Java.lang.noclass def found error.obm
Java: class obm exited with status 1
Check the
following
Please check if the OBM_HOME
environment variable set in SYS:\OBM\bin\BackupManager.ncf is correct?
envset OBM_HOME=SYS:\OBM
envset
OBM_CLASSPATH=$OBM_HOME\bin;$OBM_HOME\bin\obm.jar;
$OBM_HOME\bin\obm-lib.jar
envset LIB_PATH=$OBM_HOME\bin
java -mx384m -Djava.library.path=$LIB_PATH
-cp $OBM_CLASSPATH obm SYS:\OBM
Please change the SYS:\OBM environment
variable to your installation directory.
^Back
to top
Yes, there
are scripts in [OBM Program Home]\bin and they are described below:
Windows
l
Decrypt.bat: decrypts the
specified backup files
l
install.bat: installs the
OBM icon to the System Tray and registers the Online Backup Scheduler as
a service
l
Install-Scheduler.bat:
registers the Online Backup Scheduler as a service
l
RegisterVSS.bat:
re-registers Microsoft’s Volume Shadow Copy service DLLs
l
Remove-Scheduler.bat:
un-registers the Online Backup Scheduler service
l
Restore.bat: restores the
specified snapshot of the backup set to the specified location
l
RunBackupSet.bat: runs the
specified backup set
l
RunOBM.bat: launches the
Online Backup Manager user interface
l
Run-Scheduler.bat: starts
the Online Backup Scheduler service
l
SeedLoad.bat: runs seed load
for the specified backup set to the specified location
l
Uninstall.bat: removes the
OBM icon from the System Tray and un-registers the Online Backup
Scheduler service
Linux
l
BackupManager.sh: launches
the Online Backup Manager user interface
l
Configurator.sh: configures
client parameters such as Backup Server address, username/password,
encrypting key, etc.
l
Decrypt.sh: decrypts the
specified backup files
l
Restore.sh: restores the
specified snapshot of the backup set to the specified location
l
RunBackupSet.sh: runs the
specified backup set
l
Scheduler.sh: starts the
Online Backup Scheduler service
l
SeedLoad.sh: runs seed load
for the specified backup set to the specified location
l
StopScheduler.sh: stops the
Online Backup Scheduler service
*You may
have to set some variables in these scripts and more instructions are
provided.
^Back
to top
OBM compares
timestamps of files on the server with the corresponding copies on
client machine. Archive bit is not used as it does not detect relocated
files. Therefore tape backup would not affect OBM.
^Back
to top
After the
initial upload, subsequent backup jobs will only transfer the modified
or new data to the Backup server. It depends on the nature of the data,
but normally, less than 2% of all data is modified.
^Back
to top
Backup data
is transferred in blocks (instead of file by file) to minimize
connection negotiation roundtrips. It is not the TCP/IP block size. This
setting is optimal for the backup operation.
^Back
to top
If you have a
lot of data (e.g. 300GB) to backup to the backup server, it would take a
considerable amount of time to perform the first full backup over the
Internet. You can try the following method:
1.
Use the Seed Loading
Utility to backup your backup set to a local hard disk (instead of
directly transfer to the backup server)
2.
Send the backup data, using
a removable hard disk, to your backup service provider.
1.
The administrator can then
load all your backup files from your removable hard disk into your
backup account. This could save you days (even weeks) of performing your
first full backup.
In addition,
subsequent backups are incremental (only new or updated files will be
uploaded to the server), the amount of data transfer should be
relatively small.
Please refer
to the User’s Guide for details on the “Seed Loading Utility”.
^Back
to top
You can copy
the data of the particular backup set on OBS to a removable media, e.g.
external hard disk, and ship it to your client. Your client can then use
the “Decypt Files Tool” in OBM to restore the backup data from
the removable media to its original format.
^Back
to top
OBM requires a temporary
storage for the delta file before it gets sent to the server.
For example:
If you have a 10GB file
that has already been backed up to the server and you have updated 10MB
of this file. Then you need to have at least 10MB of free space in the
temporary directory for the delta file.
*Note: Certainly you
do not need 10GB of free disk space.
Also, if you want to
backup 5 x 10GB files in the same situation. You will only need 10MB of
free space (not 5 x 10MB), because each delta file will be automatically
deleted right after it has been backed up.
^Back
to top
All backup
files are compressed and encrypted before uploading to the Backup
Server, the average compression ratio for text-based file 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 variety
types.
^Back
to 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.
^Back
to 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.
Currently, 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
http://download.ahsay.com/support/screenshots/EncryptingKey.jpg
^Back
to 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.
^Back
to top
Please check if the external hard drive is
in FAT32 volume format. And also check whether there is any folder
containing more than 32000 files and there is no file bigger than 4GB
within your backup set. It is a FAT32 limitation, you may try to convert
the FAT32 volume to NTFS.
^Back
to top
Please try
the followings:
1.
Check if [Control Panel] ->
[Administrative Tools] -> [Services] -> [Online Backup Scheduler] is
available and started
2.
Check if C:\Program
Files\OBM\home.txt contains the home directory for your backup account
(e.g. C:\Documents and Settings\Administrator\.obm)
1.
Check if C:\Program
Files\OBM\jvm\bin\SchedulerOBM.exe exists
4.
Check if C:\Program
Files\OBM\log\Scheduler\info.log contains the startup loading entry,
e.g.
i.
[2005/12/12 12:42:44] OS
Name=Windows XP
ii.
[2005/12/12 12:42:44] OS
Version=5.1
iii.
[2005/12/12 12:42:44]
Scheduler Version=5.0.1.3e
iv.
[2005/12/12 12:42:44] Java
Vendor=Sun Microsystems Inc. Version=1.4.2_10
v.
[2005/12/12 12:42:44] [info]
Starting Scheduler, User:'backup-account', Home:'C:\Documents and
Settings\Administrator\.obm'
5.
Check if C:\Documents and
Settings\Administrator\.obm\log\Scheduler\debug.log contains the
debugging information for your scheduler
If your
system settings is not the same as the above steps, please download a
new installer (obm-win.exe) from our website or the customization portal
and try again.
^Back
to top
If you are backing up files
from a network drive, please check if you have included the valid
“Network Resources Authentication” information for the backup set. This
is required for scheduled backups that access any network resources.
You can refer to the following
screenshot:
http://download.ahsay.com/support/screenshots/Network_Resources_Authentication.JPG
^Back
to top
If you are
using port 80, please check whether your proxy server accepts "HTTP
CONNECT" calls on port 80. You may also want to try other ports like 443
to see if your proxy server accepts that.
^Back
to top
Currently, it
is not possible to do hard disk image backup with OBM. However, you can
still backup/restore the operating system by doing the followings:
To backup all
files including the operating system, please do this:
1.
Add all files to your backup
source
2.
Add a SystemState backup
type to your backup account (Windows only)
To restore
all files including the operating system, please do this:
1.
Re-install the operating
system and applications
2.
Restore the SystemState
backup to your machine (Windows only)
- To restore the System State data on a domain controller, you must
first start your computer in a special startup option called "Directory
Services Restore Mode". To access "Directory Services Restore Mode",
press F8 during startup and select it from the list of startup options.
1.
Restore all files to your
machine
^Back
to top
You can try
running “osql –L” in a command prompt, you should see the following:
Servers:
(local)
SQLSERVER1\INSTANCE1
SQLSERVER2\INSTANCE2
If you have a
firewall installed, please disable it. UDP Broadcast must be allowed.
^Back
to top
If you have
firewall installed on your network, please make sure UDP port 1434 is
allowed on the SQL Server.
^Back
to top
You can change the
recovery model by running the following commands, run it along with each
of the database that you want to run transaction log backup.
C:\> osql -E -S
SQLSERVER1\INSTANCE1 -Q "ALTER DATABASE xxx SET RECOVERY FULL"
Where
SQLSERVER1\INSTANCE1 =
the SQL Server and the corresponding instance
xxx = the name of the
database
^Back
to top
You may want
to try editing a few Windows Parameters.
SMB Size
When running
applications that copy or move a large amount of data to a remote
server, the speed of such action is determined by network speed and by
the SMB (a protocal related to Windows map drive) size.
NT/2000 negotiates the
SMB size and will generally set this to 4K blocks for applications that
are moving or copying data to a remote server. By increasing this block
size, you will allow the server to complete its file copies faster. This
will increase the performance of the application making the copy/move
calls.
HKEY_LOCAL_MACHINE\System\Current Control
Set\Services\LanmanServer\Paramerters
"SizReqBuf"= REG_DWORD
Set Value To: 16000 =
HEXDEC
Ref:
http://support.microsoft.com/default.aspx?scid=kb;en-us;320829
Map Drive Auto
Disconnect Settings
Reference:
http://support.microsoft.com/kb/138365/EN-US/
http://support.microsoft.com/default.aspx?scid=kb;en-us;297684
HKEY_LOCAL_MACHINE\System\Current Control
Set\Services\LanmanServer\Paramerters
Autodisconnect to:
fffffff
Creating BAT file for
better performance
If you are still having
problems, you may want setup a BAT file and scheduled this file to run
every 10 minutes, please setup the BAT file as follow:
BAT file
settings:
--------------------------
ping mapdrv
ping 192.168.1.15
net config server /autodisconnect:-1
net use /persistent:yes
net use "\\mapdrv\DATA STORAGE1"
net use "\\192.168.1.15\DATA
net use d: \\192.168.1.15\DATA STORAGE1
net use e: "\\mapdrv\DATA STORAGE1"
dir d:\
dir e:\
--------------------------
l
mapdrv = your NAS device
network name
l
192.168.1.15 = mapdrv
In addition,
create a host file on the server hosting the program, have the following
entry in it:
l
mapdrv = 192.168.1.15
And if you
are on a 2003 server, refer to the following:
Reference:
http://support.microsoft.com/default.aspx?scid=kb;en-us;890553
For Windows
2000, you may want to install the following Hotfix:
Windows2000-KB903237-x86-ENU
Reference:
http://support.microsoft.com/default.aspx?scid=kb;en-us;903237
^Back
to top
If you want
to backup \\SERVER\SHARE that is located on a NetWare server and you are
getting "Network drive is not accessible" error message. Please
try adding the following command as a [Pre-backup command]
net use
\\SERVER\SHARE [PASSWORD] /USER:[DOMAIN | MACHINE_NAME]\[USERNAME]
This will
authenticate the current process with the NetWare server and therefore
allow your backup to run correctly.
^Back
to top
Advantages
l
You require less backup
accounts
l
You can use one username and
password to configure the backup setting for all Backup Sets
Disadvantages
l
You must use different
backup sets for different computers
l
Whenever a new backup set is
created under the backup account, you need to go back to all computers
using the same backup account to uncheck the “Run scheduled backup on
this computer” option for the new backup set (Since backup setting
is saved on server and new backup set is default to run on all
computers, i.e. with the option checked).
l
Improper configuration could
easily cause problems, which are difficult to debug.
^Back
to top
You can check
which version a client is running by checking the access log.
The default location of the access log file is:
l
Windows: “C:\Program
Files\Offsite Backup Server\logs\access_log*.txt”
l
Linux:
“/usr/local/obs/logs/access_log*.txt”
l
Mac OS X:
“/Applications/OBS/localhost/logs/access_log*.txt”
The ‘/obs/obcX.X/file/????File.obc?u=USER_NAME&..ver=Y.Y’
entries contain this information, where:
l
USER_NAME = Login Name of a
backup account
l
X.X = major version of the
client software
l
Y.Y = minor version of the
client software
And starting
from OBS v5.0.1.5, the version of OBM can be check from the OBS
Management Console under the [Manager User] -> [Report] -> [Detailed
Report] page of the corresponding user.
^Back
to top
OBM uses its
own copy of Java and leaves the system Java VM intact.
^Back
to top
OBS works with previous versions of OBM (However
not the other way round). You only need to upgrade the existing client
software if you want to take advantage of the new features. And you do
not need to transfer client backup data again after the OBS ugprade.
^Back
to top
MySQL backup
is done with SQL Dump file, and it generates a single file which is then
uploaded. These backup files usually very large size and it takes time
to backup to the server. At this moment, it is not possible to do
incremental dump with mysqldump. But our In-File Delta feature shall
ensure that, instead of the entire backup file, only the changed data
blocks within the dump file are uploaded to the Backup Server.
^Back
to top
In general,
daily snapshots followed by a weekly snapshot or a monthly snapshot,
etc. will be removed; weekly snapshots followed by a monthly snapshot or
a quarterly snapshot, etc. will be removed; and so on.
This is illustrated by
the following example.
Assume today is 17Jan06,
and the Advanced Retention Policy is as follows:
l
Daily: retain for 7 days
l
Weekly: retain for 4 weeks
(the job will be performed on Saturday)
l
Monthly: retain for 3 months
(the job will be performed on 1st of each month)
If “Remove retention
files for overlap policy” is NOT enabled:
Then a total of 14
snapshots (7+4+3) will be kept on the server accordingly, i.e.:
(Daily): 10Jan06, 11Jan06, 12Jan06, 13Jan06, 14Jan06, 15Jan06,
16Jan06
(Weekly): 24Dec05, 31Dec05, 7Jan06, 14Jan06
(Monthly): 1Nov05, 1Dec05, 1Jan06
If “Remove retention
files for overlap policy” is enabled:
Then only the following
snapshots are kept: 1Nov05, 1Dec05, 1Jan06, 14Jan06, 15Jan06, 16Jan06.
Specifically,
the weekly policy overrides the daily policy so 10Jan06, 11Jan06,
12Jan06 and 13Jan06 will be removed. The monthly policy overrides the
weekly policy, and 24Dec05, 31Dec05 and 7Jan06 will be removed as well.
^Back
to top
In an
incremental backup, only modified files will be uploaded to the Backup
Server.
On the other
hand, In-File Delta is applicable to the physical files to be uploaded
to the Backup Server, does not matter whether it is a MS SQL database
file, MS Exchange transaction log file or any normal file in a
FileBackupSet. Specifically, only the changed blocks in comparison to
the original file on the Backup Server (delta file) will be uploaded.
For each
modified file, OBM would determine whether the entire file or only delta
file should be uploaded. If the entire file is to be uploaded, the old
version of the file will be moved to the Retention area. Else if only
the delta file is to be uploaded, the previous delta files will be moved
to the Retention area and the Data area should contain the original full
backup file, checksum file and the latest delta file of this file.
^Back
to top
If the block
size is set to “Auto”, the effective block size (Started from OBM
v5.0.1.7) will be chosen from the following table based on the file size
of the updated file:
File
Size Delta Block Size
------------ ----------------
0 - 500M
4k
500M - 2G
8k
2G - 8G
16k
8G - 15G
32k
> 15G
64k
^Back
to top
When you do
backup, the Online Backup software will do the followings:
1.
Check if any files are
added, updated or deleted (the calculation of these files are based on
files having the same filename).
2.
New files will be uploaded
to the server in whole.
1.
Deleted files will be
removed from Data area and placed into the Retention area on the Backup
server.
4.
Updated files will be
processed by the In-File delta option (i.e. only changed data blocks
within the files will be uploaded to the Backup Server)
^Back
to top
OBM can
backup application data while the application is still running.
Particularly, we have special agents for MS Exchange Server, MS SQL
Server, Oracle, Lotus Notes and MySQL, which allows these applications
to be backed up while they are online. With the Volume Shadow Copy
feature started from OBM v5.0, we are able to backup other types of
applications while they are online.
^Back
to top
Off-line Backup is basically designed for
notebook users who are off-line most of the time, and cannot rely on
backup schedule to backup regularly. The backup interval allows notebook
users to specify the interval that they would like their data to backup.
If this interval has elapsed, backup will run automatically once this
machine is online.
Logout Backup Reminder asks user if they
would like to backup if they logout of the computer or shutdown their
computer.
Local Backup allows an extra copy of
backup file to be kept on local hard disk when backup is running.
^Back
to top
You might have “Off-line
backup” enabled for every hour. Please do the following to disable
that:
1.
Logon to OBM
2.
Select the backup set that
you want to disable the Off-line backup from the left panel
1.
Select the [Extra Backup]
node under the backup set node on the left panel
4.
Uncheck the [Enable off-line
backup] checkbox under the “Off-line Backup” section
5.
If you want to do this to
all backup sets, please repeat the previous step for each backup set
Press the [Save
Setting] button from the toolbar
^Back
to top
To disable
the “System Logout Backup Reminder”, please do the followings:
1.
Logon to OBM
2.
Select the backup set that
you want to disable the Logout reminder from the left panel
1.
Select the [Extra Backup]
node under the backup set node on the left panel
4.
Uncheck the [Enable System
Logout Backup Reminder] checkbox under the “System Logout Backup
Reminder (Windows)” section
5.
If you want to do this to
all backup sets, please repeat the previous step for each backup set
Press the [Save Setting]
button from the toolbar
^Back
to top
Please do the followings for upgrade:
1.
Shutdown backup scheduler by
running "touch $OBM_HOME/ipc/Scheduler/st | 
