using arcserve 2000 to backup database receive error in
VDI.log:
2006/10/05 02:03:24 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:43 pid(1312) tid(1892)
Error on DBASQL70TID500VD0
Error at SVDS::Open: Dup(stateEvent) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:45 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: invoked
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: StateEvent Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at TriggerAbort: CompletionSem Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:46 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(State) Status Code: 6, x6
Explanation: The handle is invalid.
2006/10/05 02:03:47 pid(1948) tid(500)
Error on DBASQL70TID500VD0
Error at CVDS::Cleanup: Close(CompleteSem) Status Code: 6, x6
Explanation: The handle is invalid.
MS SQL Server version is 2000.
Pls help. Thanks
Don't have an answer but check out similar post @. http://forums.databasejournal.com/showthread.php?t=40177sql
Showing posts with label backup. Show all posts
Showing posts with label backup. Show all posts
Friday, March 30, 2012
Monday, March 26, 2012
Recataloging a log backup disk file
Backup Log DataBaseName to
DISK='\\ServerName\ShareName\Path\FileName.TRN' with
RetainDays=1, Description='Daily Backup Routine'
When I restore a database and logs to an alternate
server, I can restore the full database backup and the
first iteration of the log backups without any problems.
The problem is with all subsequent log backups that were
performed and apended to the file created by the above
statement. I know and can get to the subsequent appended
logs via TSQL, but not an easy task if there are 15
appended log backups on the device. Is there a way I can
recatalog all the log backups so I can use Enterprise
Manager's point an click interface to restore? Will the
STOPAT parameter restore the first log backup, and all
subsequent backups, up to the STOPAT? The command used
to create the log backup is stated above.
Thanx soo much for your help,
D2David,
> Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore?
Not easily. I guess you can write a TSQL script that uses RESTORE HEADERONLY and based on that
inserts data into the backup history tables in msdb. Note that *this is not supported*! EM has an
option to generate backuphistory as you select a backup device in the restore dialog, but that isn't
dine on a file basis, but on a backup basis, so using EM to generate backuphistory, you would have
to go through that dialog 15 times.
> Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT?
No. All RESTORE commands only addresses one backup at a time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Danh" <anonymous@.discussions.microsoft.com> wrote in message
news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
> Backup Log DataBaseName to
> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
> RetainDays=1, Description='Daily Backup Routine'
> When I restore a database and logs to an alternate
> server, I can restore the full database backup and the
> first iteration of the log backups without any problems.
> The problem is with all subsequent log backups that were
> performed and apended to the file created by the above
> statement. I know and can get to the subsequent appended
> logs via TSQL, but not an easy task if there are 15
> appended log backups on the device. Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore? Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT? The command used
> to create the log backup is stated above.
> Thanx soo much for your help,
> D2
>|||Thanks for the help... I ended up doing this...
RESTORE VERIFYONLY FROM DISK='FilePath' WITH
FILE=#,LOADHISTORY
Replaced the # with 1 2 3 4 5 6 7 ...
I just wish it can be done with one command.
>--Original Message--
>David,
>> Is there a way I can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore?
>Not easily. I guess you can write a TSQL script that
uses RESTORE HEADERONLY and based on that
>inserts data into the backup history tables in msdb.
Note that *this is not supported*! EM has an
>option to generate backuphistory as you select a backup
device in the restore dialog, but that isn't
>dine on a file basis, but on a backup basis, so using EM
to generate backuphistory, you would have
>to go through that dialog 15 times.
>> Will the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT?
>No. All RESTORE commands only addresses one backup at a
time.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"David Danh" <anonymous@.discussions.microsoft.com> wrote
in message
>news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
>> Backup Log DataBaseName to
>> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
>> RetainDays=1, Description='Daily Backup Routine'
>> When I restore a database and logs to an alternate
>> server, I can restore the full database backup and the
>> first iteration of the log backups without any
problems.
>> The problem is with all subsequent log backups that
were
>> performed and apended to the file created by the above
>> statement. I know and can get to the subsequent
appended
>> logs via TSQL, but not an easy task if there are 15
>> appended log backups on the device. Is there a way I
can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore? Will
the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT? The command used
>> to create the log backup is stated above.
>> Thanx soo much for your help,
>> D2
>
>.
>
DISK='\\ServerName\ShareName\Path\FileName.TRN' with
RetainDays=1, Description='Daily Backup Routine'
When I restore a database and logs to an alternate
server, I can restore the full database backup and the
first iteration of the log backups without any problems.
The problem is with all subsequent log backups that were
performed and apended to the file created by the above
statement. I know and can get to the subsequent appended
logs via TSQL, but not an easy task if there are 15
appended log backups on the device. Is there a way I can
recatalog all the log backups so I can use Enterprise
Manager's point an click interface to restore? Will the
STOPAT parameter restore the first log backup, and all
subsequent backups, up to the STOPAT? The command used
to create the log backup is stated above.
Thanx soo much for your help,
D2David,
> Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore?
Not easily. I guess you can write a TSQL script that uses RESTORE HEADERONLY and based on that
inserts data into the backup history tables in msdb. Note that *this is not supported*! EM has an
option to generate backuphistory as you select a backup device in the restore dialog, but that isn't
dine on a file basis, but on a backup basis, so using EM to generate backuphistory, you would have
to go through that dialog 15 times.
> Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT?
No. All RESTORE commands only addresses one backup at a time.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"David Danh" <anonymous@.discussions.microsoft.com> wrote in message
news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
> Backup Log DataBaseName to
> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
> RetainDays=1, Description='Daily Backup Routine'
> When I restore a database and logs to an alternate
> server, I can restore the full database backup and the
> first iteration of the log backups without any problems.
> The problem is with all subsequent log backups that were
> performed and apended to the file created by the above
> statement. I know and can get to the subsequent appended
> logs via TSQL, but not an easy task if there are 15
> appended log backups on the device. Is there a way I can
> recatalog all the log backups so I can use Enterprise
> Manager's point an click interface to restore? Will the
> STOPAT parameter restore the first log backup, and all
> subsequent backups, up to the STOPAT? The command used
> to create the log backup is stated above.
> Thanx soo much for your help,
> D2
>|||Thanks for the help... I ended up doing this...
RESTORE VERIFYONLY FROM DISK='FilePath' WITH
FILE=#,LOADHISTORY
Replaced the # with 1 2 3 4 5 6 7 ...
I just wish it can be done with one command.
>--Original Message--
>David,
>> Is there a way I can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore?
>Not easily. I guess you can write a TSQL script that
uses RESTORE HEADERONLY and based on that
>inserts data into the backup history tables in msdb.
Note that *this is not supported*! EM has an
>option to generate backuphistory as you select a backup
device in the restore dialog, but that isn't
>dine on a file basis, but on a backup basis, so using EM
to generate backuphistory, you would have
>to go through that dialog 15 times.
>> Will the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT?
>No. All RESTORE commands only addresses one backup at a
time.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>http://www.solidqualitylearning.com/
>
>"David Danh" <anonymous@.discussions.microsoft.com> wrote
in message
>news:370101c4a05d$53fc68b0$a501280a@.phx.gbl...
>> Backup Log DataBaseName to
>> DISK='\\ServerName\ShareName\Path\FileName.TRN' with
>> RetainDays=1, Description='Daily Backup Routine'
>> When I restore a database and logs to an alternate
>> server, I can restore the full database backup and the
>> first iteration of the log backups without any
problems.
>> The problem is with all subsequent log backups that
were
>> performed and apended to the file created by the above
>> statement. I know and can get to the subsequent
appended
>> logs via TSQL, but not an easy task if there are 15
>> appended log backups on the device. Is there a way I
can
>> recatalog all the log backups so I can use Enterprise
>> Manager's point an click interface to restore? Will
the
>> STOPAT parameter restore the first log backup, and all
>> subsequent backups, up to the STOPAT? The command used
>> to create the log backup is stated above.
>> Thanx soo much for your help,
>> D2
>
>.
>
Rebuilt master, what's next?
Hello,
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
Many thanks,
Pablo
Hi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo
|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>
>
|||If SQL Server expects a databases's MDF file be in a place, and the file isn't there, you have a suspect
database. Drop it and do a regular restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
Many thanks,
Pablo
Hi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo
|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>
>
|||If SQL Server expects a databases's MDF file be in a place, and the file isn't there, you have a suspect
database. Drop it and do a regular restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
Rebuilt master, what's next?
Hello,
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
--
Many thanks,
PabloHi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
--
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>>Hello,
>>What would be the way to go after rebuilding master database: (1)
>>restore it from the backup, restore msdb, and then user databases or (2)
>>restore user databases, restore master, and then msdb.
>>I mean, is it bad, when the master is restored w/o user databases being
>>accessible?
>>--
>>Many thanks,
>>Pablo
>
>|||If SQL Server expects a databases's MDF file be in a place, and the file isn't there, you have a suspect
database. Drop it and do a regular restore.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
> > Hi,
> >
> > What would be the way to go after rebuilding master database?
> >
> > This is the correct step:- Restore it from the backup (Master) , Restore
> > msdb, and then user databases
> >
> > Have a look into steps (15 - 28) in the attached link.
> >
> > http://www.dbarecovery.com/restoremasterdb.html
> >
> > I mean, is it bad, when the master is restored w/o user databases being
> > accessible?
> >
> > You have to restore the Master database and then the user databases.
> > Otherwise Master database restore will
> > overwrite the existing database entries.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> > news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> >
> >>Hello,
> >>
> >>What would be the way to go after rebuilding master database: (1)
> >>restore it from the backup, restore msdb, and then user databases or (2)
> >>restore user databases, restore master, and then msdb.
> >>
> >>I mean, is it bad, when the master is restored w/o user databases being
> >>accessible?
> >>
> >>--
> >>Many thanks,
> >>Pablo
> >
> >
> >
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
--
Many thanks,
PabloHi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
--
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>>Hello,
>>What would be the way to go after rebuilding master database: (1)
>>restore it from the backup, restore msdb, and then user databases or (2)
>>restore user databases, restore master, and then msdb.
>>I mean, is it bad, when the master is restored w/o user databases being
>>accessible?
>>--
>>Many thanks,
>>Pablo
>
>|||If SQL Server expects a databases's MDF file be in a place, and the file isn't there, you have a suspect
database. Drop it and do a regular restore.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
> > Hi,
> >
> > What would be the way to go after rebuilding master database?
> >
> > This is the correct step:- Restore it from the backup (Master) , Restore
> > msdb, and then user databases
> >
> > Have a look into steps (15 - 28) in the attached link.
> >
> > http://www.dbarecovery.com/restoremasterdb.html
> >
> > I mean, is it bad, when the master is restored w/o user databases being
> > accessible?
> >
> > You have to restore the Master database and then the user databases.
> > Otherwise Master database restore will
> > overwrite the existing database entries.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> > news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> >
> >>Hello,
> >>
> >>What would be the way to go after rebuilding master database: (1)
> >>restore it from the backup, restore msdb, and then user databases or (2)
> >>restore user databases, restore master, and then msdb.
> >>
> >>I mean, is it bad, when the master is restored w/o user databases being
> >>accessible?
> >>
> >>--
> >>Many thanks,
> >>Pablo
> >
> >
> >
Rebuilt master, what's next?
Hello,
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
Many thanks,
PabloHi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>
>
>|||If SQL Server expects a databases's MDF file be in a place, and the file isn
't there, you have a suspect
database. Drop it and do a regular restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
What would be the way to go after rebuilding master database: (1)
restore it from the backup, restore msdb, and then user databases or (2)
restore user databases, restore master, and then msdb.
I mean, is it bad, when the master is restored w/o user databases being
accessible?
Many thanks,
PabloHi,
What would be the way to go after rebuilding master database?
This is the correct step:- Restore it from the backup (Master) , Restore
msdb, and then user databases
Have a look into steps (15 - 28) in the attached link.
http://www.dbarecovery.com/restoremasterdb.html
I mean, is it bad, when the master is restored w/o user databases being
accessible?
You have to restore the Master database and then the user databases.
Otherwise Master database restore will
overwrite the existing database entries.
Thanks
Hari
MCDBA
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
> Hello,
> What would be the way to go after rebuilding master database: (1)
> restore it from the backup, restore msdb, and then user databases or (2)
> restore user databases, restore master, and then msdb.
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> --
> Many thanks,
> Pablo|||Thanks, Hari.
Still, one thing remains unclear to me: what will happen when I restore
master then start the server and user databases aren't where they
supposed to be. Will the references to them in master be automatically
erased or will the databases be marked suspect? Will I have to drop the
suspect databases before restoring them or will I have to use WITH
REPLACE clause to force the restore over the existing (suspect) user
database?
Thanks,
Pablo
Hari wrote:
> Hi,
> What would be the way to go after rebuilding master database?
> This is the correct step:- Restore it from the backup (Master) , Restore
> msdb, and then user databases
> Have a look into steps (15 - 28) in the attached link.
> http://www.dbarecovery.com/restoremasterdb.html
> I mean, is it bad, when the master is restored w/o user databases being
> accessible?
> You have to restore the Master database and then the user databases.
> Otherwise Master database restore will
> overwrite the existing database entries.
> Thanks
> Hari
> MCDBA
>
> "msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
> news:OcAE63nREHA.3052@.TK2MSFTNGP12.phx.gbl...
>
>
>|||If SQL Server expects a databases's MDF file be in a place, and the file isn
't there, you have a suspect
database. Drop it and do a regular restore.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"msnews.microsoft.com" <pablo@.this_isnt_my_mail.aaa> wrote in message
news:uLaYNSvREHA.3628@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Thanks, Hari.
> Still, one thing remains unclear to me: what will happen when I restore
> master then start the server and user databases aren't where they
> supposed to be. Will the references to them in master be automatically
> erased or will the databases be marked suspect? Will I have to drop the
> suspect databases before restoring them or will I have to use WITH
> REPLACE clause to force the restore over the existing (suspect) user
> database?
> --
> Thanks,
> Pablo
> Hari wrote:
Rebuilding Sql Server 2000 from Backups
I am trying to rebuild our server onto another - which will have the
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
Tom
On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for these
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent
|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegr oups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
Tom
On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for these
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent
|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegr oups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>
Rebuilding Sql Server 2000 from Backups
I am trying to rebuild our server onto another - which will have the
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
TomOn Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for the
se
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegroups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>sql
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
TomOn Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for the
se
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegroups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>sql
Rebuilding Sql Server 2000 from Backups
I am trying to rebuild our server onto another - which will have the
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
TomOn Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for these
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegroups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
>> I am trying to rebuild our server onto another - which will have the
>> different name.
>> So I expect the best way to handle this is to just do a backup on the old
>> server for each database and then restore them on the new server.
>> If I go this way do I need to:
>> 1. Create the database first and then do the restore for each database?
>> 2. Re-add the Logons (since the database will have permissions set for
>> these
>> logons). And do I need to create the logons before doing the restores?
>> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
>> will that be taken care of as I restore the databases?
>> Thanks,
>> Tom
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>
different name.
So I expect the best way to handle this is to just do a backup on the old
server for each database and then restore them on the new server.
If I go this way do I need to:
1. Create the database first and then do the restore for each database?
2. Re-add the Logons (since the database will have permissions set for these
logons). And do I need to create the logons before doing the restores?
3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
will that be taken care of as I restore the databases?
Thanks,
TomOn Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
> I am trying to rebuild our server onto another - which will have the
> different name.
> So I expect the best way to handle this is to just do a backup on the old
> server for each database and then restore them on the new server.
> If I go this way do I need to:
> 1. Create the database first and then do the restore for each database?
> 2. Re-add the Logons (since the database will have permissions set for these
> logons). And do I need to create the logons before doing the restores?
> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
> will that be taken care of as I restore the databases?
> Thanks,
> Tom
1. You don't need to create the databases first. Just restore
database will do what you need.
2. You are going to fix the users. If you're going to add teh logins
to the new server you will have something called orpaned users. Take
a look at the Books On Line and read the sp_change_users_login proc
since you will use it to fix the user issue. Of once you restore the
database to new server just delete the user, add the login and add the
user to database.
3. If you don't have a lot of jobs and dts packages I would generate a
sql script for jobs then run them on the new server and just save the
dts packages once you get the new server up to that server. Don't
wory about model it's just model db to create a new database. Leave
the master and msdb out of the process.
Good day,
Bulent|||"Bulent" <bulentgucuk@.gmail.com> wrote in message
news:1177033048.966489.192990@.b75g2000hsg.googlegroups.com...
> On Apr 19, 4:07 pm, "tshad" <t...@.home.com> wrote:
>> I am trying to rebuild our server onto another - which will have the
>> different name.
>> So I expect the best way to handle this is to just do a backup on the old
>> server for each database and then restore them on the new server.
>> If I go this way do I need to:
>> 1. Create the database first and then do the restore for each database?
>> 2. Re-add the Logons (since the database will have permissions set for
>> these
>> logons). And do I need to create the logons before doing the restores?
>> 3. Do I need to backup and restore the Master, Model, Msdb and tempdb or
>> will that be taken care of as I restore the databases?
>> Thanks,
>> Tom
> 1. You don't need to create the databases first. Just restore
> database will do what you need.
> 2. You are going to fix the users. If you're going to add teh logins
> to the new server you will have something called orpaned users. Take
> a look at the Books On Line and read the sp_change_users_login proc
> since you will use it to fix the user issue. Of once you restore the
> database to new server just delete the user, add the login and add the
> user to database.
> 3. If you don't have a lot of jobs and dts packages I would generate a
> sql script for jobs then run them on the new server and just save the
> dts packages once you get the new server up to that server. Don't
> wory about model it's just model db to create a new database. Leave
> the master and msdb out of the process.
I was wondering about the restore process if the Database was not there as
it is not in the list of databases to restore, which makes sense it isn't
there. But you can add the name in the list and it works fine, as you said.
Thanks,
Tom
> Good day,
> Bulent
>
Wednesday, March 21, 2012
rebuild master question
Using SQL 2K
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? Thanks
Fatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? Thanks
Fatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
rebuild master question
Using SQL 2K
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? ThanksFatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? ThanksFatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
rebuild master question
Using SQL 2K
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? ThanksFatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Say i have SQL 2K with SP3a and the latest security patch installed and now
my master goes corrupt but I have a recent master db backup someplace.
If i rebuild master using the rebuildm utility, do i have to install the
SP3a and the security patch again before i try to restore the master db or
should i just restore master next ? Just a lil confused as the restore
master article mentions to ensure that the SQL installation is at the same
version as the master backup before restoring..
btw, what does the rebuilm internally do ? ThanksFatima,
We would strongly advise that you reapply sp3a as well as the hotfixes.
Thanks,
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
rebuild master problem
I want to move sql server from server A to server B.
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..
How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..
|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Server
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> something
>
>
sql
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..
How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..
|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Server
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> something
>
>
sql
rebuild master problem
I want to move sql server from server A to server B.
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Serv
er
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> something
>
>
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Serv
er
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> something
>
>
rebuild master problem
I want to move sql server from server A to server B.
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Server
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> > I want to move sql server from server A to server B.
> > 1. path of system database in server A and server B in diffrent
> > 2. I backup master.dat from server A to restore to server B and to
> something
> > alter and it work fine.
> > 3. I create another copy of master from server A and try to restore to
> > server, fail to restore.
> > restore fail with message
> > Error: 3151, Severity: 21, State: 0.
> > Error: 9001, Severity: 21, State: 1.
> > 4. I have to rebuild the master in server B.. and then restore master.
> > Is this normal.? I mean need to rebuild the master in server B..
>
>
1. path of system database in server A and server B in diffrent
2. I backup master.dat from server A to restore to server B and to something
alter and it work fine.
3. I create another copy of master from server A and try to restore to
server, fail to restore.
restore fail with message
Error: 3151, Severity: 21, State: 0.
Error: 9001, Severity: 21, State: 1.
4. I have to rebuild the master in server B.. and then restore master.
Is this normal.? I mean need to rebuild the master in server B..How many user databases / Logins do you need to move ..?
If it's a small number it may be easier for you to simply install SQL Server
on Server B, restore the user database and create the logins manually.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> I want to move sql server from server A to server B.
> 1. path of system database in server A and server B in diffrent
> 2. I backup master.dat from server A to restore to server B and to
something
> alter and it work fine.
> 3. I create another copy of master from server A and try to restore to
> server, fail to restore.
> restore fail with message
> Error: 3151, Severity: 21, State: 0.
> Error: 9001, Severity: 21, State: 1.
> 4. I have to rebuild the master in server B.. and then restore master.
> Is this normal.? I mean need to rebuild the master in server B..|||more then 15 db, more then 50 users..
"John Smith" wrote:
> How many user databases / Logins do you need to move ..?
> If it's a small number it may be easier for you to simply install SQL Server
> on Server B, restore the user database and create the logins manually.
>
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:DFB62E1F-E079-4CAD-ADBF-2A6AF6BCD820@.microsoft.com...
> > I want to move sql server from server A to server B.
> > 1. path of system database in server A and server B in diffrent
> > 2. I backup master.dat from server A to restore to server B and to
> something
> > alter and it work fine.
> > 3. I create another copy of master from server A and try to restore to
> > server, fail to restore.
> > restore fail with message
> > Error: 3151, Severity: 21, State: 0.
> > Error: 9001, Severity: 21, State: 1.
> > 4. I have to rebuild the master in server B.. and then restore master.
> > Is this normal.? I mean need to rebuild the master in server B..
>
>
Tuesday, March 20, 2012
rebuild a database from backupfile only?
Hi NG,
in case this is not the right news group, please advise me to the right one
for my question.
How can I rebuild a database from a plain backup?
Here is my problem:
From within a C# Program I am generating backups of my database by sending
the following sql commands:
BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete
backup, SKIP, NOREWIND, NOUNLOAD, STATS = 10"
as well as:
BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME
= N'OekoTemp-Transaktionsprotokoll backup', SKIP,
NOREWIND, NOUNLOAD, STATS = 10
This works fine, and I am able to do a restore from within my C# program by
sending the sql command:
RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
But if the original .mdf and .log files are deleted, I can no longer do a
restore. Not by my program, and not by the SQL SERVER MANAGEMENT STUDIO.
When ever and how ever I try to restore my database from the plain backup I
receive error messages like (translated from german):
The backup set contains backups for a other database as the present
'OekoTemp'-Database.
Message 3013, Level 16, Status 1, Line 1
RESTORE DATABASE terminated due to errors.
As said : the OekoTemp-Database is not existing any more at all so how can
it be present like mentioned in the error message?
Thanks for any help and hints!
Rainer QueckRainer Queck wrote:
> Hi NG,
> in case this is not the right news group, please advise me to the right one
> for my question.
> How can I rebuild a database from a plain backup?
> Here is my problem:
> From within a C# Program I am generating backups of my database by sending
> the following sql commands:
> BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
> DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete
> backup, SKIP, NOREWIND, NOUNLOAD, STATS = 10"
> as well as:
> BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME
> = N'OekoTemp-Transaktionsprotokoll backup', SKIP,
> NOREWIND, NOUNLOAD, STATS = 10
> This works fine, and I am able to do a restore from within my C# program by
> sending the sql command:
> RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
> But if the original .mdf and .log files are deleted, I can no longer do a
> restore. Not by my program, and not by the SQL SERVER MANAGEMENT STUDIO.
> When ever and how ever I try to restore my database from the plain backup I
> receive error messages like (translated from german):
> The backup set contains backups for a other database as the present
> 'OekoTemp'-Database.
> Message 3013, Level 16, Status 1, Line 1
> RESTORE DATABASE terminated due to errors.
> As said : the OekoTemp-Database is not existing any more at all so how can
> it be present like mentioned in the error message?
> Thanks for any help and hints!
> Rainer Queck
>
>
Hi Rainer,
If a database with the name "OekoTemp" doesn't exists, there shouldn't
be a problem in restoring it with the command you issue. You say that
the original mdf and ldf files doesn't exists, but does that mean that
the files has been deleted manually but the database still exists in SQL
server?
If the database exists and you'd like to restore the backup to this
database, you'll have to use the REPLACE option of the restore command.
I'll suggest that you read up on the RESTORE DATABASE command/syntax in
Books On Line - that will hopefully help you.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||In addition, study RESTORE FILELISTONLY and RESTORE HEADERONLY.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
""Steen Schlüter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in message
news:ePsOMaFbHHA.3616@.TK2MSFTNGP05.phx.gbl...
> Rainer Queck wrote:
>> Hi NG,
>> in case this is not the right news group, please advise me to the right one for my question.
>> How can I rebuild a database from a plain backup?
>> Here is my problem:
>> From within a C# Program I am generating backups of my database by sending the following sql
>> commands:
>> BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
>> DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete backup, SKIP, NOREWIND,
>> NOUNLOAD, STATS = 10"
>> as well as:
>> BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME =>> N'OekoTemp-Transaktionsprotokoll backup', SKIP,
>> NOREWIND, NOUNLOAD, STATS = 10
>> This works fine, and I am able to do a restore from within my C# program by sending the sql
>> command:
>> RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1, NORECOVERY, REPLACE,
>> NOUNLOAD, STATS = 10
>> But if the original .mdf and .log files are deleted, I can no longer do a restore. Not by my
>> program, and not by the SQL SERVER MANAGEMENT STUDIO.
>> When ever and how ever I try to restore my database from the plain backup I receive error
>> messages like (translated from german):
>> The backup set contains backups for a other database as the present 'OekoTemp'-Database.
>> Message 3013, Level 16, Status 1, Line 1
>> RESTORE DATABASE terminated due to errors.
>> As said : the OekoTemp-Database is not existing any more at all so how can it be present like
>> mentioned in the error message?
>> Thanks for any help and hints!
>> Rainer Queck
>>
> Hi Rainer,
> If a database with the name "OekoTemp" doesn't exists, there shouldn't be a problem in restoring
> it with the command you issue. You say that the original mdf and ldf files doesn't exists, but
> does that mean that the files has been deleted manually but the database still exists in SQL
> server?
> If the database exists and you'd like to restore the backup to this database, you'll have to use
> the REPLACE option of the restore command.
> I'll suggest that you read up on the RESTORE DATABASE command/syntax in Books On Line - that will
> hopefully help you.
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator|||Hello Steen,
thanks for your fast reply!
I didn't expect a answer that fast, since I have the same question placed in
a german ng since 4 days without a answer.
""Steen Schlüter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> schrieb im
Newsbeitrag news:ePsOMaFbHHA.3616@.TK2MSFTNGP05.phx.gbl...
> If a database with the name "OekoTemp" doesn't exists, there shouldn't be
> a problem in restoring it with the command you issue. You say that the
> original mdf and ldf files doesn't exists, but does that mean that the
> files has been deleted manually but the database still exists in SQL
> server?
Yes and no. My intention is to backup my database in intervals and then by
program execute a script which drops / creates my database.
This way I get backups for certain periods in time. Then if it is necessary
to load a "old" database I thought I could do a "backup current restore old
database".
Well this did not (yet) work. So I manually deletet my database in SQL
SERVER 2005 and then deleted the database files, hoping to be able to now do
a restore of the old database. This did not work (Yet) and I received the
errormessages mentioned before.
> If the database exists and you'd like to restore the backup to this
> database, you'll have to use the REPLACE option of the restore command.
> I'll suggest that you read up on the RESTORE DATABASE command/syntax in
> Books On Line - that will hopefully help you.
Thanks for the hints. But as you can see by my original post, I am using the
REPLACE option on my restore efforts, but may be there is still a wrong
selection of options in my sql?
Regards
Rainer Queck|||Hi Tibor,
thanks for the additional hint.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> schrieb
im Newsbeitrag news:%23xCFMfFbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> In addition, study RESTORE FILELISTONLY and RESTORE HEADERONLY.
How would the complete SQL string look like for my case?
Since the project I am working on is a weekend project, I won't be able to
continue with my tries before saturday.
Also the current database is not yet important since the project is under
developement and I am currently working with test data and therefore a
dataloss is not yet a pain ;-)
Still it would be great, if I could get this problem solved soon.
Regards
Rainer|||Hello Rainer,
I understand that you cannot restore a database when the existing mdf/ldf
is remmoved and the database does not exist on the server. If I'm off-base,
please let me know.
You may first run fist command:
restore headeronly FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak'
Please see the Databasename in the result, and this shall be the database
name you use in restore command. Please double check the name is correct.
From the error message you encounter, it seems the database name is not
correct in your restore command
In my sample, it is dbacc. If run the command you mentioned, you may see
the following error message:
RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf"
failed with the operating system error 3(The system cannot find the path
specified.).
Msg 3156, Level 16, State 3, Line 1
File 'dbacc' cannot be restored to
'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf'. Use WITH MOVE to identify a
valid location for the file.
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf"
failed with the operating system error 3(The system cannot find the path
specified.).
Msg 3156, Level 16, State 3, Line 1
File 'dbacc_log' cannot be restored to
'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf'. Use WITH MOVE to identify a
valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous
messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
If so, you need to use "with move" statmend in restore command. For example:
RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10,
move 'dbacc' to 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.mdf',
move 'dbacc_log' to 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc_log.ldf'
If the issue still occurs, it might be the backup file is corrupted. You
may want to try a new backup/restore to test. Also, you may want to test
directly in QA or mangement studio(2005) to see if there is any difference
More related informaiton:
Moving SQL Server 7.0 databases to a new server with BACKUP and RESTORE
http://support.microsoft.com/kb/304692/
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Please let's know if you have any further questions or concerns. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Peter,
thank you very much for your detailed answer.
I will follow your suggestions as soon as I continue work on my project
(saturday) and let you know if I was successful or need more help.
Considering the answers I have up to now, there is hope ;-)
Regards
Rainer
"Peter Yang [MSFT]" <petery@.online.microsoft.com> schrieb im Newsbeitrag
news:bYXod$GbHHA.552@.TK2MSFTNGHUB02.phx.gbl...
> Hello Rainer,
> I understand that you cannot restore a database when the existing mdf/ldf
> is remmoved and the database does not exist on the server. If I'm
> off-base,
> please let me know.
> You may first run fist command:
> restore headeronly FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak'
>
> Please see the Databasename in the result, and this shall be the database
> name you use in restore command. Please double check the name is correct.
> From the error message you encounter, it seems the database name is not
> correct in your restore command
>
> In my sample, it is dbacc. If run the command you mentioned, you may see
> the following error message:
> RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
>
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf"
> failed with the operating system error 3(The system cannot find the path
> specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'dbacc' cannot be restored to
> 'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file
> "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf"
> failed with the operating system error 3(The system cannot find the path
> specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'dbacc_log' cannot be restored to
> 'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement.
> Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
> If so, you need to use "with move" statmend in restore command. For
> example:
>
> RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10,
> move 'dbacc' to 'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.mdf',
> move 'dbacc_log' to 'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc_log.ldf'
> If the issue still occurs, it might be the backup file is corrupted. You
> may want to try a new backup/restore to test. Also, you may want to test
> directly in QA or mangement studio(2005) to see if there is any difference
> More related informaiton:
>
> Moving SQL Server 7.0 databases to a new server with BACKUP and RESTORE
> http://support.microsoft.com/kb/304692/
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL
> Server
> http://support.microsoft.com/?id=314546
> Please let's know if you have any further questions or concerns. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rainer,
Please feel free to post back if you have any update. :-)
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Peter,
thank you very much for your help!
Following your advise I can now (re)generate a database completely from just
a backupfile.
Doing these 4 step give me exactly what I need:
DROP DATABASE OekoTemp
GO
restore headeronly FROM DISK = N'<backupfile>'
GO
RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
GO
RESTORE LOG [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 2, NOUNLOAD,
STATS = 10
Regards
Rainer Queck
in case this is not the right news group, please advise me to the right one
for my question.
How can I rebuild a database from a plain backup?
Here is my problem:
From within a C# Program I am generating backups of my database by sending
the following sql commands:
BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete
backup, SKIP, NOREWIND, NOUNLOAD, STATS = 10"
as well as:
BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME
= N'OekoTemp-Transaktionsprotokoll backup', SKIP,
NOREWIND, NOUNLOAD, STATS = 10
This works fine, and I am able to do a restore from within my C# program by
sending the sql command:
RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
But if the original .mdf and .log files are deleted, I can no longer do a
restore. Not by my program, and not by the SQL SERVER MANAGEMENT STUDIO.
When ever and how ever I try to restore my database from the plain backup I
receive error messages like (translated from german):
The backup set contains backups for a other database as the present
'OekoTemp'-Database.
Message 3013, Level 16, Status 1, Line 1
RESTORE DATABASE terminated due to errors.
As said : the OekoTemp-Database is not existing any more at all so how can
it be present like mentioned in the error message?
Thanks for any help and hints!
Rainer QueckRainer Queck wrote:
> Hi NG,
> in case this is not the right news group, please advise me to the right one
> for my question.
> How can I rebuild a database from a plain backup?
> Here is my problem:
> From within a C# Program I am generating backups of my database by sending
> the following sql commands:
> BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
> DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete
> backup, SKIP, NOREWIND, NOUNLOAD, STATS = 10"
> as well as:
> BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME
> = N'OekoTemp-Transaktionsprotokoll backup', SKIP,
> NOREWIND, NOUNLOAD, STATS = 10
> This works fine, and I am able to do a restore from within my C# program by
> sending the sql command:
> RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
> But if the original .mdf and .log files are deleted, I can no longer do a
> restore. Not by my program, and not by the SQL SERVER MANAGEMENT STUDIO.
> When ever and how ever I try to restore my database from the plain backup I
> receive error messages like (translated from german):
> The backup set contains backups for a other database as the present
> 'OekoTemp'-Database.
> Message 3013, Level 16, Status 1, Line 1
> RESTORE DATABASE terminated due to errors.
> As said : the OekoTemp-Database is not existing any more at all so how can
> it be present like mentioned in the error message?
> Thanks for any help and hints!
> Rainer Queck
>
>
Hi Rainer,
If a database with the name "OekoTemp" doesn't exists, there shouldn't
be a problem in restoring it with the command you issue. You say that
the original mdf and ldf files doesn't exists, but does that mean that
the files has been deleted manually but the database still exists in SQL
server?
If the database exists and you'd like to restore the backup to this
database, you'll have to use the REPLACE option of the restore command.
I'll suggest that you read up on the RESTORE DATABASE command/syntax in
Books On Line - that will hopefully help you.
--
Regards
Steen Schlüter Persson
Database Administrator / System Administrator|||In addition, study RESTORE FILELISTONLY and RESTORE HEADERONLY.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
""Steen Schlüter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> wrote in message
news:ePsOMaFbHHA.3616@.TK2MSFTNGP05.phx.gbl...
> Rainer Queck wrote:
>> Hi NG,
>> in case this is not the right news group, please advise me to the right one for my question.
>> How can I rebuild a database from a plain backup?
>> Here is my problem:
>> From within a C# Program I am generating backups of my database by sending the following sql
>> commands:
>> BACKUP DATABASE [OekoTemp] FILEGROUP = N'PRIMARY' TO
>> DISK = N'<backupfile>' WITH NOFORMAT, NOINIT, NAME = N'OekoTemp-Complete backup, SKIP, NOREWIND,
>> NOUNLOAD, STATS = 10"
>> as well as:
>> BACKUP LOG [OekoTemp] TO DISK = N'<backupfile' WITH NORECOVERY, NOINIT, NAME =>> N'OekoTemp-Transaktionsprotokoll backup', SKIP,
>> NOREWIND, NOUNLOAD, STATS = 10
>> This works fine, and I am able to do a restore from within my C# program by sending the sql
>> command:
>> RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1, NORECOVERY, REPLACE,
>> NOUNLOAD, STATS = 10
>> But if the original .mdf and .log files are deleted, I can no longer do a restore. Not by my
>> program, and not by the SQL SERVER MANAGEMENT STUDIO.
>> When ever and how ever I try to restore my database from the plain backup I receive error
>> messages like (translated from german):
>> The backup set contains backups for a other database as the present 'OekoTemp'-Database.
>> Message 3013, Level 16, Status 1, Line 1
>> RESTORE DATABASE terminated due to errors.
>> As said : the OekoTemp-Database is not existing any more at all so how can it be present like
>> mentioned in the error message?
>> Thanks for any help and hints!
>> Rainer Queck
>>
> Hi Rainer,
> If a database with the name "OekoTemp" doesn't exists, there shouldn't be a problem in restoring
> it with the command you issue. You say that the original mdf and ldf files doesn't exists, but
> does that mean that the files has been deleted manually but the database still exists in SQL
> server?
> If the database exists and you'd like to restore the backup to this database, you'll have to use
> the REPLACE option of the restore command.
> I'll suggest that you read up on the RESTORE DATABASE command/syntax in Books On Line - that will
> hopefully help you.
> --
> Regards
> Steen Schlüter Persson
> Database Administrator / System Administrator|||Hello Steen,
thanks for your fast reply!
I didn't expect a answer that fast, since I have the same question placed in
a german ng since 4 days without a answer.
""Steen Schlüter Persson (DK)"" <steen@.REMOVE_THIS_asavaenget.dk> schrieb im
Newsbeitrag news:ePsOMaFbHHA.3616@.TK2MSFTNGP05.phx.gbl...
> If a database with the name "OekoTemp" doesn't exists, there shouldn't be
> a problem in restoring it with the command you issue. You say that the
> original mdf and ldf files doesn't exists, but does that mean that the
> files has been deleted manually but the database still exists in SQL
> server?
Yes and no. My intention is to backup my database in intervals and then by
program execute a script which drops / creates my database.
This way I get backups for certain periods in time. Then if it is necessary
to load a "old" database I thought I could do a "backup current restore old
database".
Well this did not (yet) work. So I manually deletet my database in SQL
SERVER 2005 and then deleted the database files, hoping to be able to now do
a restore of the old database. This did not work (Yet) and I received the
errormessages mentioned before.
> If the database exists and you'd like to restore the backup to this
> database, you'll have to use the REPLACE option of the restore command.
> I'll suggest that you read up on the RESTORE DATABASE command/syntax in
> Books On Line - that will hopefully help you.
Thanks for the hints. But as you can see by my original post, I am using the
REPLACE option on my restore efforts, but may be there is still a wrong
selection of options in my sql?
Regards
Rainer Queck|||Hi Tibor,
thanks for the additional hint.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> schrieb
im Newsbeitrag news:%23xCFMfFbHHA.5044@.TK2MSFTNGP05.phx.gbl...
> In addition, study RESTORE FILELISTONLY and RESTORE HEADERONLY.
How would the complete SQL string look like for my case?
Since the project I am working on is a weekend project, I won't be able to
continue with my tries before saturday.
Also the current database is not yet important since the project is under
developement and I am currently working with test data and therefore a
dataloss is not yet a pain ;-)
Still it would be great, if I could get this problem solved soon.
Regards
Rainer|||Hello Rainer,
I understand that you cannot restore a database when the existing mdf/ldf
is remmoved and the database does not exist on the server. If I'm off-base,
please let me know.
You may first run fist command:
restore headeronly FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak'
Please see the Databasename in the result, and this shall be the database
name you use in restore command. Please double check the name is correct.
From the error message you encounter, it seems the database name is not
correct in your restore command
In my sample, it is dbacc. If run the command you mentioned, you may see
the following error message:
RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf"
failed with the operating system error 3(The system cannot find the path
specified.).
Msg 3156, Level 16, State 3, Line 1
File 'dbacc' cannot be restored to
'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf'. Use WITH MOVE to identify a
valid location for the file.
Msg 5133, Level 16, State 1, Line 1
Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf"
failed with the operating system error 3(The system cannot find the path
specified.).
Msg 3156, Level 16, State 3, Line 1
File 'dbacc_log' cannot be restored to
'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf'. Use WITH MOVE to identify a
valid location for the file.
Msg 3119, Level 16, State 1, Line 1
Problems were identified while planning for the RESTORE statement. Previous
messages provide details.
Msg 3013, Level 16, State 1, Line 1
RESTORE DATABASE is terminating abnormally.
If so, you need to use "with move" statmend in restore command. For example:
RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10,
move 'dbacc' to 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc.mdf',
move 'dbacc_log' to 'C:\Program Files\Microsoft SQL
Server\MSSQL.3\MSSQL\Backup\dbacc_log.ldf'
If the issue still occurs, it might be the backup file is corrupted. You
may want to try a new backup/restore to test. Also, you may want to test
directly in QA or mangement studio(2005) to see if there is any difference
More related informaiton:
Moving SQL Server 7.0 databases to a new server with BACKUP and RESTORE
http://support.microsoft.com/kb/304692/
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Please let's know if you have any further questions or concerns. Thanks.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Peter,
thank you very much for your detailed answer.
I will follow your suggestions as soon as I continue work on my project
(saturday) and let you know if I was successful or need more help.
Considering the answers I have up to now, there is hope ;-)
Regards
Rainer
"Peter Yang [MSFT]" <petery@.online.microsoft.com> schrieb im Newsbeitrag
news:bYXod$GbHHA.552@.TK2MSFTNGHUB02.phx.gbl...
> Hello Rainer,
> I understand that you cannot restore a database when the existing mdf/ldf
> is remmoved and the database does not exist on the server. If I'm
> off-base,
> please let me know.
> You may first run fist command:
> restore headeronly FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak'
>
> Please see the Databasename in the result, and this shall be the database
> name you use in restore command. Please double check the name is correct.
> From the error message you encounter, it seems the database name is not
> correct in your restore command
>
> In my sample, it is dbacc. If run the command you mentioned, you may see
> the following error message:
> RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
>
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf"
> failed with the operating system error 3(The system cannot find the path
> specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'dbacc' cannot be restored to
> 'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc.mdf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 5133, Level 16, State 1, Line 1
> Directory lookup for the file
> "E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf"
> failed with the operating system error 3(The system cannot find the path
> specified.).
> Msg 3156, Level 16, State 3, Line 1
> File 'dbacc_log' cannot be restored to
> 'E:\sql2005\MSSQL.1\MSSQL\DATA\dbacc_log.ldf'. Use WITH MOVE to identify a
> valid location for the file.
> Msg 3119, Level 16, State 1, Line 1
> Problems were identified while planning for the RESTORE statement.
> Previous
> messages provide details.
> Msg 3013, Level 16, State 1, Line 1
> RESTORE DATABASE is terminating abnormally.
>
> If so, you need to use "with move" statmend in restore command. For
> example:
>
> RESTORE DATABASE [dbacc] FROM DISK = N'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.bak' WITH FILE = 1,
> NORECOVERY, REPLACE, NOUNLOAD, STATS = 10,
> move 'dbacc' to 'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc.mdf',
> move 'dbacc_log' to 'C:\Program Files\Microsoft SQL
> Server\MSSQL.3\MSSQL\Backup\dbacc_log.ldf'
> If the issue still occurs, it might be the backup file is corrupted. You
> may want to try a new backup/restore to test. Also, you may want to test
> directly in QA or mangement studio(2005) to see if there is any difference
> More related informaiton:
>
> Moving SQL Server 7.0 databases to a new server with BACKUP and RESTORE
> http://support.microsoft.com/kb/304692/
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL
> Server
> http://support.microsoft.com/?id=314546
> Please let's know if you have any further questions or concerns. Thanks.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Rainer,
Please feel free to post back if you have any update. :-)
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello Peter,
thank you very much for your help!
Following your advise I can now (re)generate a database completely from just
a backupfile.
Doing these 4 step give me exactly what I need:
DROP DATABASE OekoTemp
GO
restore headeronly FROM DISK = N'<backupfile>'
GO
RESTORE DATABASE [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 1,
NORECOVERY, REPLACE, NOUNLOAD, STATS = 10
GO
RESTORE LOG [OekoTemp] FROM DISK = N'<backupfile>' WITH FILE = 2, NOUNLOAD,
STATS = 10
Regards
Rainer Queck
Rebuilbm not working
Hello
I have:
Windows 2000 server with SP3, SQL standard SP2
After a NT backup restore I want to use REBUILDM.EXE to create the system databases in order to restore the databases.
I get the error “Rebuild Master failed with error -1:”
I am aware of KB 273572 and I have a copy of the original files into a folder on the server. The files are not “Read-only”
But I get the error. Did some research…no luck.
If you experienced this please let me know.
Thanks a lot
Look at the SQL Server errolog and verify that Shared Memory is loaded. If
not, reboot the machine. Rebuildm makes a shared memory connection so if
shared memory is not loaded it will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have:
Windows 2000 server with SP3, SQL standard SP2
After a NT backup restore I want to use REBUILDM.EXE to create the system databases in order to restore the databases.
I get the error “Rebuild Master failed with error -1:”
I am aware of KB 273572 and I have a copy of the original files into a folder on the server. The files are not “Read-only”
But I get the error. Did some research…no luck.
If you experienced this please let me know.
Thanks a lot
Look at the SQL Server errolog and verify that Shared Memory is loaded. If
not, reboot the machine. Rebuildm makes a shared memory connection so if
shared memory is not loaded it will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Rebuilbm not working
Hello
I have:
Windows 2000 server with SP3, SQL standard SP2
After a NT backup restore I want to use REBUILDM.EXE to create the system da
tabases in order to restore the databases.
I get the error “Rebuild Master failed with error -1:”
I am aware of KB 273572 and I have a copy of the original files into a folde
r on the server. The files are not “Read-only”
But I get the error. Did some research…no luck.
If you experienced this please let me know.
Thanks a lotLook at the SQL Server errolog and verify that Shared Memory is loaded. If
not, reboot the machine. Rebuildm makes a shared memory connection so if
shared memory is not loaded it will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I have:
Windows 2000 server with SP3, SQL standard SP2
After a NT backup restore I want to use REBUILDM.EXE to create the system da
tabases in order to restore the databases.
I get the error “Rebuild Master failed with error -1:”
I am aware of KB 273572 and I have a copy of the original files into a folde
r on the server. The files are not “Read-only”
But I get the error. Did some research…no luck.
If you experienced this please let me know.
Thanks a lotLook at the SQL Server errolog and verify that Shared Memory is loaded. If
not, reboot the machine. Rebuildm makes a shared memory connection so if
shared memory is not loaded it will fail.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Friday, March 9, 2012
Reasons to restore individual file groups.
Hi,
I'm making the decision to not backup file groups and only backup databases (with backkup exec.
I don't see any reason I would have to resore individual file groups.
Does anyone know why I should backup file groups or in what situation I would need to restore individual file groups?Dont know your situation. If a user drops a table(which
typically the cant) you could restore it by itself if its
in its own filegroup.
>--Original Message--
>Hi,
>I'm making the decision to not backup file groups and
only backup databases (with backkup exec.)
>I don't see any reason I would have to resore individual
file groups.
>Does anyone know why I should backup file groups or in
what situation I would need to restore individual file
groups?
>.
>|||Chris,
I assume that you mean that the filegroup restore would help to restore only
that table to an earlier point in time? That is not possible as when you
restore a filegroup, you also have to apply all subsequent transaction log
backups.
However, I should hasten to add, in SQL2K, you can do a PARTIAL restore into
a new database and move that table to the production database. There are
restriction, however, like the primary filegroup has top be part of the
backup.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:b15301c3ecc9$e7651950$a101280a@.phx.gbl...
> Dont know your situation. If a user drops a table(which
> typically the cant) you could restore it by itself if its
> in its own filegroup.
>
> >--Original Message--
> >Hi,
> >I'm making the decision to not backup file groups and
> only backup databases (with backkup exec.)
> >I don't see any reason I would have to resore individual
> file groups.
> >Does anyone know why I should backup file groups or in
> what situation I would need to restore individual file
> groups?
> >.
> >|||Mannie,
The way I look at filegroup backup and restore is that I prefer to avoid it
if I can. If I have a database too large to handle with "regular" backup
methods, then I consider it. Just the fact that your database is toast if
you are missing one log backup taken after the filegroup you have restore
feel a bit scary to me.
I prefer to keep things as simple as possible. You can still use filegroups
and even do filegroup restore from a full backup (possibly using the PARTIAL
option of applicable).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:53DEF63A-8C4A-45A9-A48A-88A19688217D@.microsoft.com...
> Hi,
> I'm making the decision to not backup file groups and only backup
databases (with backkup exec.)
> I don't see any reason I would have to resore individual file groups.
> Does anyone know why I should backup file groups or in what situation I
would need to restore individual file groups?
I'm making the decision to not backup file groups and only backup databases (with backkup exec.
I don't see any reason I would have to resore individual file groups.
Does anyone know why I should backup file groups or in what situation I would need to restore individual file groups?Dont know your situation. If a user drops a table(which
typically the cant) you could restore it by itself if its
in its own filegroup.
>--Original Message--
>Hi,
>I'm making the decision to not backup file groups and
only backup databases (with backkup exec.)
>I don't see any reason I would have to resore individual
file groups.
>Does anyone know why I should backup file groups or in
what situation I would need to restore individual file
groups?
>.
>|||Chris,
I assume that you mean that the filegroup restore would help to restore only
that table to an earlier point in time? That is not possible as when you
restore a filegroup, you also have to apply all subsequent transaction log
backups.
However, I should hasten to add, in SQL2K, you can do a PARTIAL restore into
a new database and move that table to the production database. There are
restriction, however, like the primary filegroup has top be part of the
backup.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"chris" <anonymous@.discussions.microsoft.com> wrote in message
news:b15301c3ecc9$e7651950$a101280a@.phx.gbl...
> Dont know your situation. If a user drops a table(which
> typically the cant) you could restore it by itself if its
> in its own filegroup.
>
> >--Original Message--
> >Hi,
> >I'm making the decision to not backup file groups and
> only backup databases (with backkup exec.)
> >I don't see any reason I would have to resore individual
> file groups.
> >Does anyone know why I should backup file groups or in
> what situation I would need to restore individual file
> groups?
> >.
> >|||Mannie,
The way I look at filegroup backup and restore is that I prefer to avoid it
if I can. If I have a database too large to handle with "regular" backup
methods, then I consider it. Just the fact that your database is toast if
you are missing one log backup taken after the filegroup you have restore
feel a bit scary to me.
I prefer to keep things as simple as possible. You can still use filegroups
and even do filegroup restore from a full backup (possibly using the PARTIAL
option of applicable).
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:53DEF63A-8C4A-45A9-A48A-88A19688217D@.microsoft.com...
> Hi,
> I'm making the decision to not backup file groups and only backup
databases (with backkup exec.)
> I don't see any reason I would have to resore individual file groups.
> Does anyone know why I should backup file groups or in what situation I
would need to restore individual file groups?
Reasons to restore individual file groups.
Hi,
I'm making the decision to not backup file groups and only backup databases
(with backkup exec.)
I don't see any reason I would have to resore individual file groups.
Does anyone know why I should backup file groups or in what situation I woul
d need to restore individual file groups?Mannie,
The way I look at filegroup backup and restore is that I prefer to avoid it
if I can. If I have a database too large to handle with "regular" backup
methods, then I consider it. Just the fact that your database is toast if
you are missing one log backup taken after the filegroup you have restore
feel a bit scary to me.
I prefer to keep things as simple as possible. You can still use filegroups
and even do filegroup restore from a full backup (possibly using the PARTIAL
option of applicable).
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:53DEF63A-8C4A-45A9-A48A-88A19688217D@.microsoft.com...
> Hi,
> I'm making the decision to not backup file groups and only backup
databases (with backkup exec.)
> I don't see any reason I would have to resore individual file groups.
> Does anyone know why I should backup file groups or in what situation I
would need to restore individual file groups?
I'm making the decision to not backup file groups and only backup databases
(with backkup exec.)
I don't see any reason I would have to resore individual file groups.
Does anyone know why I should backup file groups or in what situation I woul
d need to restore individual file groups?Mannie,
The way I look at filegroup backup and restore is that I prefer to avoid it
if I can. If I have a database too large to handle with "regular" backup
methods, then I consider it. Just the fact that your database is toast if
you are missing one log backup taken after the filegroup you have restore
feel a bit scary to me.
I prefer to keep things as simple as possible. You can still use filegroups
and even do filegroup restore from a full backup (possibly using the PARTIAL
option of applicable).
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"mannie" <anonymous@.discussions.microsoft.com> wrote in message
news:53DEF63A-8C4A-45A9-A48A-88A19688217D@.microsoft.com...
> Hi,
> I'm making the decision to not backup file groups and only backup
databases (with backkup exec.)
> I don't see any reason I would have to resore individual file groups.
> Does anyone know why I should backup file groups or in what situation I
would need to restore individual file groups?
Reason to back up Database master Key?
I can backup this key using something like:
BACKUP MASTER KEY TO FILE = 'c:\TestEncryptionMasterKey.key'
ENCRYPTION BY PASSWORD = '23'
but why would I need to do it as the DBMK is stored in the databases itself ( in sys.symmetric_keys) and we dump all databases nightly. Just "in case"?
TIA,
barkingdog
Yes, we recommend you do this as a recovery measure. If you have a backup of the database anyway, this is less important because the DBMK is also backed up anyway, but this is still good as a precaution. Especially since restoring a DBMK file is a lot less expensive (in terms of server downtime) than restoring a full database backup.
Sung
Subscribe to:
Posts (Atom)