Re: Windows SBS (Server 2003) BACKUP SQL Server - FAILS
- From: "Rick V" <rick@xxxxxxxxxxx>
- Date: Fri, 4 Jul 2008 21:39:26 -0700
I do not have a solution for your problem but I have found the best way to backup SharePoint is with stsadm -o export command. You can even use "Microsoft Office SharePoint Designer 2007" to do a restore. I had to completely remove IIS from our SharePoint server (SBS 2003 R2) because of some corruption in the metabase. I use this command below and then because of the size of our site (SQL Database was at 1.5GB) I had to consolidate it into a cab file then I used "SharePoint Designer 2007" to restore the whole site in one clean shot with all the permissions in tact. I used "cabsdk" to make the cab file. (Free download)
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o export -url "https://sharepoint.mydomain.com/"; -filename E:\SPBackup\home -includeusersecurity -cabsize 800 -quiet -nofilecompression
Wish I could have been more help.
Rick
"Joe Robbins" <JoeRobbins@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:B6180116-26A6-462C-B79B-4E9A050A277C@xxxxxxxxxxxxxxxx
We are running Windows Server 2003 SP1 - under MS SBS.
For several months we ran a scheduled Backup at 23:00 each night.
This Backup dumped most of the system to a removeable hard drive.
The Sharepoint & SBSmonitoring databases (integral to SBS) were supported by
(MSDE) SQL Server 8.0.2039.
All was fine (see extract 1below from sql-server log) until we installed
SQL Server Express 9.0.3042 alongside the original MSDE.
Examining the SQL Server logs for each of 3 SQL servers:
1. New Server (SQL Server Express 9.0.3042) runs BACKUP DATABASE command
successfully.
2. Server SBSMonitoring (SQL Server 8.0.2039) fails on BACKUP DATABASE
command (see extract 2 below from sql-server log).
3. Server Sharepoint gets no BACKUP DATABASE command.
Tentative diagnosis:
NTbackup is requesting SQL Server SBSMonitoring, for each database in turn,
to BACKUP DATABASE using a VIRTUAL_DEVICE. SQL Server is unable to pipe to
the virtual device (for some reason yet to be explained) and aborts the
backup. Administrators appear to have no control over this process - other
than initiating the Windows Server Backup.
Suggested remedies tried:
1. We have tried regsvr32 on various .dll - as recommended on the web.
2. We have tried stopping the SBSMonitoring service using command:
net stop SQLAgent$sbsmonitoring
prior to time backup runs. [Logs indicate that this service was halted
successfully but the BACKUP DATABASE still failed.]
3. There are no concurrent backup/VSS operations on the system; we are using
only Microsoft BACKUP, set up from the Server Management application.
Questions:
1 Is this a known problem? There seem to be some postings around this
subject that are left unresolved.
2 Is it OK to co-exist SBS - MSDE with SQL Server Express? Is it possible or
preferable to simply upgrade the installation to SQL Server Express and get
rid of the MSDE?
3 Is there a (n unpublished) command line argument or switch that will
direct NTbackup to not communicate with the SQL Servers? This would enable us
to separately tell the SQL Servers to backup the databases. These backups
would then be transferred by NTbackup to removable media as for any other
file.
4 Anyone got any other suggestions? A week's a long time without being able
to take a dump!
Extract 1: successful backup of SQL Server storing SBSMonitoring [prior to
installation of SQL Server 8.0.2039]:
2008-05-14 23:00:48.95 backup Database backed up: Database:
SBSMonitoring, creation date(time): 2007/08/22(07:54:57), pages dumped: 1,
first LSN: 72174:166:1, last LSN: 72174:170:1, number of dump devices: 1,
device information: (FILE=1, TYPE=VIRTUAL_DEVICE:
{'{DCB9B662-5735-40E9-BCF1-238ABA61FA9D}4'}).
2008-05-14 23:00:49.09 backup Database backed up: Database: model,
creation date(time): 2002/12/17(14:36:05), pages dumped: 1, first LSN:
9:102:1, last LSN: 9:104:1, number of dump devices: 1, device information:
(FILE=1, TYPE=VIRTUAL_DEVICE: {'{DCB9B662-5735-40E9-BCF1-238ABA61FA9D}2'}).
2008-05-14 23:00:49.18 backup Database backed up: Database: msdb,
creation date(time): 2002/12/17(14:41:12), pages dumped: 1, first LSN:
199:31:1, last LSN: 199:34:1, number of dump devices: 1, device information:
(FILE=1, TYPE=VIRTUAL_DEVICE: {'{DCB9B662-5735-40E9-BCF1-238ABA61FA9D}3'}).
2008-05-14 23:00:49.21 backup Database backed up: Database: master,
creation date(time): 2008/05/09(07:47:52), pages dumped: 1, first LSN:
545:120:1, last LSN: 545:122:1, number of dump devices: 1, device
information: (FILE=1, TYPE=VIRTUAL_DEVICE:
{'{DCB9B662-5735-40E9-BCF1-238ABA61FA9D}1'}).
Extract 2: failed backup [post installation of SQL Server 8.0.2039]:
2008-07-02 23:00:36.59 spid52 BackupVirtualDeviceSet::Initialize: Open
failure on backup device '{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}4'. Operating
system error 0x80070002(error not found).
2008-07-02 23:00:36.92 spid51 BackupVirtualDeviceSet::Initialize: Open
failure on backup device '{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}1'. Operating
system error 0x80070002(error not found).
2008-07-02 23:00:37.59 backup BACKUP failed to complete the command
BACKUP DATABASE [SBSMonitoring] TO
VIRTUAL_DEVICE='{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}4' WITH
SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2008-07-02 23:00:52.89 spid54 BackupVirtualDeviceSet::Initialize: Open
failure on backup device '{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}3'. Operating
system error 0x80070002(error not found).
2008-07-02 23:00:37.59 backup BACKUP failed to complete the command
BACKUP DATABASE [master] TO
VIRTUAL_DEVICE='{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}1' WITH
SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2008-07-02 23:00:52.89 backup BACKUP failed to complete the command
BACKUP DATABASE [msdb] TO
VIRTUAL_DEVICE='{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}3' WITH
SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
2008-07-02 23:00:53.42 spid55 BackupVirtualDeviceSet::Initialize: Open
failure on backup device '{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}2'. Operating
system error 0x80070002(error not found).
2008-07-02 23:00:53.42 backup BACKUP failed to complete the command
BACKUP DATABASE [model] TO
VIRTUAL_DEVICE='{83CB2655-5C2B-428C-A3DB-EF18C0753DBD}2' WITH
SNAPSHOT,BUFFERCOUNT=1,BLOCKSIZE=1024
Extract 3: BACKUP Log
03/07/2008 23:00
-------------------------------
Date: 03/07/2008
Time: 23:00
User: SYSTEM
-------------------------------
Backup Runner started.
Launching NTBackup: ntbackup.exe backup "@C:\Program Files\Microsoft Windows
Small Business Server\Backup\Small Business Backup Script.bks" /d "SBS Backup
created on 03/07/2008 at 23:00" /v:yes /r:no /rs:no /hc:off /m normal /j
"Small Business Server Backup Job" /l:s /f "G:\Backup Files\Small Business
Server Backup (03).bkf" /UM
NTBACKUP LOG FILE: C:\Documents and Settings\SBS Backup User\Local
Settings\Application Data\Microsoft\Windows NT\NTBackup\data\backup01.log
=====================<BEGIN NTBACKUP LOG FILE>=====================
Backup Status
Operation: Backup
Active backup destination: File
Media name: "Small Business Server Backup (03).bkf created 03/07/2008 at
23:00"
Volume shadow copy creation: Attempt 1.
"MSDEWriter" has reported an error 0x800423f4. This is part of System State.
The backup cannot continue.
Error returned while creating the volume shadow copy:800423f4
Aborting Backup.
----------------------
The operation did not successfully complete.
----------------------
=======================<END NTBACKUP LOG FILE>=====================
NTBackup finished the backup with errors.
BCS/JR 4 July 2008
.
- References:
- Windows SBS (Server 2003) BACKUP SQL Server - FAILS
- From: Joe Robbins
- Windows SBS (Server 2003) BACKUP SQL Server - FAILS
- Prev by Date: NT Backup
- Next by Date: JRNL_WRAP_ERROR on SBS2003
- Previous by thread: Windows SBS (Server 2003) BACKUP SQL Server - FAILS
- Next by thread: RE: Windows SBS (Server 2003) BACKUP SQL Server - FAILS
- Index(es):
Relevant Pages
|
