Media Mount failed. User canceled a Phisical Volume Library operation

[Laith]

Hi there,


I have three servers that i backup them every day to an HP LTO-1 Ultrium. Im using 200GB tape.

The data that im backing up is about 130GB.

I'm monitoring the server remotely and i dont have access to the server remotely because of the company policy so i recieve daily reports about the server status.

Anything wrong i have to go personaly.

I've been recieving following error for the last three days.

Media mount failed.
User cnceled a phisical volume library operation.
v-79-57344-33861.

I'm new to the backup principles. but i did my best to search the problem cause.

I'm suspecting that this error is because of the tape is full. But it also might be a buffer problem since i backup three servers.

if the problem is the tape, then i know the easiest solution is to buy a bigger tape drive. BUT i need to know something before doing that.

Is it possible to use two tapes to backup my data?
If yes, As you will see that i start my backup at 20:00:00. and the backup stop at 6:00 and that means no one can insert the 2nd tape. What is the best practice solution?

Below is the job log:-

Job Log for Allt


--------------------------------------------------------------------------------


Completed status: Canceled, timed out  
Expand AllCollapse All  


Job Information
Job server: SE01SW01
Job name: Allt
Job started: den 23 september 2009 at 20:00:04
Job type: Backup
Job Log: BEX_SE01SW01_01314.xml

 

Drive and media mount requested: 2009-09-23 20:00:04

No appendable media could be mounted.
Switching to overwrite operation on scratch media.


Device and Media Information
Drive and media information from media mount: 2009-09-23 20:00:21
Drive Name: HP 1
Media Label: LTO000005
Media GUID: {f97857e2-0efa-4db2-95b2-680e4c4786e1}
Overwrite Protected Until: 2009-09-26 20:00:21
Appendable Until: 9999-12-31 01:00:00
Targeted Media Set Name: Tape

All Media Used
 LTO000005

 


Job Operation - Backup  
Backup Options
Media operation - append.
Compression Type: Hardware [if available, otherwise software]

 



Server - SE01SW01

Set Information - E: DATA
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "E: DATA"
Backup set #1 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 20:00:40.
Backup completed on 2009-09-23 at 22:28:06.

Backup Set Summary
Backed up 44197 files in 6530 directories.
Processed 70 154 889 927 bytes in  2 hours,  27 minutes, and  26 seconds.
Throughput rate: 454 MB/min

 

 


Database Consistency Checks
Consistency checking BEDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking master
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking model
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking msdb
Consistency Check including Indexes.
Consistency check was completed.

 


Set Information - SE01SW01\BKUPEXEC  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "SE01SW01\BKUPEXEC "
Backup set #2 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back up entire database or filegroup
Microsoft SQL Server Agent: Started

 


Backup started on 2009-09-23 at 22:28:18.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 22:28:53.

Backup Set Summary
Backed up 4 databases
Processed 29 049 505 bytes in  35 seconds.
Throughput rate: 47.5 MB/min

 

 


Set Information - \\SE01SW01\System?State  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\SE01SW01\System?State "
Backup set #3 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 22:28:56.
Backup completed on 2009-09-23 at 22:30:22.

Backup Set Summary
Backed up 1998 files in 78 directories.
Processed 266357856 bytes in  1 minute and  26 seconds.
Throughput rate: 177 MB/min

 

 

 


Server - se01sw02.corp.ads
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3695 <--> 10.90.10.31:4653

Database Consistency Checks
Consistency checking ADFScala51
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ISQD_ScalaDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ISQDSystemDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking master
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking model
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking msdb
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking Northwind
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking pubs
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ScalaDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ScaSystemDB
Consistency Check including Indexes.
Consistency check was completed.

 


Set Information - se01sw02.corp.ads  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "se01sw02.corp.ads "
Backup set #4 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back up entire database or filegroup
Microsoft SQL Server Agent: Started

 


Backup started on 2009-09-23 at 22:33:57.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 22:41:46.

Backup Set Summary
Backed up 10 databases
Processed 9 348 045 463 bytes in  7 minutes and  49 seconds.
Throughput rate: 1141 MB/min

 

 

Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3729 <--> 10.90.10.31:4674

Set Information - \\se01sw02.corp.ads\C:  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\C: "
Backup set #5 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 22:42:10.
Backup completed on 2009-09-23 at 23:28:56.

