Post reply

FULL DB backup job

  • December 31, 2012 at 8:12 am

    #286739

    Hi,

    Full backup job is failing with below error in our production.

    this is a LITESPEED full backup for Sys and User DB. Any one has idea on this error? thanks.

    Executed as user: xyz\xyz. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 3:00:00 AM Progress: 2012-12-31 03:00:01.38 Source: {DFBE0DBF-27DE-4F37-A580-A486C84FB622} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp_ma...".: 100% complete End Progress Error: 2012-12-26 03:00:09.54 Code: 0xC0024104 Source: Back Up SysDB Description: The Execute method on the task returned error code 0x80131501 (An exception occurred while executing a Transact-SQL statement or batch.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:00:00 AM Finished: 3:00:09 AM Elapsed: 9.062 seconds. The package execution failed. The step failed.

  • December 31, 2012 at 8:17 am

    #1572520

    Is there anything in the errorlog at the same time as this error?

    John

  • December 31, 2012 at 8:52 am

    #1572525

    Have you checked on the Quest site for information regarding the error? You might find more information there.

  • December 31, 2012 at 9:12 am

    #1572529

    i found the issue. MSDB data file has 0 growth remaining. It's weird that i see this error now, not time of backup job failure.

    the drive has no space, so i want to add new file on different large drive.

    question is- is it possible to add new file/filegroup system db msdb, if yes is it same process like adding to user db or different? please let me know.

  • December 31, 2012 at 9:20 am

    #1572530

    is the msdb large? I would first of all look to see if any data can be purged from it, in particular backup\restore history, job history, SSIS information, those are the usual culprits.

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

  • December 31, 2012 at 10:35 am

    #1572547

    yes. purged the backup history and resolved the issue. Thanks.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply