Sign in
Microsoft.com
 
System Center Configuration Manager TechCenter
 
 
 
System Center Configuration Manager TechCenter > System Center Configuration Manager Forums > Configuration Manager Backup and Recovery > SQL DB does not seem to be backing up..
Ask a questionAsk a question
Search Forums:
 

AnswerSQL DB does not seem to be backing up..

  • Tuesday, November 18, 2008 1:21 AMDan.Dufus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello all,

    I know theres numerous posts about various backup problems/configs but I couldn't find anything referencing my particular problem..

    I have my backup task scheduled to run daily.

    The sms part of it seems to back up fine, however when I check the directory on the SQL server there is only a single file called SQLBackupDocument.xml in there.

    I am trying to do a test restore of sms but am running into some problems and I think I need to get it to spit out the mdb when it does the backup. 

    Also when I did the restore I ticked the 'do not restore db', restored, then restored a manual backup (*.bak) of the database into sql. This 'work' but when I load the console everything is empty, for example, under packages, all my folders are there, but no packages. No collections are present either..

    The backup says it runs successfully so I am at a loss as to where to poke around. 

    Thankyou in advance,

    -Dan
     

Answers

All Replies

  • Monday, December 01, 2008 7:11 PMStan WhiteMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Search for a log file named smssqlbkup.log on the SQL Server.

    Also, verify you have a service called SMS_SITE_SQL_BACKUP_* running and that the 'SQL Server VSS Writer'  is also running.

     

     

     
  • Friday, December 05, 2008 11:58 AMDan.Dufus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Thanks for the reply Stan, I'll try these on Monday and post the results..

    -Dan
     
  • Monday, December 08, 2008 1:47 AMDan.Dufus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hello,

    I have looked at those log files and confirmed those services are running, here is an excerpt of the log..

    The only thing in there that seems strange to me is..

    Number of FileIncludes: 0.
    Number of FileExcludes: 2.

    Otherwise it seems happy with what its done. Just so I'm not missing something, this process IS meant to dump a snapshot of the sql database to the dir specified in the SMS Backup task? I should be expecting a file around ~1gb then. Do you think it would matter that I have relocated the data/logs from their normal location? (theyre sitting on seperate drives, I: and H: I believe)

    Thankyou,

    -Dan

    No message received in the last 30 minutes...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 04:32:53.489 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    We received a message...   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.100 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Message received = Start  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.100 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting Sql backup...   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.100 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    12/08/08 05:00:26 - starting sql backup.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.115 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Sql Writer service is running.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.115 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting VSS initialization...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.131 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting Asynchronous GatherWriterMetadata.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:26.209 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Number of writers that responded: 9.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.834 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Reading SQL Writer metadata...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.881 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Number of FileIncludes: 0.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.896 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Number of FileExcludes: 2.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.896 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Number of Components: 15.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.912 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Component - sms_XXX.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.912 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    FileGroupFile = H:\SMS_XXX\\sms_XXX.mdf [Recursive: no]  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.928 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Volume H:\ (that contains the file) is marked as a candidate for snapshot.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.928 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    FileGroupFile = I:\SMS_XXX\\sms_XXX_log.ldf [Recursive: no]  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.943 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Volume I:\ (that contains the file) is marked as a candidate for snapshot.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:27.943 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    After GatherWriterMetadata SQL Writer status = STABLE.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.037 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting Prepare for backup.   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.037 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Added volume containing H:\to the snapshot set.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.287 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Added volume containing I:\to the snapshot set.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.303 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Starting Asynchronous PrepareForBackup...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.303 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Asynchronous PrepareForBackup finished.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.412 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    After PrepareForBackup SQL Writer status = STABLE.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.490 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Updating the status to [prepare for backup done].  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.506 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Waiting for the Event Notification...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:28.506 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    We received a message...   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.850 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Message received = DoSnapshot  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.850 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting to create the snapshot...   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.850 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting to clean and prepare the backup location.   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.866 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Cleanup and/or preparation done.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.866 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Starting DoSnapshotSet...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:36.881 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Asynchronous DoSnapshotSet finished.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:37.959 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    After DoSnapshotSet SQL Writer status = WAITING_FOR_BACKUP_COMPLETION.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.038 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Updating the status to [snapshot done].  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.053 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Starting the backup complete phase.   $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.053 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Successfully created the backup metadata file - G:\SMSBackup\XXXBackup\SiteDBServer\\SQLBackupDocument.xml  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.069 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Starting asynchronous BackupComplete...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.084 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    ~Info: Asynchronous BackupComplete finished.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.178 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    After BackupComplete SQL Writer status = STABLE.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.256 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Updating the status to [backup completed].  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.272 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    12/08/08 05:00:38 - sql backup completed.  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.319 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    Waiting for the Event Notification...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:00:38.334 2008 E. Australia Standard Time><thread=2540 (0x9EC)>
    No message received in the last 30 minutes...  $$<SMS_SITE_SQL_BACKUP_SMSSERVER><Mon Dec 08 05:32:56.409 2008 E. Australia Standard Time><thread=2540 (0x9EC)>


     
  • Wednesday, December 10, 2008 5:33 PMStan WhiteMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     

    Is there anything in the event log that might help?  The FileExclude looks normal in fact the entire log looks normal except that it happened too quickly.
     
  • Thursday, December 11, 2008 1:03 AMDan.Dufus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    The event log looks fine to me also, except the last was an error, these are the items from the Application log:


    I/O is frozen on database sms_bne. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.

    I/O was resumed on database sms_bne. No user action is required.

    Database backed up. Database: sms_bne, creation date(time): 2008/05/13(22:00:23), pages dumped: 1, first LSN: 42771:228:284, last LSN: 42771:348:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{E3FA50C1-82DF-4401-87E6-52CBCE2129E5}1'}). This is an informational message only. No user action is required.

    SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex). ErrorCode=(288)Attempt to release mutex not owned by caller. . Process=2180. Thread=912. Client. Instance=. VD=.


    System log:

    The Volume Shadow Copy service was successfully sent a start control.

    The Volume Shadow Copy service entered the running state.

    The Microsoft Software Shadow Copy Provider service was successfully sent a start control.

    The Microsoft Software Shadow Copy Provider service entered the running state.

    The Volume Shadow Copy service entered the stopped state.

    The Microsoft Software Shadow Copy Provider service entered the stopped state.


    I am running this backup on the primary site and two child primaries with the same results also. Thankyou for your help,

    -Dan
     
  • Tuesday, December 16, 2008 7:56 PMStan WhiteMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Can you please post smswriter.log as well?

    Stan
     
  • Wednesday, December 17, 2008 4:34 PMStan WhiteMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    At this point you may want to engage support and they can redirect you to SQL or VSS experts as needed.
    Stan
     
  • Thursday, December 18, 2008 6:30 AMDan.Dufus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Hi Stan,

    Sorry for the late reply. Log is below. I couldn't see anything in my limited knowledge and smstrace didn't have any read or yellow lines to indicate something dodgy..


    OnIdentify event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:02:06 AM 6688 (0x1A20)
    SMS Writer 12/18/08 05:02:09 - starting to build the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:09 AM 6688 (0x1A20)
    Successfully included C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN into to the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:10 AM 6688 (0x1A20)
    Successfully included C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\INBOXES into to the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:12 AM 6688 (0x1A20)
    Successfully included C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\LOGS into to the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:13 AM 6688 (0x1A20)
    Successfully included C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\DATA into to the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:14 AM 6688 (0x1A20)
    Successfully included C:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\SRVACCT into to the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:15 AM 6688 (0x1A20)
    Successfully included \\SMSSERVER\HKEY_LOCAL_MACHINE\Software\Microsoft\NAL - C:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat into the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:16 AM 6688 (0x1A20)
    Successfully included \\SMSSERVER\HKEY_LOCAL_MACHINE\Software\Microsoft\SMS - C:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat into the metadata. SMS_SITE_VSS_WRITER 18/12/2008 5:02:17 AM 6688 (0x1A20)
    OnPrepareBackup event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:02:42 AM 6688 (0x1A20)
    The backup task has selected the components in the Sms Writer. SMS_SITE_VSS_WRITER 18/12/2008 5:02:42 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSServer\inboxes. SMS_SITE_VSS_WRITER 18/12/2008 5:02:43 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSServer\Logs. SMS_SITE_VSS_WRITER 18/12/2008 5:02:43 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSServer\data. SMS_SITE_VSS_WRITER 18/12/2008 5:02:44 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSServer\srvacct. SMS_SITE_VSS_WRITER 18/12/2008 5:02:45 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 18/12/2008 5:02:46 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteServer\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 18/12/2008 5:02:47 AM 6688 (0x1A20)
    ComponentName = XXXBackup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_VSS_WRITER 18/12/2008 5:02:47 AM 6688 (0x1A20)
    Successfully exported the \\SMSSERVER\HKEY_LOCAL_MACHINE\Software\Microsoft\NAL to C:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegNAL.dat. SMS_SITE_VSS_WRITER 18/12/2008 5:02:51 AM 6688 (0x1A20)
    Successfully exported the \\SMSSERVER\HKEY_LOCAL_MACHINE\Software\Microsoft\SMS to C:\Program Files\Microsoft Configuration Manager\BackupTemp\SMSbkSiteRegSMS.dat. SMS_SITE_VSS_WRITER 18/12/2008 5:02:54 AM 6688 (0x1A20)
    OnPrepareSnapshot event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:02:58 AM 6688 (0x1A20)
    STATMSG: ID=6829 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=6688 GMTDATE=Wed Dec 17 19:02:59.155 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:02:59 AM 6688 (0x1A20)
    LogEvent(): Successfully logged Event to NT Event Log. (4 - 74 - 1,073,748,653) SMS_SITE_VSS_WRITER 18/12/2008 5:03:00 AM 6688 (0x1A20)
    omEnterMomMaintenanceMode - beginning; parameters reason = 'ConfigMgr 4.00.6221.0000 - Starting - Backup', timeout = 3600. SMS_SITE_VSS_WRITER 18/12/2008 5:03:01 AM 6688 (0x1A20)
    Attempting to call SCOM Maintenance Mode interface. SMS_SITE_VSS_WRITER 18/12/2008 5:03:02 AM 6688 (0x1A20)
    omEnterMomMaintenanceMode - ended; parameters reason = 'ConfigMgr 4.00.6221.0000 - Starting - Backup', timeout = 3600. SMS_SITE_VSS_WRITER 18/12/2008 5:03:08 AM 6688 (0x1A20)
    Mom agent has been successfully put into maintenance mode. SMS_SITE_VSS_WRITER 18/12/2008 5:03:09 AM 6688 (0x1A20)
    Service SMS_SITE_COMPONENT_MANAGER on site system \\SMSSERVER successfully stopped. SMS_SITE_VSS_WRITER 18/12/2008 5:03:18 AM 6688 (0x1A20)
    STATMSG: ID=6805 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=6688 GMTDATE=Wed Dec 17 19:03:19.342 2008 ISTR0="SMS_SITE_COMPONENT_MANAGER" ISTR1="\\SMSSERVER" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:03:19 AM 6688 (0x1A20)
    Service SMS_EXECUTIVE on site system \\SMSSERVER successfully stopped. SMS_SITE_VSS_WRITER 18/12/2008 5:05:01 AM 6688 (0x1A20)
    STATMSG: ID=6805 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=6688 GMTDATE=Wed Dec 17 19:05:01.388 2008 ISTR0="SMS_EXECUTIVE" ISTR1="\\SMSSERVER" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:05:01 AM 6688 (0x1A20)
    OnFreeze event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:05:01 AM 6188 (0x182C)
    OnThaw event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:05:02 AM 6688 (0x1A20)
    OnPostSnapshot event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:05:02 AM 8152 (0x1FD8)
    Waiting for SQL snapshot to complete... SMS_SITE_VSS_WRITER 18/12/2008 5:05:02 AM 8152 (0x1FD8)
    Service SMS_SITE_COMPONENT_MANAGER on site system \\SMSSERVER successfully started. SMS_SITE_VSS_WRITER 18/12/2008 5:05:04 AM 8152 (0x1FD8)
    STATMSG: ID=6807 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=8152 GMTDATE=Wed Dec 17 19:05:04.857 2008 ISTR0="SMS_SITE_COMPONENT_MANAGER" ISTR1="\\SMSSERVER" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:05:04 AM 8152 (0x1FD8)
    STATMSG: ID=6830 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=8152 GMTDATE=Wed Dec 17 19:05:05.076 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    omExitMomMaintenanceMode - beginning. SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    Attempting to call SCOM Maintenance Mode interface. SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    omExitMomMaintenanceMode - ended. SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    Mom agent has been restored from the maintenance mode. SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    LogEvent(): Successfully logged Event to NT Event Log. (4 - 74 - 1,073,748,654) SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    STATMSG: ID=6831 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=8152 GMTDATE=Wed Dec 17 19:05:05.607 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    LogEvent(): Successfully logged Event to NT Event Log. (4 - 74 - 1,073,748,655) SMS_SITE_VSS_WRITER 18/12/2008 5:05:05 AM 8152 (0x1FD8)
    OnBackupComplete event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:26:11 AM 8152 (0x1FD8)
    STATMSG: ID=6833 SEV=I LEV=M SOURCE="SMS Server" COMP="" SYS=SMSSERVER SITE=XXX PID=2220 TID=8152 GMTDATE=Wed Dec 17 19:26:12.099 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_SITE_VSS_WRITER 18/12/2008 5:26:12 AM 8152 (0x1FD8)
    LogEvent(): Successfully logged Event to NT Event Log. (4 - 74 - 1,073,748,657) SMS_SITE_VSS_WRITER 18/12/2008 5:26:12 AM 8152 (0x1FD8)
    OnBackupShutdown event triggerred. SMS_SITE_VSS_WRITER 18/12/2008 5:33:37 AM 8152 (0x1FD8)


    Regarding support I'm not positive where to go for that (there seems to be so many different areas of support..), is there a website you could direct me to with more information or contact details?

    Thankyou muchly,

    -Dan
     
  • Thursday, December 18, 2008 8:40 AMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    You could try this link: http://support.microsoft.com/oas/default.aspx?Gprid=12769
     
  • Thursday, December 18, 2008 11:26 PMStan WhiteMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Probably a phone call to support $$$
     
    Start here please:
    http://support.microsoft.com/ph/2890


    Stan
     
  • Monday, February 23, 2009 10:49 PMOthewise Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    1
    Sign In to Vote

    I spoke with Microsoft Premiere Support and below is a partial copy of the email the support guy sent me:

    "SCCM integrated backup doesnt backup the database on a x64 Windows 2008. This is a known issue and will be fixed in SCCM SP2."

    I'm waiting for confirmation that this is a problem with Windows 2003 x64 as well.  Its funny cause I've had this problem with my last 2 customers (I'm a consultant) and I thought it was something I was doing wrong.  I bet there are lots of people out there who actually have broken backups but never checked to see if the database actually backed up (cause it shows as Backup Successful in all Log files, SQL Logs, Event Viewer Logs and Status Messages).

    We are working on a manual solution to back up the DB with the Site Folders, Files, etc until SP2 or a hotfix comes out.

     
  • Friday, June 12, 2009 4:49 PMBill Fourqurean Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I am experiencing the same problem that you reported. The SQL database is on a separate server running Windows Server 2003 Enterprise 64-bit, and SQL Server 2005 64-bit. I see the last post in thread says that this is a known issue that will be fixed in SP2 for Configuration Manager. Anyone know when that will be out? Is there any other work around except to do your own backup using SQL? Thanks, Bill
     
  • Friday, June 19, 2009 7:01 AMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    "SCCM integrated backup doesnt backup the database on a x64 Windows 2008. This is a known issue and will be fixed in SCCM SP2."

    I've never seen this issue before. ConfigMgr backup works fine for me on Server 2008 x64 (with SQL local or remote).

    @Bill: SP2 is currently in beta (see connect.microsoft.com) and wil be released 90 days after RTM of Win7. A SQL backup won't work, because you have to backup files, registry etc at the same time.
     
  • Thursday, October 15, 2009 6:55 PMBill Fourqurean Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm still having the same problem that I reported in this thread on June 12.  That is, on my central site, where the db is on a separate box running x64 version of SQL 2005, the SQL database fails to back up.  ConfigMgr reports it as a success, but it is a false report.  The ConfigMgr flat files get backed up, but the SQL db folder is empty except for one small xml file.  I see that Torsten says that he has a similar configuration but is not experiencing the problem.  I'm not running Server 2008, so I'm not sure if that matters (I am running Server 2003).  The ConfigMgr site server is running x86 version of Server 2003 and the SQL box is running x64 version of Server 2003.

    I haven't tried opening a support call with Microsoft yet.  That's not very easy to do where I work.  Any other suggestions about a possible fix?  I have tried changing the destination locations for the backup file to an alternate location using a UNC path, and that didn't help.  There are status messages in SQL and in the event log that VSS is kicking in and grabbing a snapshot of the database.  It says that it is writing the backup out to a file, but there ends up being no backup file where it is supposed to be.

    Thanks,

    Bill
     
  • Thursday, October 15, 2009 8:28 PMTorsten [MVP]MVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    What's in smsbkup.log?

    I've already reported the false positive status via connect, because I've seen that in another situation.

     
  • Friday, October 16, 2009 3:36 PMBill Fourqurean Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Everything in smsbkup.log indicates a success, including this line:

    Backup Succeeded  for Component - A11Backup\SiteDBServer\SMSbkSQLDBsite.dat. SMS_SITE_BACKUP 10/15/2009 3:37:43 PM 5092 (0x13E4)

    However, there is no SMSbkSQLDBsite.dat file to be found.  Only a small SQLBackupDocument.xml file is found in the SiteDBServer folder.

    Bill 
     
  • Thursday, October 22, 2009 7:12 PMBill Fourqurean Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote
    I thought that I would reply back and report that I got my issue resolved with help from Microsoft Premier Support.  After escalation, it was noticed that my database name (I used a non-standard db name and pre-created the db in SQL prior to installing SCCM) was called ConfigMgr in SQL Server but SCCM referred to is as CONFIGMGR (all caps).  Apparently there is a VSS component that is case-sensitive that was leading to the failure to complete the backup.  To fix, I had to detach the database and re-attach it using all caps in the name.  Microsoft also said that this is fixed in SP2 for SCCM, which was just released today.

    Bill