Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Duplicating Exchange 2010 backup B2D

Created: 06 Dec 2012 • Updated: 10 Dec 2012 | 3 comments

Hi all,

I have a normal full daily backup of my exchage 2010, and after it terminates it is supposed to duplicate to another disk storage.

My first step of the job occours always right but the duplicating says the following errors:

SRVSBS01 EXCHANGE BACKUP-Duplicate Exchange -- The job failed with the following error: The directory or file was not found, or could not be accessed.

Exceptions
Click an exception below to locate it in the job log

Duplicate- SRVSBS01.clandeiro.local
V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. The File and Directory count might be displayed as zero.

Duplicate
V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. The File and Directory count might be displayed as zero.

Destination Drive and Media Information
Drive and media information from media mount: 05-12-2012 21:34:03
Drive Name: NAS B2D
Media Label: B2D011138
Media GUID: {3da12aab-3ebf-4948-bb07-d43a1ddc1827}


All Media Used
 B2D011138

 IMG000951

 IMG000952


Job Operation - Duplicate
Backup Options
Media operation - Overwrite media.

Compression Type: None

Encryption Type: None

DirectCopy to tape: Disabled

WARNING: The option 'Verify after backup completes' was not selected.

Performing a verify operation to make sure that media can be read after the backup has completed is recommended.

Server - SRVSBS01.clandeiro.local
Set Information
Destination Set Information
Backup set #1: "SRVSBS01 EXCHANGE BACKUP-Full-ex"
Storage media #1: "Media created 05-12-2012 21:34:01"
Media Label: IMG000951
GRT backup set folder: \\srvnas01\backup\B2D\IMG000951
Backup started on 05-12-2012 at 21:34:03.
Duplicate completed on 05-12-2012 at 21:34:11.
Duplicate Set Summary
Backed up 0 files in 0 directories.
V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. The File and Directory count might be displayed as zero.

Processed 218864121 bytes in  8 seconds.
Throughput rate: 1565 MB/min
Set Information
Destination Set Information
Backup set #1: "SRVSBS01 EXCHANGE BACKUP-Full-ex"
Storage media #1: "Media created 05-12-2012 21:34:01"
Media Label: IMG000952
GRT backup set folder: \\srvnas01\backup\B2D\IMG000952
Backup started on 05-12-2012 at 21:34:11.
Duplicate completed on 05-12-2012 at 21:36:38.
Duplicate Set Summary
Backed up 0 files in 0 directories.
V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. The File and Directory count might be displayed as zero.

Processed 6.898.527.698 bytes in  2 minutes and  27 seconds.
Throughput rate: 2685 MB/min

The folder at \\srvnas01\backup\B2D\IMG000952 is full of files.

The event viewer writes some errors when this job fails.

An error occurred while processing a B2D command.

Changer: MoveMedium() Attempt to Dismount to Already Loaded Slot (B2DDrv4.1). Error=495

An error occurred while processing a B2D command.

Changer: MoveMedium() Attempt to Mount Non-Empty Drive (B2DDrv4.1). Error=1

An error occurred while processing a B2D command.

Changer: Error securing B2D folder path "\\srvnas01\backup\B2D\", attempting to continue with initialization. Error=6

Best regards to all.

Comments 3 CommentsJump to latest comment

pkh's picture

The backup history is corrupted.  You would need to delete your job and re-create it.

RobRodrigues's picture

Hi PKH,

You really are always here.

Guess what i createa new backup storage destination inside the NAS so the path to it is \\srvnas01\backup\B2DEX and at the jobs i simply change the storage destination to this new storage wich is the same NAS but another folder olny to this exchange backups and now the jobs with duplication right way is working fine.

What can corrupt the backup history, i'm having this many times, i'm not liking it at all.

The server is always working normally, only get errors at BE nothing more.

pkh's picture

Essentially, what you are doing is to re-create the backup history which is the same as re-creating your job.