|
1.
|
“Quota Exceeded”
|
|
|
This means that the backup account has run out of its allocated quota. Please contact
your administrator (or backup services provider) to increase your backup quota.
|
|
2.
|
“Access is denied”
|
|
|
This means that the file is not accessible by OBM. Please check if the system account
that runs OBM has read access permission to the mentioned file.
|
|
3.
|
“Checksum incorrect” / “Uploaded file size incorrect”
|
|
|
This error occurs when the backup file uploaded to the server is corrupted. Corrupted
backup files would not be stored on the backup server but will be uploaded to the
backup server again in the next backup job.
If more than one backup job of the same backup set is being run on more than one
computer at the same time, you might get this error. Please check if you have installed
the client software (OBM) with the same backup account on more than one computer.
Also, please check the file C:\Program Files\OBM\home.txt and see if you have more
than one “.obm” record (e.g. C:\Documents and Settings\Administrator\.obm)
in this file that refers to the same backup account on the server. If you can find
such entries, simply remove the redundant lines from this file and restart the computer.
Sometimes, this problem could be caused by network instability. If this only happens
occasionally, you can safely ignore this error.
|
|
4.
|
“File 'obm-delta.tmp' does not exist on server” / “File 'obm-chksum.tmp'
does not exist on server”
|
|
|
For OBM v5.0.1.4 or before, please:
1. Upgrade your OBM to a newer version.
2. Delete the obm-delta.tmp or/and obm-chksum.tmp files from your “temporary
backup directory”, (e.g. C:\Backup\MSExchange\1137065709669).
For later versions of OBM, you can simply do step 2 to remove the problematic files
which were left behind during the backup operations of previous versions.
|
|
5.
|
“C:\xxx\yyy\zzz.txt has been removed already”
|
|
|
There is latency between the backup agent with the list of files to be backed up
and the time these files are actually backed up. If any of these files are removed
between this latency, an informative message, “C:\xxx\yyy\zzz.txt has been
removed already”, will be logged in the backup log report. Under most condition,
you don’t need to worry about this since files created and then removed in
this situation are usually temporary files. It is used by some other applications
and it is not necessary to backup these files.
If you are using Infile-Delta, please make sure “Temporary directory for storing
backup files” setting of your OBM is pointing a writable directory with plenty
of disk space.
|
|
6.
|
“The process cannot access the file because another process has locked
a portion of the file”
|
|
|
You get this message when backing up “C:\xxx\yyy\zzz.txt” because another
application has held a read-exclusive lock on “C:\xxx\yyy\zzz.txt”.
The backup agent, therefore, is unable to open the file to read its content. Please
try the followings to resolve this problem:
- Enable the Volume Shadow Copy option for the corresponding backup set if you are
on Windows 2003 or XP.
- If you are on an older version for Windows, you may need to obtain a generic “Open
File Manager” in order to backup the locked files.
- If the locked file is not important (e.g. C:\pagefile.sys), simply exclude the locked
file from your backup source. By doing so, this message will not appear again.
- If the locked file is a database file held open by one of our supported applications
(e.g. Microsoft SQL Server, Microsoft Exchange Server, Oracle, Lotus Domino/Notes,
MySQL), simply use the corresponding add-on module provided to backup the database.
This way, you can backup the database you want (using the application specific APIs)
without accessing the database file directly.
- If the locked file is a file held open by some other third party applications, you
can use the [Pre/Post Command Line Tool] to shutdown/restart the application that
is locking the file before/after a backup job to make sure that no locks will be
placed on files that you need to backup.
|
|
7.
|
“The process cannot access the file because it is being used by another
process”
|
|
|
This means that the file is currently locked by another process (or program). Please
shutdown the program locking this file before running the online backup program
again.
|
|
8.
|
“Premature end of input”
|
|
|
It means that the client software has problem downloading the list of files to be
backed up from the backup server. It then retries getting the list again. This is
nothing to worry about. OBM would log this as information rather than warning to
avoid raising false alarm.
|
|
9.
|
“Invalid XML Character” / “XML document structures must start
and end within the same entity”
|
|
|
Please try the followings:
- Logon to the web interface of this backup account
- Go to the [File Explorer] page and browse to the directory reported that contain
this problem (or some other directories)
- Check if there are any filenames containing strange characters and delete them
- Try backup again.
Also, please try increasing the "connectionTimeout" attribute within the
"Connector" tag inside [OBS Home]\conf\server.xml to a larger value (e.g.
connectionTimeout="180000" or connectionTimeout="600000"). This
should help solve the problem.
|
|
10.
|
“Incorrect Function”
|
|
|
Please check if you have any antivirus or personal firewall software installed.
Kindly disable it from scanning the related data and traffic to see if the problem
persists.
|
|
11.
|
“HTTP/1.1 502 Proxy Error”
|
|
|
The specified Secure Sockets Layer (SSL) port is not allowed. ISA Server is not
configured to allow SSL requests from this port. Most Web browsers use port 443
for SSL requests.
Refer to
http://support.microsoft.com/kb/283284
|
|
12.
|
“[Microsoft][ODBC SQL Server Driver][SQL Server]The statement BACKUP LOG
is not allowed while the recovery model is SIMPLE”
|
|
|
You need to change the Recovery model to FULL.
- Open up the backup source of the SQL database in the backup software
- Right click on the erroring database > Recovery Model > Full
Alternatively, if you are using MSDE you can issue the following commands: osql
-E -S [Server Name] -Q "ALTER DATABASE [Database Name] SET RECOVERY FULL"
These will enable transaction logging option for your MSDE databases and allow incremental/differential
backup to be run with no problems.
|
|
13.
|
“CExBackup::backupService:HrESEBackupSetup: Error Number 0xc800020e: An
incremental backup cannot be performed when circular logging is enabled”
|
|
|
You need to disable circular logging in MS Exchange. Please uncheck the [Enable
circular logging] option as shown
here and restart the “Microsoft Exchange Information Store”
service after you are done.
|
|
14.
|
“CExBackup::backupStorageGroup:HrESEBackupTruncateLogs: Error Number 0xc7ff1004:
(null)”
|
|
|
This is an error returned by the Microsoft API and is a Microsoft issue. Please
try to restart the "Microsoft Exchange Information Store” service. If
the problem persists, you may want to schedule the service to restart on a daily
basis.
|
|
15.
|
“CExBackup::backupStorageGroupLog:HrESEBackupGetLogAnd
PatchFiles: Error Number 0xc8000232: Some log or patch files are
missing”
|
|
|
If you have just disabled the MS Exchange circular logging option, please try running
a full backup again, this should fix the problem.
|
|
16.
|
“CExBackup::backupFile:WriteFile: Error Number 0x6: The handle is invalid”
|
|
|
This is MS Exchange having problem in writing to the Temporary spooling directory.
Please ensure that the system account running the MS Exchange has full access right
to that directory. If it is a network drive, please use an UNC path (e.g. \\server\share),
and the “Network Resources Authentication for Windows” is properly set
for the corresponding backup set.
|
|
17.
|
“Path ‘C:\Temp\MSSQLServer\1137040769567’ does not exist”
|
|
|
If you get this error while you are doing MS SQL or MS Exchange backup, please try
to use an UNC path (e.g. //server/share) in "Temporary directory for storing
backup files" under [Backup Source Settings]. Please make sure that your OBM
is on the same machine as your MS SQL or MS Exchange. Please also ensure that you
have included the appropriate “Network Resources Authentication for Windows”
information in the backup set. For MS SQL Server, you may want to check whether
if it can spool the database file correctly by running the following command:
(Windows Authentication mode)
osql -E -Q "DECLARE @dbname char(64) SET @dbname = 'xxx' BACKUP DATABASE
@dbname TO DISK = '//server/share/abc.txt' WITH SKIP"
OR
(SQL Server Authentication mode)
osql -U USERNAME -P PASSWORD -Q "DECLARE @dbname char(64) SET @dbname = 'xxx'
BACKUP DATABASE @dbname TO DISK = '//server/share/abc.txt' WITH SKIP"
Note:
USERNAME/PASSWORD = the database username/password
xxx = the database that you would like to backup
//server/share/abc.txt = the location for the database spooling file
|
|
|
|