Showing posts with label logic. Show all posts
Showing posts with label logic. Show all posts

Friday, February 24, 2012

Backup/Restore Tran Log

Hello Experts,
This is my first time that I work with the logic of
Transaction Log Backups/Restores seriously.
--First I made a full backup, then I backup my log in a
file:
BACKUP LOG [TEST_3]
TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH INIT, NAME = N'TEST 3 backup', NOSKIP
--then I wanted to restore this log:
declare @.FilePosition as int
SELECT @.FilePosition = position
FROM msdb..backupset
WHERE database_name = 'TEST_3'
AND type != 'F'
AND backup_set_id = (SELECT MAX(backup_set_id)
FROM msdb..backupset
WHERE database_name
= 'TEST_3')
RESTORE LOG TEST_3
FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH FILE = @.FilePosition
Even though I don't have any other connection in my DB
the error message I get is:
Server: Msg 3101, Level 16, State 1, Line 11
Exclusive access could not be obtained because the
database is in use.
Server: Msg 3013, Level 16, State 1, Line 11
RESTORE LOG is terminating abnormally.
Can you please post a transaction backup/restore example?
Thanks in advance!
Hi,
It seems there is some one connected to your database. Execute sp_who and
check the user connected to the database, either issue KILL SPID from the
query analyzer to kill the user connected or execute the below command just
before the restore:-
Alter database TEST_3 set single_user with rollback immediate
go
Restore command -- Execute
go
Alter database TEST_3 set multi_user
Thanks
Hari
MCDBA
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
> Hello Experts,
> This is my first time that I work with the logic of
> Transaction Log Backups/Restores seriously.
> --First I made a full backup, then I backup my log in a
> file:
> BACKUP LOG [TEST_3]
> TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH INIT, NAME = N'TEST 3 backup', NOSKIP
> --then I wanted to restore this log:
> declare @.FilePosition as int
> SELECT @.FilePosition = position
> FROM msdb..backupset
> WHERE database_name = 'TEST_3'
> AND type != 'F'
> AND backup_set_id = (SELECT MAX(backup_set_id)
> FROM msdb..backupset
> WHERE database_name
> = 'TEST_3')
> RESTORE LOG TEST_3
> FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH FILE = @.FilePosition
> Even though I don't have any other connection in my DB
> the error message I get is:
> Server: Msg 3101, Level 16, State 1, Line 11
> Exclusive access could not be obtained because the
> database is in use.
> Server: Msg 3013, Level 16, State 1, Line 11
> RESTORE LOG is terminating abnormally.
> Can you please post a transaction backup/restore example?
> Thanks in advance!
|||Thanks for the reply, the error insists to appear
I'll try to KILL SPIDs

>--Original Message--
>Hi,
>It seems there is some one connected to your database.
Execute sp_who and
>check the user connected to the database, either issue
KILL SPID from the
>query analyzer to kill the user connected or execute
the below command just
>before the restore:-
>Alter database TEST_3 set single_user with rollback
immediate
>go
>Restore command -- Execute
>go
>Alter database TEST_3 set multi_user
>Thanks
>Hari
>MCDBA
>
>
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
Server\MSSQL\BACKUP\BACKUP[vbcol=seagreen]
example?
>
>.
>

Backup/Restore Tran Log

Hello Experts,
This is my first time that I work with the logic of
Transaction Log Backups/Restores seriously.
--First I made a full backup, then I backup my log in a
file:
BACKUP LOG [TEST_3]
TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH INIT, NAME = N'TEST 3 backup', NOSKIP
--then I wanted to restore this log:
declare @.FilePosition as int
SELECT @.FilePosition = position
FROM msdb..backupset
WHERE database_name = 'TEST_3'
AND type != 'F'
AND backup_set_id = (SELECT MAX(backup_set_id)
FROM msdb..backupset
WHERE database_name
= 'TEST_3')
RESTORE LOG TEST_3
FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH FILE = @.FilePosition
Even though I don't have any other connection in my DB
the error message I get is:
Server: Msg 3101, Level 16, State 1, Line 11
Exclusive access could not be obtained because the
database is in use.
Server: Msg 3013, Level 16, State 1, Line 11
RESTORE LOG is terminating abnormally.
Can you please post a transaction backup/restore example?
Thanks in advance!Hi,
It seems there is some one connected to your database. Execute sp_who and
check the user connected to the database, either issue KILL SPID from the
query analyzer to kill the user connected or execute the below command just
before the restore:-
Alter database TEST_3 set single_user with rollback immediate
go
Restore command -- Execute
go
Alter database TEST_3 set multi_user
Thanks
Hari
MCDBA
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
> Hello Experts,
> This is my first time that I work with the logic of
> Transaction Log Backups/Restores seriously.
> --First I made a full backup, then I backup my log in a
> file:
> BACKUP LOG [TEST_3]
> TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH INIT, NAME = N'TEST 3 backup', NOSKIP
> --then I wanted to restore this log:
> declare @.FilePosition as int
> SELECT @.FilePosition = position
> FROM msdb..backupset
> WHERE database_name = 'TEST_3'
> AND type != 'F'
> AND backup_set_id = (SELECT MAX(backup_set_id)
> FROM msdb..backupset
> WHERE database_name
> = 'TEST_3')
> RESTORE LOG TEST_3
> FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH FILE = @.FilePosition
> Even though I don't have any other connection in my DB
> the error message I get is:
> Server: Msg 3101, Level 16, State 1, Line 11
> Exclusive access could not be obtained because the
> database is in use.
> Server: Msg 3013, Level 16, State 1, Line 11
> RESTORE LOG is terminating abnormally.
> Can you please post a transaction backup/restore example?
> Thanks in advance!|||Thanks for the reply, the error insists to appear
I'll try to KILL SPIDs

>--Original Message--
>Hi,
>It seems there is some one connected to your database.
Execute sp_who and
>check the user connected to the database, either issue
KILL SPID from the
>query analyzer to kill the user connected or execute
the below command just
>before the restore:-
>Alter database TEST_3 set single_user with rollback
immediate
>go
>Restore command -- Execute
>go
>Alter database TEST_3 set multi_user
>Thanks
>Hari
>MCDBA
>
>
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message
>news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
Server\MSSQL\BACKUP\BACKUP[vbcol=seagree
n]
example?[vbcol=seagreen]
>
>.
>

Backup/Restore Tran Log

Hello Experts,
This is my first time that I work with the logic of
Transaction Log Backups/Restores seriously.
--First I made a full backup, then I backup my log in a
file:
BACKUP LOG [TEST_3]
TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH INIT, NAME = N'TEST 3 backup', NOSKIP
--then I wanted to restore this log:
declare @.FilePosition as int
SELECT @.FilePosition = position
FROM msdb..backupset
WHERE database_name = 'TEST_3'
AND type != 'F'
AND backup_set_id = (SELECT MAX(backup_set_id)
FROM msdb..backupset
WHERE database_name
= 'TEST_3')
RESTORE LOG TEST_3
FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
WITH FILE = @.FilePosition
Even though I don't have any other connection in my DB
the error message I get is:
Server: Msg 3101, Level 16, State 1, Line 11
Exclusive access could not be obtained because the
database is in use.
Server: Msg 3013, Level 16, State 1, Line 11
RESTORE LOG is terminating abnormally.
Can you please post a transaction backup/restore example?
Thanks in advance!Hi,
It seems there is some one connected to your database. Execute sp_who and
check the user connected to the database, either issue KILL SPID from the
query analyzer to kill the user connected or execute the below command just
before the restore:-
Alter database TEST_3 set single_user with rollback immediate
go
Restore command -- Execute
go
Alter database TEST_3 set multi_user
Thanks
Hari
MCDBA
"Konstantinos Michas" <anonymous@.discussions.microsoft.com> wrote in message
news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
> Hello Experts,
> This is my first time that I work with the logic of
> Transaction Log Backups/Restores seriously.
> --First I made a full backup, then I backup my log in a
> file:
> BACKUP LOG [TEST_3]
> TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH INIT, NAME = N'TEST 3 backup', NOSKIP
> --then I wanted to restore this log:
> declare @.FilePosition as int
> SELECT @.FilePosition = position
> FROM msdb..backupset
> WHERE database_name = 'TEST_3'
> AND type != 'F'
> AND backup_set_id = (SELECT MAX(backup_set_id)
> FROM msdb..backupset
> WHERE database_name
> = 'TEST_3')
> RESTORE LOG TEST_3
> FROM DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
> WITH FILE = @.FilePosition
> Even though I don't have any other connection in my DB
> the error message I get is:
> Server: Msg 3101, Level 16, State 1, Line 11
> Exclusive access could not be obtained because the
> database is in use.
> Server: Msg 3013, Level 16, State 1, Line 11
> RESTORE LOG is terminating abnormally.
> Can you please post a transaction backup/restore example?
> Thanks in advance!|||Thanks for the reply, the error insists to appear :)
I'll try to KILL SPIDs
>--Original Message--
>Hi,
>It seems there is some one connected to your database.
Execute sp_who and
>check the user connected to the database, either issue
KILL SPID from the
>query analyzer to kill the user connected or execute
the below command just
>before the restore:-
>Alter database TEST_3 set single_user with rollback
immediate
>go
>Restore command -- Execute
>go
>Alter database TEST_3 set multi_user
>Thanks
>Hari
>MCDBA
>
>
>"Konstantinos Michas"
<anonymous@.discussions.microsoft.com> wrote in message
>news:a3c601c43512$0b5aa5b0$a501280a@.phx.gbl...
>> Hello Experts,
>> This is my first time that I work with the logic of
>> Transaction Log Backups/Restores seriously.
>> --First I made a full backup, then I backup my log in a
>> file:
>> BACKUP LOG [TEST_3]
>> TO DISK = N'D:\Microsoft SQL Server\MSSQL\BACKUP\BACKUP
>> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
>> WITH INIT, NAME = N'TEST 3 backup', NOSKIP
>> --then I wanted to restore this log:
>> declare @.FilePosition as int
>> SELECT @.FilePosition = position
>> FROM msdb..backupset
>> WHERE database_name = 'TEST_3'
>> AND type != 'F'
>> AND backup_set_id = (SELECT MAX(backup_set_id)
>> FROM msdb..backupset
>> WHERE database_name
>> = 'TEST_3')
>> RESTORE LOG TEST_3
>> FROM DISK = N'D:\Microsoft SQL
Server\MSSQL\BACKUP\BACKUP
>> TEST_3\LOG\TEST_3_2004-05-08_17-22.bak'
>> WITH FILE = @.FilePosition
>> Even though I don't have any other connection in my DB
>> the error message I get is:
>> Server: Msg 3101, Level 16, State 1, Line 11
>> Exclusive access could not be obtained because the
>> database is in use.
>> Server: Msg 3013, Level 16, State 1, Line 11
>> RESTORE LOG is terminating abnormally.
>> Can you please post a transaction backup/restore
example?
>> Thanks in advance!
>
>.
>

Monday, February 13, 2012

Backup troubles

Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:

> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:

> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>

Backup troubles

Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:
> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>> Hi,
>> I need some help with a logic for a important document I need to create.
>> Its
>> regarding my Backup procedures that require me to test my database
>> backups
>> every 3 months. The problem occurs that I do not have another server to
>> test
>> out the database. So my solution was the following:
>> * Backup DB
>> * Restore DB redirected towards another DB
>> Now the problem is that QA doesnt think that is enough. I noticed that
>> SQL
>> 2005 (starting since SQL 2000) has this option which alot of 3rd party
>> Backup application use (my case backup exec 10d) "consistency check".
>> I am wondering if I set a consistency check at Backup and then at restore
>> with consistency check, could I absolutely prove that both databases are
>> EXACTLY the same.
>> Example using MD5 for comparing 2 files.
>> "Consistency check is the MD5 for the DB"
>> Thank you so much,
>> George S.
>>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:
> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
> > Hi
> >
> > The restoration of the database will only prove that you can backup and
> > restore that backup i.e. the backup was not corrupted. It does not mean to
> > say that the restored database is the one that you backed up i.e. the
> > backup
> > was not subsequently overwritten with a different backup. Therefore the
> > issue
> > is one for protecting the backup and making sure it is not tampered with.
> > A
> > checksum of the backup file may help, but then it doesn't mean that
> > someone
> > has not tampered with where that is stored either!! If checking
> > consistency
> > is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> >
> > HTH
> >
> > John
> >
> > "George Spiro" wrote:
> >
> >> Hi,
> >>
> >> I need some help with a logic for a important document I need to create.
> >> Its
> >> regarding my Backup procedures that require me to test my database
> >> backups
> >> every 3 months. The problem occurs that I do not have another server to
> >> test
> >> out the database. So my solution was the following:
> >>
> >> * Backup DB
> >> * Restore DB redirected towards another DB
> >>
> >> Now the problem is that QA doesnt think that is enough. I noticed that
> >> SQL
> >> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> >> Backup application use (my case backup exec 10d) "consistency check".
> >>
> >> I am wondering if I set a consistency check at Backup and then at restore
> >> with consistency check, could I absolutely prove that both databases are
> >> EXACTLY the same.
> >>
> >> Example using MD5 for comparing 2 files.
> >> "Consistency check is the MD5 for the DB"
> >>
> >> Thank you so much,
> >>
> >> George S.
> >>
> >>
> >>
>
>