Backup Set Summary
Backed up 96302 files in 836 directories.
Processed 10 746 790 078 bytes in  46 minutes and  46 seconds.
Throughput rate: 219 MB/min

 

 


AOFO: Started for resource: "\\se01sw02.corp.ads\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3808 <--> 10.90.10.31:4790

Set Information - \\se01sw02.corp.ads\Shadow?Copy?Components - VSS Writer File System
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\Shadow?Copy?Components  - VSS Writer File System"
Backup set #6 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:29:14.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 23:29:31.

Backup Set Summary
Backed up 2 Shadow Copy Writers
Backed up 2 Shadow Copy Components
Processed 47 547 710 bytes in  17 seconds.
Throughput rate: 160 MB/min

 

 


AOFO: Started for resource: "\\se01sw02.corp.ads\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3811 <--> 10.90.10.31:4805

Set Information - \\se01sw02.corp.ads\System?State \\se01sw02.corp.ads\System?State
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\System?State \\se01sw02.corp.ads\System?State"
Backup set #7 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:29:37.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 23:33:17.

Backup Set Summary
Backed up 8 System State components
Processed 1 151 438 005 bytes in  3 minutes and  40 seconds.
Throughput rate: 299 MB/min

 

 

 


Server - se01sw03.corp.ads
Network control connection is established between 10.90.10.30:3815 <--> 10.90.10.33:10000
Network data connection is established between    10.90.10.30:3821 <--> 10.90.10.33:2164

Set Information - \\se01sw03.corp.ads\E: Mirror
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw03.corp.ads\E: Mirror"
Backup set #8 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:33:25.

Backup Set Detail Information
Drive and media mount requested: 2009-09-24 00:48:04
Media mount failed.
User canceled a Physical Volume Library operation.

V-79-57344-33861 - The media operation was terminated by the user.

 

Backup completed on 2009-09-24 at 06:00:09.

Backup Set Summary
Backed up 28299 files in 3519 directories.
Processed 37 199 010 051 bytes in  1 hour,  14 minutes, and  20 seconds.
Throughput rate: 477 MB/min

 

 

 

 


Job Completion Status
Job ended: den 24 september 2009 at 06:00:09
Completed status: Canceled, timed out
The job was automatically canceled because it
exceeded the job's maximum configured
run time.

 

Errors
Click an error below to locate it in the job log
Backup- \\se01sw03.corp.ads\E: MirrorMedia mount failed.
User canceled a Physical Volume Library operation.
V-79-57344-33861 - The media operation was terminated by the user.

Hi there,


I have three servers that i backup them every day to an HP LTO-1 Ultrium. Im using 200GB tape.

The data that im backing up is about 130GB.

I'm monitoring the server remotely and i dont have access to the server remotely because of the company policy so i recieve daily reports about the server status.

Anything wrong i have to go personaly.

I've been recieving following error for the last three days.

Media mount failed.
User cnceled a phisical volume library operation.
v-79-57344-33861.

I'm new to the backup principles. but i did my best to search the problem cause.

I'm suspecting that this error is because of the tape is full. But it also might be a buffer problem since i backup three servers.

if the problem is the tape, then i know the easiest solution is to buy a bigger tape drive. BUT i need to know something before doing that.

Is it possible to use two tapes to backup my data?
If yes, As you will see that i start my backup at 20:00:00. and the backup stop at 6:00 and that means no one can insert the 2nd tape. What is the best practice solution?

Below is the job log:-

Job Log for Allt


--------------------------------------------------------------------------------


Completed status: Canceled, timed out  
Expand AllCollapse All  


Job Information
Job server: SE01SW01
Job name: Allt
Job started: den 23 september 2009 at 20:00:04
Job type: Backup
Job Log: BEX_SE01SW01_01314.xml

 

Drive and media mount requested: 2009-09-23 20:00:04

No appendable media could be mounted.
Switching to overwrite operation on scratch media.


Device and Media Information
Drive and media information from media mount: 2009-09-23 20:00:21
Drive Name: HP 1
Media Label: LTO000005
Media GUID: {f97857e2-0efa-4db2-95b2-680e4c4786e1}
Overwrite Protected Until: 2009-09-26 20:00:21
Appendable Until: 9999-12-31 01:00:00
Targeted Media Set Name: Tape

All Media Used
 LTO000005

 


