Backup jobs from Exchange Database iDataAgent
will be displayed as "Completed
w/ one or more errors" in the Job History in the following
cases:
1. For Exchange Legacy:
If atleast one database is found to be un-mounted
and the remaining databases are backed up successfully.
If one database is
failed to backup due to exchange streaming api failure or network failure and
we cannot recover from those errors for the legacy backup.
2. ForVSS backup:
Some databases mounted, some un-mounted within one SG will not cause any
failure
'un-mounted' error may cause job failure if all databases within one SG are
un-mounted.
Other database
failures due to exchange, includes Exchange information store server
down, Exchange VSS writer not in stable state etc.
3. For Exchange 2010:
Backup from one
node that is failing and the other succeeding will cause Completed w/
one or more Errors.
Any un-mounted
database (involved in a backup) will cause a job failure.
Other database
failures due to exchange, includes Exchange information store server
down, Exchange VSS writer not in stable state etc.
Backup jobs from Exchange Public Folder Archiver Agent will be displayed as "Completed
w/ one or more errors" in the Job History in the following cases:
Backup jobs from Lotus Notes Database iDataAgent
will be displayed as "Completed
w/ one or more errors" in the Job History in the following
cases:
When the NSF database cannot be opened due to insufficient security privilege
of the backup user account configured in the iDA properties, job completes
with errors. To resolve this problem please refer to https://support.bull.com/ols/product/storage/backup/calypso
for configuring the backup user account with sufficient privileges.
The NSF database cannot be opened because the database is corrupt.
During backup if one of the databases is not accessible, due to reasons
like the database could not be opened or the database got corrupt etc.
When a subclient containing multiple databases is backed up, if it
happens that one of the databases had been deleted from the domino server,
during scan phase the deleted database is skipped and is not backed up and
the remaining databases get backed up.
For a default subclient, if all the databases that are its content are auto
discovered, then even if one of the database has been deleted from the domino
server, job completes successfully as the database that has been deleted
from the domino server will not be a part of the default subclient content.
Backup jobs from Domino Mailbox Archiver Agent
will be displayed as "Completed
w/ one or more errors" in the Job History in the following
cases:
During archiving if one of the mailboxes is not accessible, because of various
reasons like the mailbox is deleted, or could not be opened etc, then job completes
with errors.
Backup jobs from NAS iDataAgent will
be displayed as "Completed
w/ one or more errors" in the Job History in the following cases:
Backup context no longer exists on the file server. Backup cannot be restarted.
Failing restarted backup of path [^1%s]. Failed to get context list from
the file server.
Data Loss detected. The number of tape blocks written as reported by NDMP
tape server does not match the reported value for the actual tape drive.
Failed to update the reference time. Failing path.
Error committing chunks with the Job Manager. Failing path.
Failing restarted backup of path. The restart string does not match the
data backed up.
Failing restarted backup of path. Unable to parse the restart string. If
this error persists, please kill the backup and start a new one.
Exceeded maximum number of incremental backups. Must run full or differential
backup.
EMC Celerra backup failed: probably an incorrect data backup path in subclient
content.
Error writing chunk trailer to media.
Error marking the media full at end of media.
ArchiveManager error marking chunk closed in the database.
Failure to update restart string.
Failed to update media information in the database.
Error writing chunk header to NAS attached tape.
Error enabling hardware encryption on NAS attached tape drive.
Error mounting media in NAS attached tape drive.
NDMP Server [<File Server>] was unable to back up path. It is likely this
path does not exist.
Unexpected NDMP error communicating with client [<File Server>].
Unexpected NDMP error communicating with tape server [<File Server>].
NDMP connection to host [<File Server>] failed. Verify if NDMP can be reached
on this host.
Could not position tape. Error returned [<File Server Error String>].
<File Server>: tape server halted with internal error.
Tape server halted with INTERNAL_ERROR and may not have received any data
for the timeout period. Backup may be retried with NDMP_API DWORD registry key
nREADSOCKETTIMEOUT set to a larger value, in seconds.
NDMP Server is reporting a write error: [NDMP_MOVER_HALT_MEDIA_ERROR].
NDMP Server is reporting a write error: [NDMP_MOVER_PAUSE_MEDIA_ERROR].
Received data halt with internal error. See nasBackup.log for problem details.
Error updating the new chunk information in the database.
Error write file mark to NAS attached media.
Error sending backup file information to indexing.
When using snapmirror-to-tape, a full volume must be backed up. Backup Path
is not a full volume.
NDMP authentication failed.
Failed to start the NRS process on remote host [<Media Agent>]
Backup jobs from Microsoft Sharepoint Server iDataAgent will be displayed as
"Completed
w/ one or more errors" in the Job History in
the following cases:
Sharepoint Database Backup
Site collection backup error “[backupSiteCollection]:
Microsoft.SharePoint.SPException: Write error on file "*.dat". ”
This implies
that there is not enough free space where the file is staged (folder ..\iDataAgent\MS
Sharepoint Doc Agent). An appropriate amount of
temporary space must be allotted in the Job Results folder to accommodate the
SharePoint Database Site Collection, Portal Index and SharePoint Document
metadata.
Error “CCvSQLVDIBase::InitializeVDI() - Failed to create Virtual device”:
This implies that the connection to SQL Server is lost, because it is a farm setup and remote.
Under SharePoint Server Properties select option “SQL Databases hosted on a
remote SQL Server”.
Sharepoint Documents OM Backup
Error “SP2K3DocServer COM return error - Access is
denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))”. This implies
that the
Base Services account is not given site administrator rights. Add
the account to site as Site Administrator.
Backup jobs from Microsoft SQL Server iDataAgent
will be displayed as "Completed
w/ one or more errors" in the Job History in the following
cases:
When a subclient which contains multiple databases is backed up, if one
of the database is not backed up due to reasons like, database is in
standby mode or database got corrupt etc, then job completes w/ one or more errors.
The databases that failed will be shown as part of the failed items and those
that were backed up will be shown as part of the successful items.
When running a backup, a check is made to verify if the backup is
restorable. If the log chain is broken the job will be displayed as
Completed With Errors.
CDR works at a pair-level and WBA works at a Repset level and repsets can possibly contain
more than one pair. Hence, when deciding the completion status of the job, the
status of each pair is taken into account. The logic is:
If all pairs have failed, job fails.
If all pairs have succeeded, job succeeds.
By default, if at least one pair has succeeded and at least one pair has
failed, job fails. However, this behavior can be overridden via a registry
key, which, if set, causes the job to be reported as "Completed
w/ one or more errors". This registry key is a DWORD named “nRestartOnlyFailedContents”.
Backup jobs from Continuous Data Replicator/Workstation Backup will be displayed as
'"Completed
w/ one or more errors"' in the following cases:
Driver detected Error: Monitored journaling
driver (for CDR) or Change journaling driver (for DDR/SDR/WBA) faced a critical
error.
Configuration file is corrupt. Content configuration
maintained locally by CDR service is corrupt.
Aborting pair since source could not ask destination
to start log replay (CDR).
Failed to perform incremental backup because
one or more expected items were missing from system log files (DDR/SDR/WBA).
Client computer has a new update which requires
a reboot before jobs can run. Please reboot the client computer and resume backup
jobs (DDR/SDR/WBA).
Update is being installed on this machine.
Cannot run backup now (WBA).
User disabled backup activity. No backup will
be done (WBA). Backup activity has been explicitly disabled by user via WBA
desktop console.
Pair is in inconsistent state.
Could not connect to CommServe or to destination.
Pair Level File filters changed. Needs full
resync.
Cluster Group of which this pair is part of,
failed over to other server. (DDR/SDR)
Destination volume is full. Aborting pair
on request from destination.
Failed to create destination directory.
Specified source path doesn't exist. A pair’s
source folder does not exist.
Invalid source path. Problem encountered with
a pair’s source path.
No pairs are configured for Repset. Backup
requested on a repset that has no content defined. (DDR/SDR/WBA)
CDR Service is not initialized completely.
Please try again after some time.
Changes were saved to CommServe Database,
but the Replication Service could not be reached for change notifications. Network
problem was observed when connecting to remote component.
Failed to allocate Memory.
Failure starting data transfer pipe, Network
Error.
Journal Id in smart synch phase does not match.
Could not create resynch file. A collect file
could not be created.
Could not take snapshot of source folder.
Could not initiate checksum processing.
Failed to perform checksum processing with
retry.
Source did not receive response from destination
for smart sync update.
Mismatch between the current source volume
GUID and the GUID when the pair was created.
Failure Scenarios with Recovery Point Jobs
CDR Service encountered error while processing request.
Failed to create snapshot.
Failed to identify paths to databases. Error specific to a native IDA
Mining CRP. (CDR)
Required Library is missing for performing database recovery. Error
specific to a native IDA Mining CRP. (CDR)
Failed to perform database recovery. Error specific to a native IDA
Mining CRP. (CDR)
