|
|
You're in the
sql server replication
group:error when using log shipping
sql server replication:
I got an error when i run restore job: Database 'some database' is not in Norecovery\standby mode. what it that means? should i set it on database or in entire server?
Where I do it?
[quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... > after you restore your tlogs make sure you use the no_recovery switch so > you can restore more logs. > > -- > RelevantNoise.com - dedicated to mining blogs for business intelligence. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > "Roy Goldhammer" <roy@hotmail.com> wrote in message > news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >> Hello there >> >> I got an error when i run restore job: >> >> Database 'some database' is not in Norecovery\standby mode. >> >> what it that means? should i set it on database or in entire server? >> >> >> > >
Whell HIlary
In my case the name of database is the same and each one of them are in diffrent Server So I did all the part of backup in one server, copy the data and the log backups to second server and run the restore part on second server After that i ran the Log shipping again. and it worked fine without no error. The now is that the database on secondery server is in Restoring mode and cannot be accessible. Whay is that? and this is the situation it should be? [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... > Here is an example: > Create database TestRoy > GO > Create database testRoyShipped > GO > alter database testroy set recovery full > GO > alter database TestRoyShipped set recovery full > GO > backup database TestRoy to disk='c:\TestRoy.bak' > GO > restore database [testroyshipped] > from disk = 'C:\TestRoy.bak' with > move 'TestRoy' to > 'C:\Program Files\Microsoft SQL > Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', > move 'TestRoy_log' to > 'C:\Program Files\Microsoft SQL > Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', > norecovery, replace > go > backup log testroy to disk='c:\testroylog.bak' > GO > restore log testroyshipped from disk='c:\testroylog.bak' with norecovery > GO > -- > RelevantNoise.com - dedicated to mining blogs for business intelligence. > > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > "Roy Goldhammer" <roy@hotmail.com> wrote in message > news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >> Where I do it? >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>> after you restore your tlogs make sure you use the no_recovery switch so >>> you can restore more logs. >>> >>> -- >>> RelevantNoise.com - dedicated to mining blogs for business intelligence. >>> >>> Looking for a SQL Server replication book? >>> http://www.nwsu.com/0974973602.html >>> >>> Looking for a FAQ on Indexing Services/SQL FTS >>> http://www.indexserverfaq.com >>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>> Hello there >>>> >>>> I got an error when i run restore job: >>>> >>>> Database 'some database' is not in Norecovery\standby mode. >>>> >>>> what it that means? should i set it on database or in entire server? >>>> >>>> >>>> >>> >>> >> >> > >
Hello Roy,
In Log Shipping, the secondary server is supposed to be inaccessible. There are two modes of it. One is Norecovery and the other one is Standby. In Norecovery mode, users can not connect to the secondary server database. In Standby mode, users can connect and query the secondary database. But this time, logs can not be merged with the secondary server database unless all users are disconnected. You can not use Database Mirroring' s mirror database as a report server because it is also going to be inaccessible. The only way you can use the mirror server as a report server is to use a database snapshot and update it periodically (you may use jobs for this) If you want to use the secondary server as a report server, then the best is to set up a transactional replication. -- Ekrem Önsoy [quoted text, click to view] "Roy Goldhammer" <roy@hotmail.com> wrote in message
news:ufIEUtX6HHA.5160@TK2MSFTNGP05.phx.gbl... > Whell HIlary > > In my case the name of database is the same and each one of them are in > diffrent Server > > So I did all the part of backup in one server, copy the data and the log > backups to second server and run the restore part on second server > > After that i ran the Log shipping again. and it worked fine without no > error. > > The now is that the database on secondery server is in Restoring mode and > cannot be accessible. > > Whay is that? and this is the situation it should be? > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... >> Here is an example: >> Create database TestRoy >> GO >> Create database testRoyShipped >> GO >> alter database testroy set recovery full >> GO >> alter database TestRoyShipped set recovery full >> GO >> backup database TestRoy to disk='c:\TestRoy.bak' >> GO >> restore database [testroyshipped] >> from disk = 'C:\TestRoy.bak' with >> move 'TestRoy' to >> 'C:\Program Files\Microsoft SQL >> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', >> move 'TestRoy_log' to >> 'C:\Program Files\Microsoft SQL >> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', >> norecovery, replace >> go >> backup log testroy to disk='c:\testroylog.bak' >> GO >> restore log testroyshipped from disk='c:\testroylog.bak' with norecovery >> GO >> -- >> RelevantNoise.com - dedicated to mining blogs for business intelligence. >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> "Roy Goldhammer" <roy@hotmail.com> wrote in message >> news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >>> Where I do it? >>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>>> after you restore your tlogs make sure you use the no_recovery switch >>>> so you can restore more logs. >>>> >>>> -- >>>> RelevantNoise.com - dedicated to mining blogs for business >>>> intelligence. >>>> >>>> Looking for a SQL Server replication book? >>>> http://www.nwsu.com/0974973602.html >>>> >>>> Looking for a FAQ on Indexing Services/SQL FTS >>>> http://www.indexserverfaq.com >>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>>> Hello there >>>>> >>>>> I got an error when i run restore job: >>>>> >>>>> Database 'some database' is not in Norecovery\standby mode. >>>>> >>>>> what it that means? should i set it on database or in entire server? >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
Whell Ekrem
I've canceled the log Shipping secondery side and the server still in restoring level. Also I'm using log shipping for Disaster recovery. Server1 main server and Server2 is secondery server. If server1 has fallen down I will have to use Server2 as replace until Server1 will be on air again. If I understand it as it now server2 will never be usable if i don't cancel the logshipping from server1 (which can't be done if server1 is down) [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:ekLbGyX6HHA.600@TK2MSFTNGP05.phx.gbl... > Hello Roy, > > > In Log Shipping, the secondary server is supposed to be inaccessible. > There are two modes of it. One is Norecovery and the other one is Standby. > > In Norecovery mode, users can not connect to the secondary server > database. > > In Standby mode, users can connect and query the secondary database. But > this time, logs can not be merged with the secondary server database > unless all users are disconnected. > > You can not use Database Mirroring' s mirror database as a report server > because it is also going to be inaccessible. The only way you can use the > mirror server as a report server is to use a database snapshot > and update it periodically (you may use jobs for this) > > If you want to use the secondary server as a report server, then the best > is to set up a transactional replication. > > -- > Ekrem Önsoy > > > > "Roy Goldhammer" <roy@hotmail.com> wrote in message > news:ufIEUtX6HHA.5160@TK2MSFTNGP05.phx.gbl... >> Whell HIlary >> >> In my case the name of database is the same and each one of them are in >> diffrent Server >> >> So I did all the part of backup in one server, copy the data and the log >> backups to second server and run the restore part on second server >> >> After that i ran the Log shipping again. and it worked fine without no >> error. >> >> The now is that the database on secondery server is in Restoring mode and >> cannot be accessible. >> >> Whay is that? and this is the situation it should be? >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... >>> Here is an example: >>> Create database TestRoy >>> GO >>> Create database testRoyShipped >>> GO >>> alter database testroy set recovery full >>> GO >>> alter database TestRoyShipped set recovery full >>> GO >>> backup database TestRoy to disk='c:\TestRoy.bak' >>> GO >>> restore database [testroyshipped] >>> from disk = 'C:\TestRoy.bak' with >>> move 'TestRoy' to >>> 'C:\Program Files\Microsoft SQL >>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', >>> move 'TestRoy_log' to >>> 'C:\Program Files\Microsoft SQL >>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', >>> norecovery, replace >>> go >>> backup log testroy to disk='c:\testroylog.bak' >>> GO >>> restore log testroyshipped from disk='c:\testroylog.bak' with norecovery >>> GO >>> -- >>> RelevantNoise.com - dedicated to mining blogs for business intelligence. >>> >>> Looking for a SQL Server replication book? >>> http://www.nwsu.com/0974973602.html >>> >>> Looking for a FAQ on Indexing Services/SQL FTS >>> http://www.indexserverfaq.com >>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>> news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >>>> Where I do it? >>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>>> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>>>> after you restore your tlogs make sure you use the no_recovery switch >>>>> so you can restore more logs. >>>>> >>>>> -- >>>>> RelevantNoise.com - dedicated to mining blogs for business >>>>> intelligence. >>>>> >>>>> Looking for a SQL Server replication book? >>>>> http://www.nwsu.com/0974973602.html >>>>> >>>>> Looking for a FAQ on Indexing Services/SQL FTS >>>>> http://www.indexserverfaq.com >>>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>>>> Hello there >>>>>> >>>>>> I got an error when i run restore job: >>>>>> >>>>>> Database 'some database' is not in Norecovery\standby mode. >>>>>> >>>>>> what it that means? should i set it on database or in entire server? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >
Correct:
After running the restore section, Just the restore database the database becomes in restoring mode and don't use. His files don't growth and even when i reset the server it still stuck in this mode. The only way to revive it is by delete the database and do restore with recovery model. Whay is that? [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:ekLbGyX6HHA.600@TK2MSFTNGP05.phx.gbl... > Hello Roy, > > > In Log Shipping, the secondary server is supposed to be inaccessible. > There are two modes of it. One is Norecovery and the other one is Standby. > > In Norecovery mode, users can not connect to the secondary server > database. > > In Standby mode, users can connect and query the secondary database. But > this time, logs can not be merged with the secondary server database > unless all users are disconnected. > > You can not use Database Mirroring' s mirror database as a report server > because it is also going to be inaccessible. The only way you can use the > mirror server as a report server is to use a database snapshot > and update it periodically (you may use jobs for this) > > If you want to use the secondary server as a report server, then the best > is to set up a transactional replication. > > -- > Ekrem Önsoy > > > > "Roy Goldhammer" <roy@hotmail.com> wrote in message > news:ufIEUtX6HHA.5160@TK2MSFTNGP05.phx.gbl... >> Whell HIlary >> >> In my case the name of database is the same and each one of them are in >> diffrent Server >> >> So I did all the part of backup in one server, copy the data and the log >> backups to second server and run the restore part on second server >> >> After that i ran the Log shipping again. and it worked fine without no >> error. >> >> The now is that the database on secondery server is in Restoring mode and >> cannot be accessible. >> >> Whay is that? and this is the situation it should be? >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... >>> Here is an example: >>> Create database TestRoy >>> GO >>> Create database testRoyShipped >>> GO >>> alter database testroy set recovery full >>> GO >>> alter database TestRoyShipped set recovery full >>> GO >>> backup database TestRoy to disk='c:\TestRoy.bak' >>> GO >>> restore database [testroyshipped] >>> from disk = 'C:\TestRoy.bak' with >>> move 'TestRoy' to >>> 'C:\Program Files\Microsoft SQL >>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', >>> move 'TestRoy_log' to >>> 'C:\Program Files\Microsoft SQL >>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', >>> norecovery, replace >>> go >>> backup log testroy to disk='c:\testroylog.bak' >>> GO >>> restore log testroyshipped from disk='c:\testroylog.bak' with norecovery >>> GO >>> -- >>> RelevantNoise.com - dedicated to mining blogs for business intelligence. >>> >>> Looking for a SQL Server replication book? >>> http://www.nwsu.com/0974973602.html >>> >>> Looking for a FAQ on Indexing Services/SQL FTS >>> http://www.indexserverfaq.com >>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>> news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >>>> Where I do it? >>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>>> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>>>> after you restore your tlogs make sure you use the no_recovery switch >>>>> so you can restore more logs. >>>>> >>>>> -- >>>>> RelevantNoise.com - dedicated to mining blogs for business >>>>> intelligence. >>>>> >>>>> Looking for a SQL Server replication book? >>>>> http://www.nwsu.com/0974973602.html >>>>> >>>>> Looking for a FAQ on Indexing Services/SQL FTS >>>>> http://www.indexserverfaq.com >>>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>>>> Hello there >>>>>> >>>>>> I got an error when i run restore job: >>>>>> >>>>>> Database 'some database' is not in Norecovery\standby mode. >>>>>> >>>>>> what it that means? should i set it on database or in entire server? >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> >
after you restore your tlogs make sure you use the no_recovery switch so you
can restore more logs. -- RelevantNoise.com - dedicated to mining blogs for business intelligence. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Roy Goldhammer" <roy@hotmail.com> wrote in message news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... > Hello there > > I got an error when i run restore job: > > Database 'some database' is not in Norecovery\standby mode. > > what it that means? should i set it on database or in entire server? > > >
Here is an example:
Create database TestRoy GO Create database testRoyShipped GO alter database testroy set recovery full GO alter database TestRoyShipped set recovery full GO backup database TestRoy to disk='c:\TestRoy.bak' GO restore database [testroyshipped] from disk = 'C:\TestRoy.bak' with move 'TestRoy' to 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', move 'TestRoy_log' to 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', norecovery, replace go backup log testroy to disk='c:\testroylog.bak' GO restore log testroyshipped from disk='c:\testroylog.bak' with norecovery GO -- RelevantNoise.com - dedicated to mining blogs for business intelligence. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Roy Goldhammer" <roy@hotmail.com> wrote in message news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... > Where I do it? > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >> after you restore your tlogs make sure you use the no_recovery switch so >> you can restore more logs. >> >> -- >> RelevantNoise.com - dedicated to mining blogs for business intelligence. >> >> Looking for a SQL Server replication book? >> http://www.nwsu.com/0974973602.html >> >> Looking for a FAQ on Indexing Services/SQL FTS >> http://www.indexserverfaq.com >> "Roy Goldhammer" <roy@hotmail.com> wrote in message >> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>> Hello there >>> >>> I got an error when i run restore job: >>> >>> Database 'some database' is not in Norecovery\standby mode. >>> >>> what it that means? should i set it on database or in entire server? >>> >>> >>> >> >> > >
Hi Roy,
You can bring the secondary database online by restoring a tail / transaction log from the primary using "Recovery" from the Restore Options. Restoring a database using "Recovery" is the last operation to be processed in a restore operation. It finalizes the restore operation. In Log Shipping and Database Mirroring, "NoRecovery" or "Standby" options are used to keep the secondary / mirror databases up to date all the time. Log Shipping and Replication are called Warm Standby options. Warm Standby means, system can not failover automatically to the other server in case of a failure that may occur in the primary server. You have to switch / failover to the secondary server manually when you use these technologies. If you are looking for a Hot Standby system and want to use the secondary server as a report server then you can try to set up a SQL Server Active\Active two node Failover Clustering. -- Ekrem Önsoy [quoted text, click to view] "Roy Goldhammer" <roy@hotmail.com> wrote in message
news:eH%23smLY6HHA.3716@TK2MSFTNGP03.phx.gbl... > Correct: > > After running the restore section, Just the restore database the database > becomes in restoring mode and don't use. His files don't growth and even > when i reset the server it still stuck in this mode. > > The only way to revive it is by delete the database and do restore with > recovery model. > > Whay is that? > > "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message > news:ekLbGyX6HHA.600@TK2MSFTNGP05.phx.gbl... >> Hello Roy, >> >> >> In Log Shipping, the secondary server is supposed to be inaccessible. >> There are two modes of it. One is Norecovery and the other one is >> Standby. >> >> In Norecovery mode, users can not connect to the secondary server >> database. >> >> In Standby mode, users can connect and query the secondary database. But >> this time, logs can not be merged with the secondary server database >> unless all users are disconnected. >> >> You can not use Database Mirroring' s mirror database as a report server >> because it is also going to be inaccessible. The only way you can use the >> mirror server as a report server is to use a database snapshot >> and update it periodically (you may use jobs for this) >> >> If you want to use the secondary server as a report server, then the best >> is to set up a transactional replication. >> >> -- >> Ekrem Önsoy >> >> >> >> "Roy Goldhammer" <roy@hotmail.com> wrote in message >> news:ufIEUtX6HHA.5160@TK2MSFTNGP05.phx.gbl... >>> Whell HIlary >>> >>> In my case the name of database is the same and each one of them are in >>> diffrent Server >>> >>> So I did all the part of backup in one server, copy the data and the log >>> backups to second server and run the restore part on second server >>> >>> After that i ran the Log shipping again. and it worked fine without no >>> error. >>> >>> The now is that the database on secondery server is in Restoring mode >>> and cannot be accessible. >>> >>> Whay is that? and this is the situation it should be? >>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>> news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... >>>> Here is an example: >>>> Create database TestRoy >>>> GO >>>> Create database testRoyShipped >>>> GO >>>> alter database testroy set recovery full >>>> GO >>>> alter database TestRoyShipped set recovery full >>>> GO >>>> backup database TestRoy to disk='c:\TestRoy.bak' >>>> GO >>>> restore database [testroyshipped] >>>> from disk = 'C:\TestRoy.bak' with >>>> move 'TestRoy' to >>>> 'C:\Program Files\Microsoft SQL >>>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', >>>> move 'TestRoy_log' to >>>> 'C:\Program Files\Microsoft SQL >>>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', >>>> norecovery, replace >>>> go >>>> backup log testroy to disk='c:\testroylog.bak' >>>> GO >>>> restore log testroyshipped from disk='c:\testroylog.bak' with >>>> norecovery >>>> GO >>>> -- >>>> RelevantNoise.com - dedicated to mining blogs for business >>>> intelligence. >>>> >>>> Looking for a SQL Server replication book? >>>> http://www.nwsu.com/0974973602.html >>>> >>>> Looking for a FAQ on Indexing Services/SQL FTS >>>> http://www.indexserverfaq.com >>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>> news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >>>>> Where I do it? >>>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>>>> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>>>>> after you restore your tlogs make sure you use the no_recovery switch >>>>>> so you can restore more logs. >>>>>> >>>>>> -- >>>>>> RelevantNoise.com - dedicated to mining blogs for business >>>>>> intelligence. >>>>>> >>>>>> Looking for a SQL Server replication book? >>>>>> http://www.nwsu.com/0974973602.html >>>>>> >>>>>> Looking for a FAQ on Indexing Services/SQL FTS >>>>>> http://www.indexserverfaq.com >>>>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>>>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>>>>> Hello there >>>>>>> >>>>>>> I got an error when i run restore job: >>>>>>> >>>>>>> Database 'some database' is not in Norecovery\standby mode. >>>>>>> >>>>>>> what it that means? should i set it on database or in entire server? >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> > >
You can also do a restore database databasename with recovery
-- RelevantNoise.com - dedicated to mining blogs for business intelligence. Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:A0EB2ED2-3872-43D5-8CB6-F74575CEE845@microsoft.com... > Hi Roy, > > > You can bring the secondary database online by restoring a tail / > transaction log from the primary using "Recovery" from the Restore > Options. Restoring a database using "Recovery" is the last operation to be > processed in a restore operation. It finalizes the restore operation. In > Log Shipping and Database Mirroring, "NoRecovery" or "Standby" options are > used to keep the secondary / mirror databases up to date all the time. > > Log Shipping and Replication are called Warm Standby options. Warm Standby > means, system can not failover automatically to the other server in case > of a failure that may occur in the primary server. You have to switch / > failover to the secondary server manually when you use these technologies. > If you are looking for a Hot Standby system and want to use the secondary > server as a report server then you can try to set up a SQL Server > Active\Active two node Failover Clustering. > > > -- > Ekrem Önsoy > > > > "Roy Goldhammer" <roy@hotmail.com> wrote in message > news:eH%23smLY6HHA.3716@TK2MSFTNGP03.phx.gbl... >> Correct: >> >> After running the restore section, Just the restore database the database >> becomes in restoring mode and don't use. His files don't growth and even >> when i reset the server it still stuck in this mode. >> >> The only way to revive it is by delete the database and do restore with >> recovery model. >> >> Whay is that? >> >> "Ekrem Önsoy" <ekrem@btegitim.com> wrote in message >> news:ekLbGyX6HHA.600@TK2MSFTNGP05.phx.gbl... >>> Hello Roy, >>> >>> >>> In Log Shipping, the secondary server is supposed to be inaccessible. >>> There are two modes of it. One is Norecovery and the other one is >>> Standby. >>> >>> In Norecovery mode, users can not connect to the secondary server >>> database. >>> >>> In Standby mode, users can connect and query the secondary database. But >>> this time, logs can not be merged with the secondary server database >>> unless all users are disconnected. >>> >>> You can not use Database Mirroring' s mirror database as a report server >>> because it is also going to be inaccessible. The only way you can use >>> the mirror server as a report server is to use a database snapshot >>> and update it periodically (you may use jobs for this) >>> >>> If you want to use the secondary server as a report server, then the >>> best is to set up a transactional replication. >>> >>> -- >>> Ekrem Önsoy >>> >>> >>> >>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>> news:ufIEUtX6HHA.5160@TK2MSFTNGP05.phx.gbl... >>>> Whell HIlary >>>> >>>> In my case the name of database is the same and each one of them are in >>>> diffrent Server >>>> >>>> So I did all the part of backup in one server, copy the data and the >>>> log backups to second server and run the restore part on second server >>>> >>>> After that i ran the Log shipping again. and it worked fine without no >>>> error. >>>> >>>> The now is that the database on secondery server is in Restoring mode >>>> and cannot be accessible. >>>> >>>> Whay is that? and this is the situation it should be? >>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>>> news:OMAWABX6HHA.1208@TK2MSFTNGP05.phx.gbl... >>>>> Here is an example: >>>>> Create database TestRoy >>>>> GO >>>>> Create database testRoyShipped >>>>> GO >>>>> alter database testroy set recovery full >>>>> GO >>>>> alter database TestRoyShipped set recovery full >>>>> GO >>>>> backup database TestRoy to disk='c:\TestRoy.bak' >>>>> GO >>>>> restore database [testroyshipped] >>>>> from disk = 'C:\TestRoy.bak' with >>>>> move 'TestRoy' to >>>>> 'C:\Program Files\Microsoft SQL >>>>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped.mdf', >>>>> move 'TestRoy_log' to >>>>> 'C:\Program Files\Microsoft SQL >>>>> Server\MSSQL.1\MSSQL\DATA\TestRoyShipped_log.LDF', >>>>> norecovery, replace >>>>> go >>>>> backup log testroy to disk='c:\testroylog.bak' >>>>> GO >>>>> restore log testroyshipped from disk='c:\testroylog.bak' with >>>>> norecovery >>>>> GO >>>>> -- >>>>> RelevantNoise.com - dedicated to mining blogs for business >>>>> intelligence. >>>>> >>>>> Looking for a SQL Server replication book? >>>>> http://www.nwsu.com/0974973602.html >>>>> >>>>> Looking for a FAQ on Indexing Services/SQL FTS >>>>> http://www.indexserverfaq.com >>>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>>> news:eFCIx5V6HHA.3716@TK2MSFTNGP03.phx.gbl... >>>>>> Where I do it? >>>>>> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >>>>>> news:uWY9TZV6HHA.3828@TK2MSFTNGP06.phx.gbl... >>>>>>> after you restore your tlogs make sure you use the no_recovery >>>>>>> switch so you can restore more logs. >>>>>>> >>>>>>> -- >>>>>>> RelevantNoise.com - dedicated to mining blogs for business >>>>>>> intelligence. >>>>>>> >>>>>>> Looking for a SQL Server replication book? >>>>>>> http://www.nwsu.com/0974973602.html >>>>>>> >>>>>>> Looking for a FAQ on Indexing Services/SQL FTS >>>>>>> http://www.indexserverfaq.com >>>>>>> "Roy Goldhammer" <roy@hotmail.com> wrote in message >>>>>>> news:%231lEnKV6HHA.5844@TK2MSFTNGP02.phx.gbl... >>>>>>>> Hello there >>>>>>>> >>>>>>>> I got an error when i run restore job: >>>>>>>> >>>>>>>> Database 'some database' is not in Norecovery\standby mode. >>>>>>>> >>>>>>>> what it that means? should i set it on database or in entire >>>>>>>> server? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >> >> >
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |