Solved

NT Backup - not completing backup, event 8019

Posted on 2006-07-05
6
676 Views
Last Modified: 2012-05-05
Hallo there,

We have 3 clients with exactly the same problem.  Their ntbackup backs up all their data but gives the error "The requested media failed to mount. The operation was aborted." just before it starts with the system state backup.  The end result is that it shows that the backup failed, but we were able to restore files from the backup so it is working up to the system state backup.
All of the clients have HP DLT VS160 backup drives, except one who has a VS80.
If you look on the Microsoft site they say that this happens when your Exchange database is on your system drive.  In my case the exchange files are all on drive E:.

Please help.
0
Comment
Question by:itcoza
  • 3
  • 3
6 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17043079
The most common reason for this error would be what is described in http://support.microsoft.com/kb/831664

If this is not the case for you, please post an entire Backup Log which contains that error.

Jeff
TechSoEasy
0
 
LVL 13

Author Comment

by:itcoza
ID: 17043205
At the one client I had NTBackup configured with the \um switch.  It worked fine for a long time, then it gave this error for 3 days, on the 4th day it worked fine again.
How do I clear the catalog library?

--------------------------------------------------------------------------------------
Backup Status
Operation: Backup
Active backup destination: DLT
Media name: "Media created 2006/06/29 at 07:00 PM"

Volume shadow copy creation: Attempt 1.
Backup of "Qb_pro"
Backup set #1 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:05 PM.
Warning: Unable to open "\\Annamaria\Qb_pro\qbsdklog.txt" - skipped.
Reason: The process cannot access the file because it is being used by another process.


Backup completed on 2006/06/29 at 07:06 PM.
Directories: 169
Files: 2174
Bytes: 349,226,940
Time:  1 minute and  33 seconds
Backup of "EM_WIN"
Backup set #2 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:06 PM.
Backup completed on 2006/06/29 at 07:06 PM.
Directories: 4
Files: 113
Bytes: 152,334,202
Time:  24 seconds
Backup of "Sandy"
Backup set #3 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:06 PM.
Backup completed on 2006/06/29 at 07:07 PM.
Directories: 9
Files: 191
Bytes: 162,951,411
Time:  31 seconds

Error: \\Sg-term01\Backup is not a valid drive, or you do not have access.

Backup (via shadow copy) of "C: SYS-VOL"
Backup set #4 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:07 PM.
Backup completed on 2006/06/29 at 07:28 PM.
Directories: 3104
Files: 43586
Bytes: 7,641,246,719
Time:  20 minutes and  41 seconds
Backup (via shadow copy) of "D: APPS-VOL"
Backup set #5 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:28 PM.
Backup completed on 2006/06/29 at 07:39 PM.
Directories: 74
Files: 1516
Bytes: 6,498,249,854
Time:  10 minutes and  50 seconds
Backup (via shadow copy) of "E: USER-VOL"
Backup set #6 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 07:39 PM.
Backup completed on 2006/06/29 at 09:52 PM.
Directories: 12562
Files: 135486
Bytes: 84,185,159,056
Time:  2 hours,  13 minutes, and  50 seconds
Backup of "L: \\Sg-term01\Backups"
Backup set #7 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 09:52 PM.
Backup completed on 2006/06/29 at 11:02 PM.
Directories: 1
Files: 4
Bytes: 40,333,905,708
Time:  1 hour,  9 minutes, and  40 seconds
Backup of "M: \\192.168.30.76\em_win"
Backup set #8 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 11:02 PM.
Backup completed on 2006/06/29 at 11:02 PM.
Directories: 4
Files: 113
Bytes: 152,334,202
Time:  25 seconds
Backup of "N: \\192.168.30.55\h_c"
Backup set #9 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 11:02 PM.
Backup completed on 2006/06/29 at 11:03 PM.
Directories: 5
Files: 121
Bytes: 170,527,478
Time:  29 seconds
Backup of "O: \\192.168.30.76\sandy"
Backup set #10 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 11:03 PM.
Backup completed on 2006/06/29 at 11:03 PM.
Directories: 9
Files: 191
Bytes: 162,951,411
Time:  31 seconds
Backup of "SERVER-02\Microsoft Information Store\First Storage Group"
Backup set #11 on media #1
Backup description: "Full Backup set Created on 2006/03/27 at 12:25"
Media name: "Media created 2006/06/29 at 07:00 PM"

Backup Type: Normal

Backup started on 2006/06/29 at 11:03 PM.
The requested media failed to mount. The operation was aborted.
The operation was ended.
Backup completed on 2006/06/29 at 11:12 PM.
Directories: 0
Files: 1
Bytes: 2,493,511,452
Time:  8 minutes and  45 seconds

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

The operation did not successfully complete.

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

0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 17043358
I would highly suggest that you use the built-in SBS Backup for your primary backup process by running the SBS Backup Wizard, and not creating a task manually or through the NTBackup Wizard.  You can then add additional backup jobs as needed... but I find it strange that you have mapped back to IP addresses for user files, rather than having those user files stored on the server.

While these suggestions don't necessarily answer your problem directly, it will help to clean up your backup routine so that you can more easily track down the problem.  One thing I notice is that you are backing up a \backups share which is extremely large... does this need to be backed up each night?

Jeff
TechSoEasy
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 13

Author Comment