Backup troubles

Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.
Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issue
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:

> Hi,
> I need some help with a logic for a important document I need to create. Its
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to test
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>
|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:

> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>

Backup troubles

Hi,
I need some help with a logic for a important document I need to create. Its
regarding my Backup procedures that require me to test my database backups
every 3 months. The problem occurs that I do not have another server to test
out the database. So my solution was the following:
* Backup DB
* Restore DB redirected towards another DB
Now the problem is that QA doesnt think that is enough. I noticed that SQL
2005 (starting since SQL 2000) has this option which alot of 3rd party
Backup application use (my case backup exec 10d) "consistency check".
I am wondering if I set a consistency check at Backup and then at restore
with consistency check, could I absolutely prove that both databases are
EXACTLY the same.
Example using MD5 for comparing 2 files.
"Consistency check is the MD5 for the DB"
Thank you so much,
George S.Hi
The restoration of the database will only prove that you can backup and
restore that backup i.e. the backup was not corrupted. It does not mean to
say that the restored database is the one that you backed up i.e. the backup
was not subsequently overwritten with a different backup. Therefore the issu
e
is one for protecting the backup and making sure it is not tampered with. A
checksum of the backup file may help, but then it doesn't mean that someone
has not tampered with where that is stored either!! If checking consistency
is the same as a DBCC CHECKDB it is not a comparison of the two databases.
HTH
John
"George Spiro" wrote:

> Hi,
> I need some help with a logic for a important document I need to create. I
ts
> regarding my Backup procedures that require me to test my database backups
> every 3 months. The problem occurs that I do not have another server to te
st
> out the database. So my solution was the following:
> * Backup DB
> * Restore DB redirected towards another DB
> Now the problem is that QA doesnt think that is enough. I noticed that SQL
> 2005 (starting since SQL 2000) has this option which alot of 3rd party
> Backup application use (my case backup exec 10d) "consistency check".
> I am wondering if I set a consistency check at Backup and then at restore
> with consistency check, could I absolutely prove that both databases are
> EXACTLY the same.
> Example using MD5 for comparing 2 files.
> "Consistency check is the MD5 for the DB"
> Thank you so much,
> George S.
>
>|||So what exactly is the Check consistency option on SQL 2000 / 2005?
G.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...[vbcol=seagreen]
> Hi
> The restoration of the database will only prove that you can backup and
> restore that backup i.e. the backup was not corrupted. It does not mean to
> say that the restored database is the one that you backed up i.e. the
> backup
> was not subsequently overwritten with a different backup. Therefore the
> issue
> is one for protecting the backup and making sure it is not tampered with.
> A
> checksum of the backup file may help, but then it doesn't mean that
> someone
> has not tampered with where that is stored either!! If checking
> consistency
> is the same as a DBCC CHECKDB it is not a comparison of the two databases.
> HTH
> John
> "George Spiro" wrote:
>|||Hi George
I don't use backup exec so I can not be sure, but the sales literature does
talk about performing DBCC commands, I don't think that it is anything that
will help you, although you may want to check with Symantic directly.
John
"George Spiro" wrote:

> So what exactly is the Check consistency option on SQL 2000 / 2005?
> G.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6D092594-641C-46D3-92ED-78F3D0E13678@.microsoft.com...
>
>