Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 min
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?
I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.
|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?

Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 min
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?sql

Log Shipping Sql server 2005 enterprise edition

require some urgent help on Sql Server 2005 Log Shipping
Our Project :
Seprate Read & Write Process by building Report Server using Sql
Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
Windows 2003 (64- bit) Server as Production server we had implemented Log
Shipping on the production server which will transfer logs after every 15 mi
n
to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both secondry
databases are in Standby / ReadOnly Mode .The system is working fine. All
logs are transffered sucessfully. we had tried online indexing on production
server which works fine.
Problem :--
Our main purpose of two standby server is 1st standby server will be
utilised as Report Server and 2nd standby Server we want to take full backup
everyday but when we try to take backup of 2nd standby server it give us
error like "cannot take backup the database is in warm standby mode".We
cannot take backup from Production server as it is required for online
indexing and data updation during night hrs.
OR
Is there any other way to take full backup from secondry servers?
We require help on following issues
1) How to take full backup of 2nd stand by server?
2) If Log shipping Failed How to restart Log Shipping without restoring a
new backup copy on secondry servers?
3) In this case how to make all server available with minimum downtime?
4) Is the process is Technically Perfect?I think you have a problem here.
Only way i can think of is .Stop the standy mode -recover the database with
last log file. And make a fullbackup.|||A database that is in STANDBY mode is technically in a RESTORING state with
a special stop point. You cannot back up a database while it is restoring.
Therefore, you cannot back up a log shipping target database.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"PankajP" <PankajP@.discussions.microsoft.com> wrote in message
news:49EB67A0-288F-4339-9F01-5EEBBB2CF86C@.microsoft.com...
> require some urgent help on Sql Server 2005 Log Shipping
> Our Project :
> Seprate Read & Write Process by building Report Server using Sql
> Server 2005 Log Shipping SQL Server 2005 Enterprise Edition installed on
> Windows 2003 (64- bit) Server as Production server we had implemented Log
> Shipping on the production server which will transfer logs after every 15
> min
> to two Sql Server 2005 standby servers.(Windows 2003 64-bit). Both
> secondry
> databases are in Standby / ReadOnly Mode .The system is working fine. All
> logs are transffered sucessfully. we had tried online indexing on
> production
> server which works fine.
> Problem :--
> Our main purpose of two standby server is 1st standby server will be
> utilised as Report Server and 2nd standby Server we want to take full
> backup
> everyday but when we try to take backup of 2nd standby server it give us
> error like "cannot take backup the database is in warm standby mode".We
> cannot take backup from Production server as it is required for online
> indexing and data updation during night hrs.
> OR
> Is there any other way to take full backup from secondry servers?
> We require help on following issues
> 1) How to take full backup of 2nd stand by server?
> 2) If Log shipping Failed How to restart Log Shipping without restoring a
> new backup copy on secondry servers?
> 3) In this case how to make all server available with minimum downtime?
> 4) Is the process is Technically Perfect?

log shipping monitor report error

I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:

Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.

There is nothing special about the configuration. Any ideas?

Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||

I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.

As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").

The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.

The old configuration data is probably causing the incorrect alerts you are seeing.

|||

Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.

Thank you

|||

Hi Mark,

I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.

I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.

For,

select * from dbo.log_shipping_monitor_secondary

I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.

So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.

Thanks in anticipation.

Amit

sql

log shipping monitor report error

I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:

Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.

There is nothing special about the configuration. Any ideas?

Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||

I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.

As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").

The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.

The old configuration data is probably causing the incorrect alerts you are seeing.

|||

Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.

Thank you

|||

Hi Mark,

I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.

I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.

For,

select * from dbo.log_shipping_monitor_secondary

I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.

So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.

Thanks in anticipation.

Amit

log shipping monitor report error

I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:

Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.

There is nothing special about the configuration. Any ideas?

Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||

I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.

As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").

The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.

The old configuration data is probably causing the incorrect alerts you are seeing.

|||

Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.

Thank you

|||

Hi Mark,

I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.

I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.

For,

select * from dbo.log_shipping_monitor_secondary

I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.

So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.

Thanks in anticipation.

Amit

log shipping monitor report error

I have SQL Server 2005 log shipping setup with primary/secondary configuration. I can confirm from the logs that log shipping is working without issue, however, reports generated from the monitor server show this message:

Violation of PRIMARY KEY constraint 'PK__#log_shipping_mo__3ABBDC91'. Cannot insert duplicate key in object 'dbo.#log_shipping_monitor'. The statement has been terminated.

There is nothing special about the configuration. Any ideas?

Clear out the log on Log shipping monitor and ensure the log shipping is working properly on secondary server too.|||Log shipping is working properly on the secondary server. The error is generated when I try to view the Log Shipping Status report on the secondary server. The monitor server instance is also throwing incorrect alerts.|||