by:itcoza
ID: 17048843
Thank you for your suggestion.  I will definitely have to do some cleanup at this specific client.
The problem is that this is only one client who works on NTBackup, the other clients who has this error are all working on the SBS Backup wizard and they only backup the data on the server's hard drives.
I am including one of their backup logs.
----------------------------------------------------------------

05/07/2006 23:00 PM
-------------------------------
Date: 05/07/2006
Time: 23:00 PM
User: SYSTEM
-------------------------------

Backup Runner started.
NTMS session started successfully.
EnumerateNtmsObject(NTMS_LIBRARY) succeeded.
Will enumerate on 3 media libraries found.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
Found an enabled library.
InventoryNtmsLibrary(NtmsInventoryOmid) succeeded.
Identify Media completed
EnumerateNtmsObject(NTMS_PHYSICAL_MEDIA) succeeded.
Will enumerate on 0 media types found.
GetNtmsObjectInformation(NtmsLibraryInfo) succeeded.
Found an enabled library.
InventoryNtmsLibrary(NtmsInventoryOmid) succeeded.
Identify Media completed
EnumerateNtmsObject(NTMS_PHYSICAL_MEDIA) succeeded.
Will enumerate on 1 media types found.
GetNtmsObjectInformation(NtmsPhysicalMediaInfo) succeeded.
GetNtmsObjectInformation(NtmsMediaTypeInfo) succeeded.
Found a tape media type in the library (DLT).
Launching NTBackup: ntbackup.exe backup "@G:\SBS-DATA\Backup\Small Business Backup Script.bks" /d "SBS Backup created on 05/07/2006 at 23:00 PM" /v:yes /r:no /rs:no /hc:on /m normal /j "Small Business Server Backup Job" /l:s /p "DLT" /UM
NTBACKUP LOG FILE: C:\Documents and Settings\SBS Backup User\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup04.log
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: DLT
Media name: "Media created 05/07/2006 at 23:00 PM"

Volume shadow copy creation: Attempt 1.
Backup (via shadow copy) of "C: 1.SYS-VOL"
Backup set #1 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 05/07/2006 at 23:07 PM.
Backup completed on 05/07/2006 at 23:30 PM.
Directories: 4297
Files: 77098
Bytes: 10,025,966,286
Time:  22 minutes and  44 seconds
Backup (via shadow copy) of "D: 5.DATA"
Backup set #2 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 05/07/2006 at 23:30 PM.
Backup completed on 06/07/2006 at 01:02 AM.
Directories: 11164
Files: 114746
Bytes: 57,086,548,206
Time:  1 hour,  32 minutes, and  47 seconds
Backup (via shadow copy) of "E: 2.EXCH-VOL"
Backup set #3 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 06/07/2006 at 01:03 AM.
Backup completed on 06/07/2006 at 01:34 AM.
Directories: 258
Files: 3645
Bytes: 8,311,069,626
Time:  31 minutes and  19 seconds
Backup (via shadow copy) of "F: 3.SQL-VOL"
Backup set #4 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 06/07/2006 at 01:34 AM.
Backup completed on 06/07/2006 at 01:37 AM.
Directories: 35
Files: 352
Bytes: 410,567,068
Time:  3 minutes and  22 seconds
Backup (via shadow copy) of "G: 4.CMP-VOL"
Backup set #5 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 06/07/2006 at 01:37 AM.
Backup completed on 06/07/2006 at 03:01 AM.
Directories: 3633
Files: 64287
Bytes: 25,455,697,801
Time:  1 hour,  24 minutes, and  8 seconds
Backup of "SVR001\Microsoft Information Store\First Storage Group"
Backup set #6 on media #1
Backup description: "SBS Backup created on 05/07/2006 at 23:00 PM"
Media name: "Media created 05/07/2006 at 23:00 PM"

Backup Type: Normal

Backup started on 06/07/2006 at 03:01 AM.
The requested media failed to mount. The operation was aborted.
The operation was ended.
Backup completed on 06/07/2006 at 03:13 AM.
Directories: 0
Files: 2
Bytes: 5,775,554,284
Time:  12 minutes and  0 seconds

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

The operation did not successfully complete.

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

=======================<END NTBACKUP LOG FILE>=====================
NTBackup finished the backup with errors.

For more information about failed backups, see the article on troubleshooting your backup at the following Web page: http://go.microsoft.com/fwlink/?LinkId=18414

Backup ended at 06 July 2006 03:14 AM
Backup Runner finished.
0
 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 500 total points
ID: 17049106
Has this ever worked?  I find it curious that you've created an "SBS-DATA" share and have somehow moved the Backup script to that share.  I can't be certain without looking deeper into your event logs, but I'd suspect that would be a problem.  However it's probably not the problem that is causing this error...

Have you applied KB 831664 to this server as I first suggested?

Jeff
TechSoEasy
0
 
LVL 13

Author Comment

by:itcoza
ID: 17178555
Hallo,  The problem seems to have been that we implemented a corrupt fix from MS on rather a few of our client computers and with the guidance of Jeff, and the request to load KB 831664 we have been able to resolve the problem by updating all the patches on the servers from scratch.

Thank you for the assistance.

Regards,
M
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the event you manage a Small Business Server 2003, and you are audited for PCI compliance, there are several changes you must make in order to pass the audit. I can take no credit for discovering any of these fixes or workarounds, but there is no…
The articles for turning off the Client firewall policy on the internet are for SBS 2008 and don't really help for SBS 2011. They actually moved the Client firewall policy. In 2011, the client firewall policy has moved to the SBS computers conta…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question