Log shipping alerts: configured

Showing posts with label configured. Show all posts

Wednesday, March 28, 2012

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard again
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?
Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY =
{standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?
|||My goal was to have a readable database on the destination side that could be
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (I
never used log shipping in 2000 since we only have standard edition). I will
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY =
> {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
>
>

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into
a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard agai
n
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY =
{standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?|||My goal was to have a readable database on the destination side that could b
e
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (
I
never used log shipping in 2000 since we only have standard edition). I wil
l
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY =
> {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
>
>

log shipping sql 2005 database remains in (restoring...) mode

I've been playing with the SQL 2005 log shipping and have been running into a
few problems.
My system is configured on a virtual server with two instances of SQL 2005.
The OS is Windows 2003. I'm shipping logs from the default instance to the
named instance with the default having the primary database and the named,
the secondary.
When I use the log shipping wizard, and have it do the initial restore to
the secondary, all appears to work well but the database remains in
"(Restoring ...) in the Management Studio (MS) GUI. So after starting over
and manually restoring the database to the secondary, I used the wizard again
to set this up and now the Agent jobs indicate success in applying the logs
but again, the database continues to show as (Restoring ...) in the MS GUI.
It is indeed unavailable as you can't query it in a Query window. I tried
this with upgraded SQL 2000 databases and newly created SQL 2005 databases,
both with the same result.
Has anyone run into this and can you tell me what might be happening?Hi
By default, you can not access the destination DB in a log shipping
partnership. It was the same in SQL Server 2000.
If you want to have read only access, subject to having your connections
dropped when the next log restore occurs,
you need to execute a restore with the additional parameter of "STANDBY ={standby_file_name}".
This can not be done in the GUI.
What are you trying to achieve?
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> I've been playing with the SQL 2005 log shipping and have been running
> into a
> few problems.
> My system is configured on a virtual server with two instances of SQL
> 2005.
> The OS is Windows 2003. I'm shipping logs from the default instance to the
> named instance with the default having the primary database and the named,
> the secondary.
> When I use the log shipping wizard, and have it do the initial restore to
> the secondary, all appears to work well but the database remains in
> "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> and manually restoring the database to the secondary, I used the wizard
> again
> to set this up and now the Agent jobs indicate success in applying the
> logs
> but again, the database continues to show as (Restoring ...) in the MS
> GUI.
> It is indeed unavailable as you can't query it in a Query window. I tried
> this with upgraded SQL 2000 databases and newly created SQL 2005
> databases,
> both with the same result.
> Has anyone run into this and can you tell me what might be happening?|||My goal was to have a readable database on the destination side that could be
accessible in case of failure of the primary database. I guess I'm ignorant
of a basic tenent of log shipping and for that I apologize. Apparently, the
process is working as it should be and I thank you for pointing that out. (I
never used log shipping in 2000 since we only have standard edition). I will
"read up" on the subject a bit more. Thanks much!
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> By default, you can not access the destination DB in a log shipping
> partnership. It was the same in SQL Server 2000.
> If you want to have read only access, subject to having your connections
> dropped when the next log restore occurs,
> you need to execute a restore with the additional parameter of "STANDBY => {standby_file_name}".
> This can not be done in the GUI.
> What are you trying to achieve?
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Dlorbecki" <Dlorbecki@.discussions.microsoft.com> wrote in message
> news:4262DE8E-343E-4C2C-B2D6-43A5D6A425A3@.microsoft.com...
> > I've been playing with the SQL 2005 log shipping and have been running
> > into a
> > few problems.
> >
> > My system is configured on a virtual server with two instances of SQL
> > 2005.
> > The OS is Windows 2003. I'm shipping logs from the default instance to the
> > named instance with the default having the primary database and the named,
> > the secondary.
> >
> > When I use the log shipping wizard, and have it do the initial restore to
> > the secondary, all appears to work well but the database remains in
> > "(Restoring ...) in the Management Studio (MS) GUI. So after starting over
> > and manually restoring the database to the secondary, I used the wizard
> > again
> > to set this up and now the Agent jobs indicate success in applying the
> > logs
> > but again, the database continues to show as (Restoring ...) in the MS
> > GUI.
> > It is indeed unavailable as you can't query it in a Query window. I tried
> > this with upgraded SQL 2000 databases and newly created SQL 2005
> > databases,
> > both with the same result.
> >
> > Has anyone run into this and can you tell me what might be happening?
>
>

Log Shipping Role Reversal

I have log shipping configured on a pair of test SQL 2000 servers, both are
at SP3. The log shipping is working fine, but the problem occurs when I try
to reverse roles. I run this SQL statement on the primary server:
USE master
GO
EXEC msdb.dbo.sp_change_primary_role
@.db_name = 'ModelCopy',
@.backup_log = 1,
@.terminate = 1,
@.final_state = 3,
@.access_level = 1
This places the primary database into read-only mode. I then run this SQL
statement on the secondary server.
USE master
GO
EXEC msdb.dbo.sp_change_secondary_role
@.db_name = 'ModelCopy',
@.do_load = 1,
@.force_load = 1,
@.final_state = 1,
@.access_level = 1,
@.terminate = 1,
@.keep_replication = 0,
@.stopat = null
At which time I get this error:
Server: Msg 927, Level 14, State 2, Line 1
Database 'ModelCopy' cannot be opened. It is in the middle of a restore.
Server: Msg 5069, Level 16, State 1, Line 1
ALTER DATABASE statement failed.
Server: Msg 14440, Level 16, State 1, Procedure sp_change_secondary_role,
Line 49
Could not set single user mode.
In each case, I am runnig the statements in Query Analyzer with the
Enterprise Manager window closed. I understand that these statements cause
the primary to make a final copy and the secondary to do a final restore, but
the database I'm using is very small (a copy of the Model databae) and
shouldn't take but a few seconds, which is all the time it took to create and
initialize the database on the secondary to begin with. Is this process hung,
or am I just being impatient? It's been over 20 minutes.
TIA,
Ken
Ken,
See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
3101 if There Are Outstanding Transaction Log Backups
http://support.microsoft.com/default...&Product=sql2k
This is similar, though not identical, to the error you are getting. The
upshot is that you need to make sure that all the transaction logs have been
restored if you set the @.terminate parameter to 1.
Hope this helps,
Ron
Ron Talmage
SQL Server MVP
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> I have log shipping configured on a pair of test SQL 2000 servers, both
are
> at SP3. The log shipping is working fine, but the problem occurs when I
try
> to reverse roles. I run this SQL statement on the primary server:
> USE master
> GO
> EXEC msdb.dbo.sp_change_primary_role
> @.db_name = 'ModelCopy',
> @.backup_log = 1,
> @.terminate = 1,
> @.final_state = 3,
> @.access_level = 1
> This places the primary database into read-only mode. I then run this SQL
> statement on the secondary server.
> USE master
> GO
> EXEC msdb.dbo.sp_change_secondary_role
> @.db_name = 'ModelCopy',
> @.do_load = 1,
> @.force_load = 1,
> @.final_state = 1,
> @.access_level = 1,
> @.terminate = 1,
> @.keep_replication = 0,
> @.stopat = null
> At which time I get this error:
> Server: Msg 927, Level 14, State 2, Line 1
> Database 'ModelCopy' cannot be opened. It is in the middle of a restore.
> Server: Msg 5069, Level 16, State 1, Line 1
> ALTER DATABASE statement failed.
> Server: Msg 14440, Level 16, State 1, Procedure sp_change_secondary_role,
> Line 49
> Could not set single user mode.
> In each case, I am runnig the statements in Query Analyzer with the
> Enterprise Manager window closed. I understand that these statements cause
> the primary to make a final copy and the secondary to do a final restore,
but
> the database I'm using is very small (a copy of the Model databae) and
> shouldn't take but a few seconds, which is all the time it took to create
and
> initialize the database on the secondary to begin with. Is this process
hung,
> or am I just being impatient? It's been over 20 minutes.
> TIA,
> Ken
|||Thanks for the info Ron. It pointed me in the right direction. I still needed
to to a detach/attach sequesnce on the database before running the secondary
stored procedure, but at least it is working in a predictable manner now.
"Ron Talmage" wrote:

> Ken,
> See the KB article 294397 BUG: sp_change_secondary_role Fails with Error
> 3101 if There Are Outstanding Transaction Log Backups
> http://support.microsoft.com/default...&Product=sql2k
> This is similar, though not identical, to the error you are getting. The
> upshot is that you need to make sure that all the transaction logs have been
> restored if you set the @.terminate parameter to 1.
> Hope this helps,
> Ron
> --
> Ron Talmage
> SQL Server MVP
> "kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
> news:733456B1-BC99-43B2-B6BD-4030A08DB6EC@.microsoft.com...
> are
> try
> but
> and
> hung,
>
>
|||OK, I spoke too soon. Occasionally, the sp_change_secondary_role procedure
will end with a "sqlmaint.exe failed. [SQLSTATE 42000][Error 22029]. The step
failed." message. I haven't been able to find any helpful information on this
message yet. Can you shed some more light on what is happening during this
procedure? Same scripts as posted previously in this thread, and include the
manual running of the restore job and a database detach/attach sequence in
Enterprise Manager immediately prior to running the secondary role change
stpred procedure.
Thanks Again,
Ken
"kmkrause2" wrote:
[vbcol=seagreen]
> Thanks for the info Ron. It pointed me in the right direction. I still needed
> to to a detach/attach sequesnce on the database before running the secondary
> stored procedure, but at least it is working in a predictable manner now.
> "Ron Talmage" wrote:

Friday, March 23, 2012

log shipping problem

I have 2 server 1 primary 2nd secondary
I have configured log shipping on them'
Now everything works fine, no errors any where bt file is not copied in the
secondary server folder.
any if I run the copy job on secondary server it gives following output
output
----
----
----
--
NULL
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
NULL
Logged on to SQL Server 'DB_OLD'
as 'DB_OLD\sqlservice' (trusted)
NULL
NULL
Starting copy for plan 10.11.11.11.CCM_logshipping
NULL
Source database - CCM
Copied 0 files
NULL
Finished copy for plan 10.11.11.11.CCM_logshipping
I have configure a/c on both server, a/c are local account under which sql
agent and server runs
Please let me know what can be the problem.Hi,
I think this is mainly access permisssion issue.
May user of primary server don't have access to write in secondary
server.
Regards,
Sajid C.
VSS wrote:
> I have 2 server 1 primary 2nd secondary
> I have configured log shipping on them'
> Now everything works fine, no errors any where bt file is not copied in th
e
> secondary server folder.
> any if I run the copy job on secondary server it gives following output
> output
> ----
--
> ----
--
> ----
--
> --
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> Logged on to SQL Server 'DB_OLD'
> as 'DB_OLD\sqlservice' (trusted)
> NULL
> NULL
> Starting copy for plan 10.11.11.11.CCM_logshipping
> NULL
> Source database - CCM
> Copied 0 files
> NULL
> Finished copy for plan 10.11.11.11.CCM_logshipping
> I have configure a/c on both server, a/c are local account under which sql
> agent and server runs
> Please let me know what can be the problem.

log shipping problem

I have 2 server 1 primary 2nd secondary
I have configured log shipping on them'
Now everything works fine, no errors any where bt file is not copied in the
secondary server folder.
any if I run the copy job on secondary server it gives following output
output
----
----
----
--
NULL
Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
Copyright (C) Microsoft Corporation, 1995 - 1998
NULL
Logged on to SQL Server 'DB_OLD'
as 'DB_OLD\sqlservice' (trusted)
NULL
NULL
Starting copy for plan 10.11.11.11.CCM_logshipping
NULL
Source database - CCM
Copied 0 files
NULL
Finished copy for plan 10.11.11.11.CCM_logshipping
I have configure a/c on both server, a/c are local account under which sql
agent and server runs
Please let me know what can be the problem.Hi,
I think this is mainly access permisssion issue.
May user of primary server don't have access to write in secondary
server.
Regards,
Sajid C.
VSS wrote:
> I have 2 server 1 primary 2nd secondary
> I have configured log shipping on them'
> Now everything works fine, no errors any where bt file is not copied in the
> secondary server folder.
> any if I run the copy job on secondary server it gives following output
> output
> ----
> ----
> ----
> --
> NULL
> Microsoft (R) SQLMaint Utility (Unicode), Version 8.00.760
> Copyright (C) Microsoft Corporation, 1995 - 1998
> NULL
> Logged on to SQL Server 'DB_OLD'
> as 'DB_OLD\sqlservice' (trusted)
> NULL
> NULL
> Starting copy for plan 10.11.11.11.CCM_logshipping
> NULL
> Source database - CCM
> Copied 0 files
> NULL
> Finished copy for plan 10.11.11.11.CCM_logshipping
> I have configure a/c on both server, a/c are local account under which sql
> agent and server runs
> Please let me know what can be the problem.

Monday, March 19, 2012

Log Shipping Monitor

Hello,
I have configured a SQL Server for Log Shipping using the Database Maintenan
ce Planner Wizard. Now a Log Shipping Monitor object appears below the Manag
ement folder. How do I reverse this process, and make the Log Shipping Monit
or disappear? In other word
s I want to revert back to the state SQL Server was in before I ran the Data
base Maintenance Planner.
Thanks,
Jerome SmithHello all,
I'll answer my own question for everybody's benefit. Eliminating the Log Shi
pping Monitor is equivalent to eliminating all Log Shipping pairs from the L
og Shipping system database. This is done with the stored procedure:
sp_delete_log_shipping_primary
located in the msdb system database.
Following is the help article.
Cheers,
Jerome
sp_delete_log_shipping_primary
Deletes the primary server from the log_shipping_primaries table.
Syntax
sp_delete_log_shipping_primary
[ @.primary_server_name = ] 'primary_server_name' ,
[ @.primary_database_name = ] 'primary_database_name' ,
{ [ @.delete_secondaries = ] delete_secondaries }
Arguments
[@.primary_server_name =] 'primary_server_name'
Is the name of the primary server. primary_server_name is sysname.
[@.primary_database_name =] 'primary_database_name'
Is the name of the secondary server. primary_database_name is sysname.
[@.delete_secondaries =] delete_secondaries
Specifies that the delete action is also applied to log_shipping_secondaries
table. delete_secondaries is bit, with a default of zero (0).
Return Code Values
0 (success) or 1 (failure)
Remarks
This stored procedure only removes the primary and secondary server from the
monitor. Log shipping still has to be removed from the primary and secondar
y servers.
sp_delete_log_shipping_primary deletes a log shipping primary table. If ther
e are corresponding rows in the log_shipping_databases table, delete_seconda
ries must be set to one (1) or the stored procedure will fail.
Permissions
Only members of the sysadmin fixed server role can execute sp_delete_log_shi
pping_primaries.
Examples
This example deletes the source database "pubs" from the server "source". Th
ere are no corresponding rows in log_shipping_secondaries table.
EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source', @.pri
mary_database_name = N'pubs'
?1988-2000 Microsoft Corporation. All Rights Reserved.|||Actually, when nothing has gone wrong, the easiest way is in Enterprise
Manager:
Management->Database Maintenance Plans->Right-Click->Properties->Log
Shipping->Remove Log Shipping.
Then delete Plan.
Jerome
"Jerome Smith" <jerosmith@.hotmail.com> escribi en el mensaje
news:3B6447C3-7819-4F31-983B-7BDD84D2311F@.microsoft.com...
> Hello all,
> I'll answer my own question for everybody's benefit. Eliminating the Log
Shipping Monitor is equivalent to eliminating all Log Shipping pairs from
the Log Shipping system database. This is done with the stored procedure:
> sp_delete_log_shipping_primary
> located in the msdb system database.
> Following is the help article.
> Cheers,
> Jerome
> sp_delete_log_shipping_primary
> Deletes the primary server from the log_shipping_primaries table.
> Syntax
> sp_delete_log_shipping_primary
> [ @.primary_server_name = ] 'primary_server_name' ,
> [ @.primary_database_name = ] 'primary_database_name' ,
> { [ @.delete_secondaries = ] delete_secondaries }
> Arguments
> [@.primary_server_name =] 'primary_server_name'
> Is the name of the primary server. primary_server_name is sysname.
> [@.primary_database_name =] 'primary_database_name'
> Is the name of the secondary server. primary_database_name is sysname.
> [@.delete_secondaries =] delete_secondaries
> Specifies that the delete action is also applied to
log_shipping_secondaries table. delete_secondaries is bit, with a default of
zero (0).
> Return Code Values
> 0 (success) or 1 (failure)
> Remarks
> This stored procedure only removes the primary and secondary server from
the monitor. Log shipping still has to be removed from the primary and
secondary servers.
> sp_delete_log_shipping_primary deletes a log shipping primary table. If
there are corresponding rows in the log_shipping_databases table,
delete_secondaries must be set to one (1) or the stored procedure will fail.
> Permissions
> Only members of the sysadmin fixed server role can execute
sp_delete_log_shipping_primaries.
> Examples
> This example deletes the source database "pubs" from the server "source".
There are no corresponding rows in log_shipping_secondaries table.
> EXEC sp_delete_log_shipping_primary @.primary_server_name = N'source',
@.primary_database_name = N'pubs'
> 1988-2000 Microsoft Corporation. All Rights Reserved.
>
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.629 / Virus Database: 403 - Release Date: 17-03-2004

Monday, March 12, 2012

Log Shipping from 2000 to 2005

Can log shipping be configured from a SQL Server 2000 database to a SQL
Server 2005 database? I have read some posts on the Microsoft forums that
indicate that it may be possible if a backup of the SQL Server 2000 database
is restored to SQL Server 2005 with NoRecovery. I have tried to set this up
with Enterprise Manager but have not had any luck.
I have searched the Microsoft documentation but have not found anything
definitive.
Please help.
Thanks!
ChrisI'd very much doubt that you can use the built-in support for log shipping. But you can roll your
own. Google and you will even find script written for you.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:%23j0xkdmkHHA.4848@.TK2MSFTNGP05.phx.gbl...
> Can log shipping be configured from a SQL Server 2000 database to a SQL Server 2005 database? I
> have read some posts on the Microsoft forums that indicate that it may be possible if a backup of
> the SQL Server 2000 database is restored to SQL Server 2005 with NoRecovery. I have tried to set
> this up with Enterprise Manager but have not had any luck.
> I have searched the Microsoft documentation but have not found anything definitive.
> Please help.
> Thanks!
> Chris
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:ehcjHunkHHA.4676@.TK2MSFTNGP02.phx.gbl...
> I'd very much doubt that you can use the built-in support for log
> shipping. But you can roll your own. Google and you will even find script
> written for you.
>
Tibor, I haven't tried, but I don't think you can do log-shipping here, even
rolling your own since as soon as you do the restore to 2005, it wants to
"update" the database.
Cgal, MIGHT work if you specify a standby file. let us know.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
> news:%23j0xkdmkHHA.4848@.TK2MSFTNGP05.phx.gbl...
>> Can log shipping be configured from a SQL Server 2000 database to a SQL
>> Server 2005 database? I have read some posts on the Microsoft forums
>> that indicate that it may be possible if a backup of the SQL Server 2000
>> database is restored to SQL Server 2005 with NoRecovery. I have tried to
>> set this up with Enterprise Manager but have not had any luck.
>> I have searched the Microsoft documentation but have not found anything
>> definitive.
>> Please help.
>> Thanks!
>> Chris
>
--
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hello Chris,
Consider the following scenario:
a) SQL Server 2000 as the source server and SQL 2005 as the standby
destination
server for LogShipping.
b) SQL Server 20005 as the source server and SQL 2000 as the standby
destination
server for Log Shipping
Both these scenarios are NOT possible. This is by design.
In SQL 2000, if you try to use the Database Maintenance Plan Wizard, you
will
realize that the wizard pre-fills the list of SQL 2000 destination servers.
You
cannot specify a SQL 2005 server as the destination server.
Similarly, if you register a SQL 2000 server in Management Studio, and
right click
to see the properties of the database, you wont see the Transaction Log
Shipping
option there for a SQL 2000 database. However, this option is present for
SQL 2005
databases only.
Sincerely,
Wei Lu
Microsoft Online Community 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.|||> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
> since as soon as you do the restore to 2005, it wants to "update" the database.
I've tried it ;-). You can restore the log as long as you specify NORECOVERY.
> Cgal, MIGHT work if you specify a standby file. let us know.
This is where it doesn't work. Specifying STANDBY means SQL Server need to upgrade the database, and
then downgrading it when applying your next log backup, which isn't possible. So you get an error if
you specify STANDBY when restoring 2000 backup onto 2005.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:eCgyKiskHHA.4624@.TK2MSFTNGP04.phx.gbl...
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:ehcjHunkHHA.4676@.TK2MSFTNGP02.phx.gbl...
>> I'd very much doubt that you can use the built-in support for log shipping. But you can roll your
>> own. Google and you will even find script written for you.
> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
> since as soon as you do the restore to 2005, it wants to "update" the database.
> Cgal, MIGHT work if you specify a standby file. let us know.
>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
>> news:%23j0xkdmkHHA.4848@.TK2MSFTNGP05.phx.gbl...
>> Can log shipping be configured from a SQL Server 2000 database to a SQL Server 2005 database? I
>> have read some posts on the Microsoft forums that indicate that it may be possible if a backup
>> of the SQL Server 2000 database is restored to SQL Server 2005 with NoRecovery. I have tried to
>> set this up with Enterprise Manager but have not had any luck.
>> I have searched the Microsoft documentation but have not found anything definitive.
>> Please help.
>> Thanks!
>> Chris
>>
> --
> Greg Moore
> SQL Server DBA Consulting Remote and Onsite available!
> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>|||Everyone,
Thanks for the reponses.
The conclusion I draw from all your comments is that log shipping is
possible from 2000 to 2005 if the 2000 log shipping destination database is
restored in NORECOVERY on the 2005 server. The log shipping in this
scenario must be done with a custom solution and is not supported with
either SSMS or Enterprise Manager.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uiMAg3skHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Tibor, I haven't tried, but I don't think you can do log-shipping here,
>> even rolling your own since as soon as you do the restore to 2005, it
>> wants to "update" the database.
> I've tried it ;-). You can restore the log as long as you specify
> NORECOVERY.
>
>> Cgal, MIGHT work if you specify a standby file. let us know.
> This is where it doesn't work. Specifying STANDBY means SQL Server need to
> upgrade the database, and then downgrading it when applying your next log
> backup, which isn't possible. So you get an error if you specify STANDBY
> when restoring 2000 backup onto 2005.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
> message news:eCgyKiskHHA.4624@.TK2MSFTNGP04.phx.gbl...
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
>> in message news:ehcjHunkHHA.4676@.TK2MSFTNGP02.phx.gbl...
>> I'd very much doubt that you can use the built-in support for log
>> shipping. But you can roll your own. Google and you will even find
>> script written for you.
>>
>> Tibor, I haven't tried, but I don't think you can do log-shipping here,
>> even rolling your own since as soon as you do the restore to 2005, it
>> wants to "update" the database.
>> Cgal, MIGHT work if you specify a standby file. let us know.
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
>> news:%23j0xkdmkHHA.4848@.TK2MSFTNGP05.phx.gbl...
>> Can log shipping be configured from a SQL Server 2000 database to a SQL
>> Server 2005 database? I have read some posts on the Microsoft forums
>> that indicate that it may be possible if a backup of the SQL Server
>> 2000 database is restored to SQL Server 2005 with NoRecovery. I have
>> tried to set this up with Enterprise Manager but have not had any luck.
>> I have searched the Microsoft documentation but have not found anything
>> definitive.
>> Please help.
>> Thanks!
>> Chris
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com
>> http://www.greenms.com/sqlserver.html
>>
>|||> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.
Yes, it should be possible. I should add that what I've tested is to restore a few 2000 log backups
to 2005 using norecovery. This was all OK. I then did RESTORE DATABASE x WITH RECOVERY to verify
that this was possible. Also OK. You should run a test where you actually log ship (a series of
restore) so nothing strange happens over time (not that I can see what that would be).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message news:ujFHgNvkHHA.3472@.TK2MSFTNGP04.phx.gbl...
> Everyone,
> Thanks for the reponses.
> The conclusion I draw from all your comments is that log shipping is possible from 2000 to 2005 if
> the 2000 log shipping destination database is restored in NORECOVERY on the 2005 server. The log
> shipping in this scenario must be done with a custom solution and is not supported with either
> SSMS or Enterprise Manager.
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:uiMAg3skHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>> since as soon as you do the restore to 2005, it wants to "update" the database.
>> I've tried it ;-). You can restore the log as long as you specify NORECOVERY.
>>
>> Cgal, MIGHT work if you specify a standby file. let us know.
>> This is where it doesn't work. Specifying STANDBY means SQL Server need to upgrade the database,
>> and then downgrading it when applying your next log backup, which isn't possible. So you get an
>> error if you specify STANDBY when restoring 2000 backup onto 2005.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
>> news:eCgyKiskHHA.4624@.TK2MSFTNGP04.phx.gbl...
>>
>> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
>> news:ehcjHunkHHA.4676@.TK2MSFTNGP02.phx.gbl...
>> I'd very much doubt that you can use the built-in support for log shipping. But you can roll
>> your own. Google and you will even find script written for you.
>>
>> Tibor, I haven't tried, but I don't think you can do log-shipping here, even rolling your own
>> since as soon as you do the restore to 2005, it wants to "update" the database.
>> Cgal, MIGHT work if you specify a standby file. let us know.
>>
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Cgal" <cgallelli@.newsgroups.nospam> wrote in message
>> news:%23j0xkdmkHHA.4848@.TK2MSFTNGP05.phx.gbl...
>> Can log shipping be configured from a SQL Server 2000 database to a SQL Server 2005 database?
>> I have read some posts on the Microsoft forums that indicate that it may be possible if a
>> backup of the SQL Server 2000 database is restored to SQL Server 2005 with NoRecovery. I have
>> tried to set this up with Enterprise Manager but have not had any luck.
>> I have searched the Microsoft documentation but have not found anything definitive.
>> Please help.
>> Thanks!
>> Chris
>>
>> --
>> Greg Moore
>> SQL Server DBA Consulting Remote and Onsite available!
>> Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
>>
>>
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uiMAg3skHHA.2552@.TK2MSFTNGP06.phx.gbl...
>> Tibor, I haven't tried, but I don't think you can do log-shipping here,
>> even rolling your own since as soon as you do the restore to 2005, it
>> wants to "update" the database.
> I've tried it ;-). You can restore the log as long as you specify
> NORECOVERY.
Nothing like reality to confirm something.
(Just went through an interview where they claimed I was wrong about how BCP
and BULK COPY recovery mode worked. Annoyed me so much I had to go home to
confirm I was right. I was...they were wrong. But they still think they're
right. Oh well.)
>
>> Cgal, MIGHT work if you specify a standby file. let us know.
> This is where it doesn't work. Specifying STANDBY means SQL Server need to
> upgrade the database, and then downgrading it when applying your next log
> backup, which isn't possible. So you get an error if you specify STANDBY
> when restoring 2000 backup onto 2005.
Ah ok, so the exact opposite of what I was thinking. But I can see taht.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
Does this mean you're working over at SQL now or simply hawking a great
site?
(Great group of people there, I've met a few. When I'm 1/2 as good as any
of them I'll consider myself "pretty good". ;-)

Log Shipping from 2000 to 2005

Log Shipping for multiple databases

Hello

we have SQL instance which contains databases (A, B, C...). When ever i configured LS with Standby option, and i want complete restore of database A (Primary) to stand by A (Secondary), then logs will always going to restore...

but SQL server is taking a copy of the Backup like "GJ_Temp_data, GJ_Temp_log" as the default file names, for restore the DB Backups.

if i want to set up for the database B, it is taking "GJ_Temp_data, GJ_Temp_log" again for the database B, and giving error as "the files are already in use".

If i script the Log shipping setup while enabling for Database A, and make sure that i will enabling it for remaining databases B, C, D..

Please advice, and give us best experienceS for enabling LS FOR Multiple databases on the single SQL Instance.

Thanks in advance.

Pls perform the below steps I assume there are 2 sql servers namely Sql1 and Sql2

1. Take full backup in Sql1 of database A and copy it to shared folder in Sql2 and restore with standby option

2. Take full backup in Sql1 of database B and copy it to shared folder in Sql2 and restore with standby option

3. Start the log backups,copy and restore jobs in principal and secondary servers for both the databases

Performing log shipping in a single sql instance will not server the purpose of log shipping as LS is a high availability solution and in your case if the single instance which holds both the primary and secondary db is down you cannot have a DR solution as a backup to your production db !

Thanxx

Deepak

Friday, March 9, 2012

log shipping error

I have successfully configured log shipping, and verified that the standby
server is being updated correctly.
There is one job named "Log Shipping Alert Job - Backup" which fails every
minute.
In the job history, it says:
'The job shipping source SERVERNAME.DATABASE has not backed up for 190
minutes. [SQLSTATE 42000] [Error 14420] The step failed.'
I guess that this can be disregarded, but supervisors get nervous about
errors, and suspect that the log shipping is not reliable.
How can I make this job succeed?
Thanks
Bill
It looks like the 'last_updated' field in 'log_shipping_primaries' in MSDB
isn't getting updated.
Whey would that be the case?
Thanks
Bill
"bill" <belgie@.datamti.com> wrote in message
news:e$lobJOeFHA.2128@.TK2MSFTNGP14.phx.gbl...
> I have successfully configured log shipping, and verified that the standby
> server is being updated correctly.
> There is one job named "Log Shipping Alert Job - Backup" which fails every
> minute.
> In the job history, it says:
> 'The job shipping source SERVERNAME.DATABASE has not backed up for 190
> minutes. [SQLSTATE 42000] [Error 14420] The step failed.'
> I guess that this can be disregarded, but supervisors get nervous about
> errors, and suspect that the log shipping is not reliable.
> How can I make this job succeed?
> Thanks
> Bill
>
>
|||Microsoft say:
"Thresholds
The DBA maintaining the SQL Server environment needs to know if log shipping becomes too far out of sync and/or may be failing. The two parameters to configure are: backup alert threshold and out of sync alert threshold. The alerts are triggered by error messages 14420 and 14421, respectively, and can be changed. After log shipping is installed, access the parameters by selecting the properties of the log shipping pair listed under the Log Shipping Monitor. "
Regards,
Milovan

Wednesday, March 7, 2012

Log Shipping and SQL Server Licence Requirement

Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
as[vbcol=seagreen]
SQL[vbcol=seagreen]
kept[vbcol=seagreen]
can[vbcol=seagreen]
any[vbcol=seagreen]
wrote[vbcol=seagreen]
what[vbcol=seagreen]
server?[vbcol=seagreen]
>
>

Log Shipping and SQL Server Licence Requirement

Given that the secondary server can be configured in standby mode, what is
the minimum SQL Server licensing requirement for the secondary server?
thanks in advance
James
The "secondary server" is not in standby mode, only the database(s) you log ship is. So you need a
license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James
|||The EULA states that the passive node in a cluster configuration as well as
the SQL Server hosting only standby databases in a log-shipping
configuration may be hosted for disaster recovery purposes as long as SQL
Server is licensed for the host with the most CPUs if one were licensed
under the per-processor mode.
For CAL based installations, it is the number of CALs that need to be kept
up to date, but the SQL Server host that is acting in a passive capacity can
be installed under the active's license as long as only one is active at any
given moment.
Sincerely,
Anthony Thomas

"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
The "secondary server" is not in standby mode, only the database(s) you
log ship is. So you need a
license for that server as well. See
http://www.microsoft.com/sql/howtobuy/faq.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> Given that the secondary server can be configured in standby mode, what
is
> the minimum SQL Server licensing requirement for the secondary server?
> thanks in advance
> James
|||That doesn't goes with the FAQ page I referred to:
Q. If I am doing log shipping in an active/passive failover configuration, how should I
license the backup server?
A. In this scenario, the active and passive servers must be licensed identically, so that the
passive server can process the same workload as the active server in the event of a failover.
Makes one wonder whether to go by the EULA or the FAQ page. I guess that the EULA is more legally
binding, so I would carefully read the text...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> The EULA states that the passive node in a cluster configuration as well as
> the SQL Server hosting only standby databases in a log-shipping
> configuration may be hosted for disaster recovery purposes as long as SQL
> Server is licensed for the host with the most CPUs if one were licensed
> under the per-processor mode.
> For CAL based installations, it is the number of CALs that need to be kept
> up to date, but the SQL Server host that is acting in a passive capacity can
> be installed under the active's license as long as only one is active at any
> given moment.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The "secondary server" is not in standby mode, only the database(s) you
> log ship is. So you need a
> license for that server as well. See
> http://www.microsoft.com/sql/howtobuy/faq.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> is
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end
|||I believe MS wants you license the warm standby as a production server.
Hence, it needs to have money spent on it..

Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally[vbcol=seagreen]
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
as[vbcol=seagreen]
SQL[vbcol=seagreen]
kept[vbcol=seagreen]
can[vbcol=seagreen]
any[vbcol=seagreen]
wrote[vbcol=seagreen]
what[vbcol=seagreen]
server?
>
>

Log Shipping and SQL Server Licence Requirement

The EULA states that the passive node =in a cluster configuration as well as the SQL Server hosting only standby =databases in a log-shipping configuration may be hosted for disaster recovery =purposes as long as SQL Server is licensed for the host with the most CPUs if one =were licensed under the per-processor mode.
For CAL based installations, it is =the number of CALs that need to be kept up to date, but the SQL Server host that is =acting in a passive capacity can be installed under the active's license as long =as only one is active at any given moment.
Sincerely,
Anthony Thomas
--
"Tibor Karaszi" wrote in message news:%23ASMAQj8EHA.=3236@.TK2MSFTNGP15.phx.gbl...The "secondary server" is not in standby mode, only the database(s) you =log ship is. So you need a license for that server as well. See http://www.microsoft.com/sql/howtobuy/faq.asp">http://www.microso=ft.com/sql/howtobuy/faq.asp-- Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asp">http://www.karaszi.=com/sqlserver/default.asphttp://www.solidqualitylearning.com/">http://www.solidqualitylear=ning.com/http://www.sqlug.se/">http://www.sqlug.se/"James-=Aus" wrote in message news:7A4=6C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...> Given that the secondary server can be configured in standby mode, =what is> the minimum SQL Server licensing requirement for the =secondary server?>> thanks in advance> James

--=_NextPart_000_07A3_01C4F23E.E02BFD90--|||That doesn't goes with the FAQ page I referred to:
Q. If I am doing log shipping in an active/passive failover configuration, how should I
license the backup server?
A. In this scenario, the active and passive servers must be licensed identically, so that the
passive server can process the same workload as the active server in the event of a failover.
Makes one wonder whether to go by the EULA or the FAQ page. I guess that the EULA is more legally
binding, so I would carefully read the text...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> The EULA states that the passive node in a cluster configuration as well as
> the SQL Server hosting only standby databases in a log-shipping
> configuration may be hosted for disaster recovery purposes as long as SQL
> Server is licensed for the host with the most CPUs if one were licensed
> under the per-processor mode.
> For CAL based installations, it is the number of CALs that need to be kept
> up to date, but the SQL Server host that is acting in a passive capacity can
> be installed under the active's license as long as only one is active at any
> given moment.
> Sincerely,
>
> Anthony Thomas
>
> --
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> The "secondary server" is not in standby mode, only the database(s) you
> log ship is. So you need a
> license for that server as well. See
> http://www.microsoft.com/sql/howtobuy/faq.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> > Given that the secondary server can be configured in standby mode, what
> is
> > the minimum SQL Server licensing requirement for the secondary server?
> >
> > thanks in advance
> > James
>
begin 666 ts.gif
J1TE&.#EA`0`!`( ``````/___R'Y! $`````+ `````!``$```(!1 `[
`
end|||I believe MS wants you license the warm standby as a production server.
Hence, it needs to have money spent on it.. :(
Eric D. Smith
St. Louis, MO
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:uHl12Jn8EHA.3416@.TK2MSFTNGP09.phx.gbl...
> That doesn't goes with the FAQ page I referred to:
> Q. If I am doing log shipping in an active/passive failover
configuration, how should I
> license the backup server?
>
> A. In this scenario, the active and passive servers must be
licensed identically, so that the
> passive server can process the same workload as the active server in the
event of a failover.
>
> Makes one wonder whether to go by the EULA or the FAQ page. I guess that
the EULA is more legally
> binding, so I would carefully read the text...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> http://www.sqlug.se/
>
> "AnthonyThomas" <Anthony.Thomas@.CommerceBank.com> wrote in message
> news:%23udXVFn8EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > The EULA states that the passive node in a cluster configuration as well
as
> > the SQL Server hosting only standby databases in a log-shipping
> > configuration may be hosted for disaster recovery purposes as long as
SQL
> > Server is licensed for the host with the most CPUs if one were licensed
> > under the per-processor mode.
> >
> > For CAL based installations, it is the number of CALs that need to be
kept
> > up to date, but the SQL Server host that is acting in a passive capacity
can
> > be installed under the active's license as long as only one is active at
any
> > given moment.
> >
> > Sincerely,
> >
> >
> > Anthony Thomas
> >
> >
> > --
> >
> > "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com>
wrote
> > in message news:%23ASMAQj8EHA.3236@.TK2MSFTNGP15.phx.gbl...
> > The "secondary server" is not in standby mode, only the database(s) you
> > log ship is. So you need a
> > license for that server as well. See
> > http://www.microsoft.com/sql/howtobuy/faq.asp
> >
> > --
> > Tibor Karaszi, SQL Server MVP
> > http://www.karaszi.com/sqlserver/default.asp
> > http://www.solidqualitylearning.com/
> > http://www.sqlug.se/
> >
> >
> > "James-Aus" <JamesAus@.discussions.microsoft.com> wrote in message
> > news:7A46C301-BBF6-4D55-AFC0-52939FE2877F@.microsoft.com...
> > > Given that the secondary server can be configured in standby mode,
what
> > is
> > > the minimum SQL Server licensing requirement for the secondary
server?
> > >
> > > thanks in advance
> > > James
> >
> >
>
>

Monday, February 20, 2012

Log Shipping - SQL Clustering environment

Hi all,
I have configured two node SQL cluster with default instance and SAN as shared disk.
I have also configured log shipping on primary server which uses maintenance plan to
backup, copy and restore transaction logs to secondary server in remote location.
My questions are:
1) If failover happens, what would be the impact on log shipping?
2) How would i accomplish the log shipping automation without any interruption even if
the cluster failover occurs?
Dear Sentil,
Setting up Log Shipping involves using a share to backup the transaction
logs to. The share will be used by the copy job to pick up the transaction
log backup file and save it to the default backup directory on the restore
(or secondary) server. The files will then be used by the load job. The
file share has to be accessible at all times for the copy job to continue
copying the transaction log backup files.
In a Cluster environment, file shares are cluster resources and hence if
they are not setup as such, they will be not available when the cluster
resources failover to a different node causing log shipping copy job on the
secondary server to not copy any files.
Consider a situation where we have
Server1 -- Node 1
Server2 -- Node 2
VirtualServerName ServerV
If we create a share on a shared disk drive E owned by Server1 and called
"logshipping", the share can be accessed using the unc name
\\ServerV\logshipping. IF the shared disk is now failed over to Server2 for
any reason, the share \\ServerV\logshipping will not be available as a file
share because it was local to the Server1.
Hence, to get around this, please follow KB article "224967 How to Create
File Shares on a Cluster http://support.microsoft.com/?id=224967" to setup
file share resources and use it for log shipping.
Thanks,
Vikram
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.

Log Shipping - SQL Clustering environment

Hi all,
I have configured two node SQL cluster with default instance and SAN as shared disk.
I have also configured log shipping on primary server which uses maintenance plan to
backup, copy and restore transaction logs to secondary server in remote location.
My questions are:
1) If failover happens, what would be the impact on log shipping?
2) How would i accomplish the log shipping automation without any interruption even if
the cluster failover occurs?Dear Sentil,
Setting up Log Shipping involves using a share to backup the transaction
logs to. The share will be used by the copy job to pick up the transaction
log backup file and save it to the default backup directory on the restore
(or secondary) server. The files will then be used by the load job. The
file share has to be accessible at all times for the copy job to continue
copying the transaction log backup files.
In a Cluster environment, file shares are cluster resources and hence if
they are not setup as such, they will be not available when the cluster
resources failover to a different node causing log shipping copy job on the
secondary server to not copy any files.
Consider a situation where we have
Server1 -- Node 1
Server2 -- Node 2
VirtualServerName ServerV
If we create a share on a shared disk drive E owned by Server1 and called
"logshipping", the share can be accessed using the unc name
\\ServerV\logshipping. IF the shared disk is now failed over to Server2 for
any reason, the share \\ServerV\logshipping will not be available as a file
share because it was local to the Server1.
Hence, to get around this, please follow KB article "224967 How to Create
File Shares on a Cluster http://support.microsoft.com/?id=224967" to setup
file share resources and use it for log shipping.
Thanks,
Vikram
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.

Log Shipping - SQL Clustering environment

Hi all,
I have configured two node SQL cluster with default instance and SAN as shar
ed disk.
I have also configured log shipping on primary server which uses maintenance
plan to
backup, copy and restore transaction logs to secondary server in remote loca
tion.
My questions are:
1) If failover happens, what would be the impact on log shipping?
2) How would i accomplish the log shipping automation without any interrupti
on even if
the cluster failover occurs?Dear Sentil,
Setting up Log Shipping involves using a share to backup the transaction
logs to. The share will be used by the copy job to pick up the transaction
log backup file and save it to the default backup directory on the restore
(or secondary) server. The files will then be used by the load job. The
file share has to be accessible at all times for the copy job to continue
copying the transaction log backup files.
In a Cluster environment, file shares are cluster resources and hence if
they are not setup as such, they will be not available when the cluster
resources failover to a different node causing log shipping copy job on the
secondary server to not copy any files.
Consider a situation where we have
Server1 -- Node 1
Server2 -- Node 2
VirtualServerName ServerV
If we create a share on a shared disk drive E owned by Server1 and called
"logshipping", the share can be accessed using the unc name
\\ServerV\logshipping. IF the shared disk is now failed over to Server2 for
any reason, the share \\ServerV\logshipping will not be available as a file
share because it was local to the Server1.
Hence, to get around this, please follow KB article "224967 How to Create
File Shares on a Cluster http://support.microsoft.com/?id=224967" to setup
file share resources and use it for log shipping.
Thanks,
Vikram
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.

Wednesday, March 28, 2012

log shipping sql 2005 database remains in (restoring...) mode

log shipping sql 2005 database remains in (restoring...) mode

log shipping sql 2005 database remains in (restoring...) mode

Log Shipping Role Reversal

Friday, March 23, 2012

log shipping problem

log shipping problem

Monday, March 19, 2012

Log Shipping Monitor

Monday, March 12, 2012

Log Shipping from 2000 to 2005

Log Shipping from 2000 to 2005

Log Shipping from 2000 to 2005

Log Shipping for multiple databases

Friday, March 9, 2012

log shipping error

Wednesday, March 7, 2012

Log Shipping and SQL Server Licence Requirement

Log Shipping and SQL Server Licence Requirement

Log Shipping and SQL Server Licence Requirement

Monday, February 20, 2012

Log Shipping - SQL Clustering environment

Log Shipping - SQL Clustering environment

Log Shipping - SQL Clustering environment

Log shipping alerts

Blog Archive

About Me