Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as well as a BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
Too many drinks I think Rick<g>. Seriously though I have not noticed this before. Is there any chance there is a job that tries to clean out the history without using sp_deletebackuphistory?
Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as well as a BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
|||There is that possibility,
I'm still researching it however. This only happens occasionally, so it is a bit baffling.
I've got 50 or so servers in the hosted environment and only a few of them are experiencing this problem.
All the servers are the same H/W and S/W, service packs etc.
Win 2k Server, SP4, SQL 2k SP3a etc.
I'll keep you posted, meanwhile if anyone else can think of anything...
I've got jobs that run after a restore takes place which ensures that everything in these logs match up (just in case we run into problems like this. ;-))
Rick
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message news:uT3Lwr54EHA.4008@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick<g>. Seriously though I have not noticed this before. Is there any chance there is a job that tries to clean out the history without using sp_deletebackuphistory?
Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as well as a BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
Showing posts with label history. Show all posts
Showing posts with label history. Show all posts
Sunday, February 19, 2012
Backup/Restore History Question
This is a multi-part message in MIME format.
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to = be orphaned records in the RestoreHistory table. (eg. The = RestoreHistory has a record of the restore as well as a BackupSetID = value, however these values cannot be found in the BackupSet and = BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi all,
Occasionally, when I perform a RESTORE = on a database,
The msdb tables are not updated = properly.
The RESTORE functions normally, however = when I run a query against the
BackupSet, BackupMediaFamily and = RestoreHistory tables, there appear to be orphaned records in the RestoreHistory = table. (eg. The RestoreHistory has a record of the restore as well as a = BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however it = does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0009_01C4E35E.2D639B30--This is a multi-part message in MIME format.
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there is a job =that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" wrote in =message news:e7q53A54EHA.1260=@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.
The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory =table. (eg. The RestoreHistory has a record of the restore as well as a =BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however =it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0048_01C4E370.FDF3EB80--|||This is a multi-part message in MIME format.
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
There is that possibility,
I'm still researching it however. This only happens occasionally, so =it is a bit baffling.
I've got 50 or so servers in the hosted environment and only a few of =them are experiencing this problem.
All the servers are the same H/W and S/W, service packs etc.
Win 2k Server, SP4, SQL 2k SP3a etc.
I'll keep you posted, meanwhile if anyone else can think of =anything...
I've got jobs that run after a restore takes place which ensures that =everything in these logs match up (just in case we run into problems =like this. ;-))
Rick
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uT3Lwr54EHA.4008@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against =the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
There is that possibility, =
I'm still researching it =however. This only happens occasionally, so it is a bit baffling.
I've got 50 or so servers in the hosted =environment and only a few of them are experiencing this problem.
All the servers are the same H/W and =S/W, service packs etc.
Win 2k Server, SP4, SQL 2k =SP3a etc.
I'll keep you posted, meanwhile =if anyone else can think of anything...
I've got jobs that run after a restore =takes place which ensures that everything in these logs match up (just in case we =run into problems like this. ;-))
Rick
"Andrew J. Kelly" wrote in message news:uT3Lwr54EHA.4008=@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there =is a job that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" wrote =in message news:e7q53A54EHA.1260=@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.
The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as =well as a BackupSetID value, however these values cannot be found in the =BackupSet and BackupMediaFamily tables.
This is a recurring problem, =however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0034_01C4E36D.A1FD50D0--
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear to = be orphaned records in the RestoreHistory table. (eg. The = RestoreHistory has a record of the restore as well as a BackupSetID = value, however these values cannot be found in the BackupSet and = BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0009_01C4E35E.2D639B30
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi all,
Occasionally, when I perform a RESTORE = on a database,
The msdb tables are not updated = properly.
The RESTORE functions normally, however = when I run a query against the
BackupSet, BackupMediaFamily and = RestoreHistory tables, there appear to be orphaned records in the RestoreHistory = table. (eg. The RestoreHistory has a record of the restore as well as a = BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however it = does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0009_01C4E35E.2D639B30--This is a multi-part message in MIME format.
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0048_01C4E370.FDF3EB80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there is a job =that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell"
Hi all,
Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.
The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory =table. (eg. The RestoreHistory has a record of the restore as well as a =BackupSetID value, however these values cannot be found in the BackupSet and BackupMediaFamily tables.
This is a recurring problem, however =it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0048_01C4E370.FDF3EB80--|||This is a multi-part message in MIME format.
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
There is that possibility,
I'm still researching it however. This only happens occasionally, so =it is a bit baffling.
I've got 50 or so servers in the hosted environment and only a few of =them are experiencing this problem.
All the servers are the same H/W and S/W, service packs etc.
Win 2k Server, SP4, SQL 2k SP3a etc.
I'll keep you posted, meanwhile if anyone else can think of =anything...
I've got jobs that run after a restore takes place which ensures that =everything in these logs match up (just in case we run into problems =like this. ;-))
Rick
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message =news:uT3Lwr54EHA.4008@.TK2MSFTNGP15.phx.gbl...
Too many drinks I think Rick<g>. Seriously though I have not noticed =this before. Is there any chance there is a job that tries to clean out =the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell" <quickening@.msn.com> wrote in message =news:e7q53A54EHA.1260@.TK2MSFTNGP12.phx.gbl...
Hi all,
Occasionally, when I perform a RESTORE on a database,
The msdb tables are not updated properly.
The RESTORE functions normally, however when I run a query against =the
BackupSet, BackupMediaFamily and RestoreHistory tables, there appear =to be orphaned records in the RestoreHistory table. (eg. The =RestoreHistory has a record of the restore as well as a BackupSetID =value, however these values cannot be found in the BackupSet and =BackupMediaFamily tables.
This is a recurring problem, however it does not happen all of the =time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0034_01C4E36D.A1FD50D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
There is that possibility, =
I'm still researching it =however. This only happens occasionally, so it is a bit baffling.
I've got 50 or so servers in the hosted =environment and only a few of them are experiencing this problem.
All the servers are the same H/W and =S/W, service packs etc.
Win 2k Server, SP4, SQL 2k =SP3a etc.
I'll keep you posted, meanwhile =if anyone else can think of anything...
I've got jobs that run after a restore =takes place which ensures that everything in these logs match up (just in case we =run into problems like this. ;-))
Rick
"Andrew J. Kelly"
Too many drinks I think Rick. =Seriously though I have not noticed this before. Is there any chance there =is a job that tries to clean out the history without using sp_deletebackuphistory?
-- Andrew J. Kelly SQL MVP
"Rick Sawtell"
Hi all,
Occasionally, when I perform a =RESTORE on a database,
The msdb tables are not updated =properly.
The RESTORE functions normally, =however when I run a query against the
BackupSet, BackupMediaFamily and =RestoreHistory tables, there appear to be orphaned records in the RestoreHistory table. (eg. The RestoreHistory has a record of the restore as =well as a BackupSetID value, however these values cannot be found in the =BackupSet and BackupMediaFamily tables.
This is a recurring problem, =however it does not happen all of the time.
Do you have any ideas?
TIA
Rick Sawtell
MCT, MCSD, MCDBA
--=_NextPart_000_0034_01C4E36D.A1FD50D0--
Subscribe to:
Posts (Atom)