Job Operation - Backup  
Backup Options
Media operation - append.
Compression Type: Hardware [if available, otherwise software]

 



Server - SE01SW01

Set Information - E: DATA
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "E: DATA"
Backup set #1 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 20:00:40.
Backup completed on 2009-09-23 at 22:28:06.

Backup Set Summary
Backed up 44197 files in 6530 directories.
Processed 70 154 889 927 bytes in  2 hours,  27 minutes, and  26 seconds.
Throughput rate: 454 MB/min

 

 


Database Consistency Checks
Consistency checking BEDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking master
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking model
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking msdb
Consistency Check including Indexes.
Consistency check was completed.

 


Set Information - SE01SW01\BKUPEXEC  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "SE01SW01\BKUPEXEC "
Backup set #2 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back up entire database or filegroup
Microsoft SQL Server Agent: Started

 


Backup started on 2009-09-23 at 22:28:18.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 22:28:53.

Backup Set Summary
Backed up 4 databases
Processed 29 049 505 bytes in  35 seconds.
Throughput rate: 47.5 MB/min

 

 


Set Information - \\SE01SW01\System?State  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\SE01SW01\System?State "
Backup set #3 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 22:28:56.
Backup completed on 2009-09-23 at 22:30:22.

Backup Set Summary
Backed up 1998 files in 78 directories.
Processed 266357856 bytes in  1 minute and  26 seconds.
Throughput rate: 177 MB/min

 

 

 


Server - se01sw02.corp.ads
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3695 <--> 10.90.10.31:4653

Database Consistency Checks
Consistency checking ADFScala51
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ISQD_ScalaDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ISQDSystemDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking master
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking model
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking msdb
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking Northwind
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking pubs
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ScalaDB
Consistency Check including Indexes.
Consistency check was completed.
Consistency checking ScaSystemDB
Consistency Check including Indexes.
Consistency check was completed.

 


Set Information - se01sw02.corp.ads  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "se01sw02.corp.ads "
Backup set #4 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back up entire database or filegroup
Microsoft SQL Server Agent: Started

 


Backup started on 2009-09-23 at 22:33:57.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 22:41:46.

Backup Set Summary
Backed up 10 databases
Processed 9 348 045 463 bytes in  7 minutes and  49 seconds.
Throughput rate: 1141 MB/min

 

 

Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3729 <--> 10.90.10.31:4674

Set Information - \\se01sw02.corp.ads\C:  
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\C: "
Backup set #5 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 22:42:10.
Backup completed on 2009-09-23 at 23:28:56.

Backup Set Summary
Backed up 96302 files in 836 directories.
Processed 10 746 790 078 bytes in  46 minutes and  46 seconds.
Throughput rate: 219 MB/min

 

 


AOFO: Started for resource: "\\se01sw02.corp.ads\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3808 <--> 10.90.10.31:4790

Set Information - \\se01sw02.corp.ads\Shadow?Copy?Components - VSS Writer File System
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\Shadow?Copy?Components  - VSS Writer File System"
Backup set #6 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:29:14.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 23:29:31.

Backup Set Summary
Backed up 2 Shadow Copy Writers
Backed up 2 Shadow Copy Components
Processed 47 547 710 bytes in  17 seconds.
Throughput rate: 160 MB/min

 

 


AOFO: Started for resource: "\\se01sw02.corp.ads\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between 10.90.10.30:3694 <--> 10.90.10.31:10000
Network data connection is established between    10.90.10.30:3811 <--> 10.90.10.31:4805

Set Information - \\se01sw02.corp.ads\System?State \\se01sw02.corp.ads\System?State
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw02.corp.ads\System?State \\se01sw02.corp.ads\System?State"
Backup set #7 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:29:37.

Backup Set Detail Information

 

Backup completed on 2009-09-23 at 23:33:17.

Backup Set Summary
Backed up 8 System State components
Processed 1 151 438 005 bytes in  3 minutes and  40 seconds.
Throughput rate: 299 MB/min

 

 

 


Server - se01sw03.corp.ads
Network control connection is established between 10.90.10.30:3815 <--> 10.90.10.33:10000
Network data connection is established between    10.90.10.30:3821 <--> 10.90.10.33:2164