I think the problem you are seeing is related to some old information being present in the tables used to store log shipping configuration. There are some scenarios where this can happen and it causes the problem you reported in your first post. We are working on correcting this in a future release.

As you can tell from the error, the problem is caused by an insert to a temp table causing a PK constraint violation. The PK for the temp table is server name and database name. This error is normally caused by old configuration being present in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary. You can view the contents of these tables directly (in msdb) or use some supplied help SP's (see BOL topic titled "Log Shipping Tables and Stored Procedures").

The workaround is to remove the old rows from log_shipping_monitor_primary and/or log_shipping_monitor_secondary tables. Can you determine that you do indeed have stale data in the log shipping tables. If this is the case I can work with you on how to remove the old rows.

The old configuration data is probably causing the incorrect alerts you are seeing.

|||

Hi, Is that possible for you to show how to delete the old data in the tables log_shipping_monitor_primary and/or log_shipping_monitor_secondary.

Thank you

|||

Hi Mark,

I am getting a similar error when I try to run the report on the primary server. The report on the secondary server which is also the monitor runs fine.

I queried the tables mentioned by you and got one row in each. FYI, I have only one DB on the primary server being log shipped to the secondary.

For,

select * from dbo.log_shipping_monitor_secondary

I am geeting null values for last_copied_file, last_copied_date, last_copied_date_utc and last restored_file. However, I know that the log shipping is working well for the database.

So How do I go about correcting the report? Should I delete the row in log_shipping_monitor_secondary? In log_shipping_monitor_primary the information is up to date and correct.

Thanks in anticipation.

Amit

Log shipping and Full Text

I setup log shipping on my production server which is a part of Replication
and went ahead and created a report server using log Shipping however my
Report server is missing Full Text and it don't allow me to create it saying
it is read only database.
I am running SQL server 2000 with service Pack 2
Is there any way I can also bring Full text on Report Server my databasde is
huge and full text takes couple of days to create so I was exploring a
solution that can take full txet catalog from my production server and copy
it to Reprot Server.
Thanks
Tanweer
Hilary Cotter
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
"Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
news:820818D0-7F18-45F0-8B82-9ACBF539F8BE@.microsoft.com...
> I setup log shipping on my production server which is a part of
Replication
> and went ahead and created a report server using log Shipping however my
> Report server is missing Full Text and it don't allow me to create it
saying
> it is read only database.
> I am running SQL server 2000 with service Pack 2
> Is there any way I can also bring Full text on Report Server my databasde
is
> huge and full text takes couple of days to create so I was exploring a
> solution that can take full txet catalog from my production server and
copy
> it to Reprot Server.
> Thanks
> Tanweer
|||oops, that went out prematurely. You could follow these steps every time you
want your database synchronized -
http://support.microsoft.com/default...b;en-us;240867
Or you could use replication. If you use replication you will have to build
your tables and full-text indexes in advance on the subscriber. Then in your
article properties make sure you select the delete all data option.
SQL 2005 replication will support this directly.
Hilary Cotter
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
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:u$9GFtsaFHA.3488@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
>
> --
> Hilary Cotter
> 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
> "Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
> news:820818D0-7F18-45F0-8B82-9ACBF539F8BE@.microsoft.com...
> Replication
> saying
databasde
> is
> copy
>
|||However I want this to be automatic every 3 hours the report server need to
have the same catalog as the Production Server.
What I can do to automate this process.
Thanks
Tanweer
"Hilary Cotter" wrote:

> oops, that went out prematurely. You could follow these steps every time you
> want your database synchronized -
> http://support.microsoft.com/default...b;en-us;240867
> Or you could use replication. If you use replication you will have to build
> your tables and full-text indexes in advance on the subscriber. Then in your
> article properties make sure you select the delete all data option.
> SQL 2005 replication will support this directly.
> --
> Hilary Cotter
> 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
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:u$9GFtsaFHA.3488@.tk2msftngp13.phx.gbl...
> databasde
>
>
|||This can be automated.
Hilary Cotter
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
"Tanweer" <Tanweer@.discussions.microsoft.com> wrote in message
news:0E2E76B8-B1FE-4A1E-BE73-D1C949A2AB6A@.microsoft.com...
> However I want this to be automatic every 3 hours the report server need
to[vbcol=seagreen]
> have the same catalog as the Production Server.
> What I can do to automate this process.
> Thanks
> Tanweer
> "Hilary Cotter" wrote:
you[vbcol=seagreen]
build[vbcol=seagreen]
your[vbcol=seagreen]
however my[vbcol=seagreen]
it[vbcol=seagreen]
exploring a[vbcol=seagreen]
and[vbcol=seagreen]