Set Information - \\se01sw03.corp.ads\E: Mirror
Backup Set Information
Family Name: "Media created 2009-09-23 20:00:04"
Backup of "\\se01sw03.corp.ads\E: Mirror"
Backup set #8 on storage media #1
Backup set description: "Allt"
Backup Method: Full - Back Up Files - Reset Archive Bit

 


Backup started on 2009-09-23 at 23:33:25.

Backup Set Detail Information
Drive and media mount requested: 2009-09-24 00:48:04
Media mount failed.
User canceled a Physical Volume Library operation.

V-79-57344-33861 - The media operation was terminated by the user.

 

Backup completed on 2009-09-24 at 06:00:09.

Backup Set Summary
Backed up 28299 files in 3519 directories.
Processed 37 199 010 051 bytes in  1 hour,  14 minutes, and  20 seconds.
Throughput rate: 477 MB/min

 

 

 

 


Job Completion Status
Job ended: den 24 september 2009 at 06:00:09
Completed status: Canceled, timed out
The job was automatically canceled because it
exceeded the job's maximum configured
run time.

 

Errors
Click an error below to locate it in the job log
Backup- \\se01sw03.corp.ads\E: MirrorMedia mount failed.
User canceled a Physical Volume Library operation.
V-79-57344-33861 - The media operation was terminated by the user.

[CraigV]

Hi Laith,

If your job spanned 2 tapes, it would automatically eject the tape and prompt for another tape to be put in. You'd see this job on hold under Job Monitor, with a queued state, with a green ? .
Your error is most likely related to the link below. Read it, and it should help you:

http://seer.support.veritas.com/docs/246967.htm

Just make sure you've also run a cleaning tape, and that there are no hardware issues with your tape drive.

[Laith]

Hi Craig,

As you can see from the Backup Log that the backup up process for the first two servers have been completed successfully. That means that there is nothing wrong with the tape neither with the drive.

I cleaned the drive three times.

Any further suggestion?

[CraigV]

Your data size you're backing up and the native size of the tape (130GB vs. 200GB) means you don't need to use 2 tapes.
Next thing to check is that your Remote Agents are all publishing to the backup server, and that the services are running under the correct credentials (local system), and are actually started.

[Laith]

I recieved this backup log yesterday. It is from the first server but its the same error.
Correct me if im wrong, That means its not from the servers its something locally from the program or the tape.

P.S: I used a new tape the day before yesterday.

Completed status: Canceled, timed out

Expand AllCollapse All

Job Information
Job server: SE01SW01 Job name: Allt Job started: den 24 september 2009 at 20:00:00 Job type: Backup Job Log: BEX_SE01SW01_01316.xml

Drive and media mount requested: 2009-09-24 20:00:00

Device and Media Information
Drive and media information from media mount: 2009-09-24 20:00:12 Drive Name: HP 1 Media Label: A Media GUID: {63a0c9fc-dafa-4568-a1c2-310215ebdc43} Overwrite Protected Until: 2009-09-11 04:44:41 Appendable Until: 9999-12-31 01:00:00 Targeted Media Set Name: Tape All Media Used A

Job Operation - Backup

Backup Options Media operation - append. Compression Type: Hardware [if available, otherwise software]   Server - SE01SW01   Set Information - E: DATA Backup Set Information Family Name: "Media created 2009-09-07 20:00:04" Backup of "E: DATA" Backup set #12 on storage media #1 Backup set description: "Allt" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 2009-09-24 at 20:02:24. Backup Set Detail Information Drive and media mount requested: 2009-09-24 20:05:02 Media mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user. Backup completed on 2009-09-25 at 06:00:08. Backup Set Summary Backed up 886 files in 152 directories. Processed 879357591 bytes in 2 minutes and 19 seconds. Throughput rate: 362 MB/min

Job Completion Status
Job ended: den 25 september 2009 at 06:00:08 Completed status: Canceled, timed out The job was automatically canceled because it exceeded the job's maximum configured run time.

Errors
Click an error below to locate it in the job log Backup- E: DATA Media mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user.

[pkh]

I can explain why your first job failed.  Below from your job log (in italics)

Drive and media mount requested: 2009-09-23 20:00:04

No appendable media could be mounted.
Switching to overwrite operation on scratch media.

I presume that the tape in the drive is a new tape, so it do not have any data on it and thus cannot be appended.  The job then switched to overwrite mode.

Device and Media Information
Drive and media information from media mount: 2009-09-23 20:00:21
Drive Name: HP 1
Media Label: LTO000005
Media GUID: {f97857e2-0efa-4db2-95b2-680e4c4786e1}
Overwrite Protected Until: 2009-09-26 20:00:21

Note that your tape is overwrite protected until 2009-09-26.  Presumably you are not using an autoloader, so the job is stuck, it cannot write.  If you check your alerts, there will be prompt to mount a scatch tape.  Without any response, it will time-out.

For your second job,

Media operation - append

If your tape do not have any data on it, the job will not append to tape.

For your job, you should set the it to Overwrite media, under the Device and Media section of the job properties.  Then make sure that the Overwrite Protection property of your media set is set so that when you load the tape it is overwriteable.

_______________________________________

If this solves your problem, please make it as a solution

[Laith]

All what you presumed is correct.
The tape was new and i dont have an autoloader BUT as far as i know (correct me if im wrong) is when you insert a new tape it will first try to overwrite and append if its not working then it will move it to Scratch Media (as a new tape) and then it will start writing on it

I run a Test Run and first it went wrong. I searched for the solution and it tells me to remove the following:-
"Media capacity check to complete individual job" and "Media check" in the propirities of Test Run. After i unchecked these it worked fine.

P.S:
1. The Backup job is set to "Append to media. Overwrite if no appendable media is available".
2. I removed some of the unnecessary data that it was included in the backup and i will see the result today.

Any Further suggestions?

[CraigV]

This part is interesting Laith:

Job ended: den 25 september 2009 at 06:00:08
Completed status: Canceled, timed out
The job was automatically canceled because it 
exceeded the job's maximum configured 
run time.

Under Tools --> Options --> Priority and Availability, you will see a setting called:

Enable automatic cancellation for selection list - Cancel backup job if not completed within: x hours

Just make sure that isn't selected. It could be timing your backups out if it is. By default it should be off, and set explicitly by you.
There doesn't appear to be the same sort of setting on a job, so that is your first point-of-call.

[Laith]

It is.

I traced the job request and start time. As you you can see in the backup log.

The backup started on 2009-09-23 at 23:33:25

Drive and media mount request: 2009-09-24 at 00:48:04
Media mount failed
User canceled a Phisical Volume Library operation.
V-79-57344-33861 - The media operation was terminated by the user.

Backup completed at 6:00:09.

Look at those three times. I think that the backup should have enough time to finish but when the drive and media mount requested at 00:48:00 thats when the error happend.

What do you think?

[pkh]

I don't know why you want to set your job to Append to media. Overwrite if no appendable media is available.  Since you do not have an autoloader, you want to make sure that you have the entire tape available to you, so the job should be set to Overwrite media.  If it is set to append, whatever old data on the tape would not be erased, reducing the tape capacity.

When you say "new tape", did you format or inventory the tape drive after you put it into the tape drive.  If you did not do any of these things, then the tape would not be recognised by BE.  After you put in any tape, go to the Devices tab and click on the tape drive.  The tape label should be shown.  Otherwise, you need to inventory the drive for BE to recognise the tape.

BE does not "move" tape to scratch.  You have to manually associate the tape with the Sratch Media set.  If a tape is associated with a particular media set, then the Overwrite Protection Period setting of the media set applies to the tape.  Go to the media set tab and check which media set is the tape associated to.

To trace your problem, you also got to look at the Alerts to see what are the alerts during the job.

This is what I will do if I am in your situation

1) Change the job to Overwrite media.

2) Put a tape into the tape drive and inventory the drive.

3) Check that the tape in the drive is either associated with Scatch Media or it overwriteable

[Laith]

Hi There,

I bought a new cleaning tape. Cleaned the tape driver several times. Check the backup data. Deleted abuot 30 useless GB. Run the backup and now its working. Do you think that it was the size?

As i said before i had a limit knowledge regarding backup systems. I gave your suggestions a though and you are totaly right. Im going to change to what you have suggested.

Thanks for your help.

[pkh · Accepted solution]

If my solution is correct, shouldn't you mark my suggestion as the solution, rather than your acknowledgement that my solution is correct as the solution.  This way, you are awarding yourself the points for the solution rather than me.

[CraigV]

pkh: You can award yourself the fix, but there are no points involved. It's simply closed off. But you do lose the points.