Log shipping issue

I am getting the below alert in transaction log shipping status report.
I would like to remove the below alert.
here you can see that primary server
[Server01\Insta1].[DB01] is already have a good health status with secondary server --[Server02\InstaXa].[DB01]
Please let me know how can i remove this alert from transaction log shipping status report.

Hi,
how do you expect to help you with just some screenshot. Did you tried yourself to find out why Logshipping is out of sync. Go and check LS backup and restore and copy job see which one is failing.
As per screenshot none of backup or copy job is executed which makes me think the Log shipping for this database is removed and you did not even tried asking within team who and when this was removed.
From my side you can just go to jobs and either
remove the Logshipping or disable the job
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

SQL Log shipping ISSUE

Hi All,
I have a maintenance plan set to run FULL backup for the database every night 12:00 AM and differential backups hourly. I also configured Log shipping for few databases. My question is: should I remove the log shipping database from maintenance plan both
full and differential?
My concern is that log shipping will do backup and maintenance plan will also backup the DBs. Will both interfere each other? The log shipping takes the backup during the same time period (Because I put the default settings while LS setup)
Should I exclude Log shipping DB’s from maintenance plan?
Your response is important to me.
Thanks,
DBA
DBA

Should I exclude Log shipping DB’s from maintenance plan?
Hi,
No you should not as such but since your database is configured for logshipping differential backup might not be required but Full backup you must keep taking.
Both diff and full backup would not affect logshipping.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Dataguard log shipping issue

Hello,i have just set up the physical standby first time in 11g r2 and sucessfully completed.but log is not shipped to standby ,tnsname.ora and listener.ora have all the required entries and working properly,no any error seen in the alert log of both physical and standby .it will be appreciable if any one give me the clue to debug the issue..
Thanks,
Pankaj

Post results from ( on Primary )
show parameter LOG_ARCHIVE_DEST_STATE_2
Best Regards
mseberg

Transaction log shipping restore with standby failed: log file corrupted

Restore transaction log failed and I get this error: for only 04 no of database in same SQL server, renaming are working fine.
Date
9/10/2014 6:09:27 AM
Log
Job History (LSRestore_DATA_TPSSYS)
Step ID
1
Server
DATADR
Job Name
LSRestore_DATA_TPSSYS
Step Name
Log shipping restore log job step.
Duration
00:00:03
Sql Severity        0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted
0
Message
2014-09-10 06:09:30.37 *** Error: Could not apply log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' to secondary database 'TPSSYS'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: An error occurred while processing the log for database 'TPSSYS'.
If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'TPSSYS' (13:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
Processed 0 pages for database 'TPSSYS', file 'TPSSYS' on file 1.
Processed 1 pages for database 'TPSSYS', file 'TPSSYS_log' on file 1.(.Net SqlClient Data Provider) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Skipping log backup file '\\10.227.32.27\LsSecondery\TPSSYS\TPSSYS_20140910003724.trn' for secondary database 'TPSSYS' because the file could not be verified.
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: An error occurred restoring the database access mode.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteScalar requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 Deleting old log backup files. Primary Database: 'TPSSYS'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 The restore operation completed with errors. Secondary ID: 'dd25135a-24dd-4642-83d2-424f29e9e04c'
2014-09-10 06:09:30.37 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.37 *** Error: Could not cleanup history.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-10 06:09:30.37 *** Error: ExecuteNonQuery requires an open and available Connection. The connection's current state is closed.(System.Data) ***
2014-09-10 06:09:30.38 ----- END OF TRANSACTION LOG RESTORE
Exit Status: 1 (Error)

I Have restore the database to new server and check with new log shipping but its give this same error again, If it is network issue i believe issue need to occur on every database in that server with log shipping configuration
error :
Message
2014-09-12 10:50:03.18   *** Error: Could not apply log backup file 'E:\LsSecondery\EAPDAT\EAPDAT_20140912051511.trn' to secondary database 'EAPDAT'.(Microsoft.SqlServer.Management.LogShipping) ***
2014-09-12 10:50:03.18   *** Error: An error occurred while processing the log for database 'EAPDAT'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
An error occurred during recovery, preventing the database 'EAPDAT' (8:0) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
RESTORE LOG is terminating abnormally.
can this happened due to data base or log file corruption, if so how can i check on that to verify the issue
Its not necessary if the issue is with network it would happen every day IMO it basically happens when load on network is high and you transfer log file which is big in size.
As per message database engine was not able to restore log backup and said that you must rebuild log because it did not find out log to be consistent. From here it seems log corruption.
Is it the same log file you restored ? if that is the case since log file was corrupt it would ofcourse give error on wehatever server you restore.
Can you try creating logshipping on new server by taking fresh full and log backup and see if you get issue there as well. I would also say you to raise case with Microsoft and let them tell what is root cause to this problem
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Sql server log shipping space consumption

I have implemented sql server logs shipping from hq to dr server
The secondary databases are in standby mode .
The issue is that after configuring it , my dr server is running out of space very rapidly
I have checked the log shipping folders where the trn files resides and they are of very decent size , and the retention is configured for twenty four hours
I checked the secondary databases and their size is exactly same as that of the corresponding primary databases
Could you guys please help me out in identifying the reason behind this odd space increase
I would be grateful if you could point me to some online resources that explains this matter with depth

The retention is happening . I have checked the folders they do not have records older then 24 hours .
I dont know may be its because in the secondary server (Dr) there is no full backup job working , is it because of this the ldf file is getting bigger and bigger but again I far as my understanding goes we cannot take a database full backup in the stand
by mode .
The TLog files of log shipped DBs on the secondary will be same size as that of primary. The only way to shrink the TLog files on secondary (I am not advising you to do this) is to shrink them on the primary, force-start the TLog backup job, then the copy
job, then the restore job on the secondary, which will sync the size of the TLog file on the secondary.
If you have allocated the same sized disk on both primary and secondary for TLog files, then check if the Volume Shadow Copy is consuming the space on the secondary
Satish Kartan www.sqlfood.com

Log shipping job failing

HI guys,
We are using SQL SERVER 2005.
I am having a LSAlert_Serv job and this job runs the system stored procedure sys.sp_check_log_shipping_monitor_alert.
when this job is run I am getting the following error message:
Here is the error message I am getting :
The log shipping primary database SHARP has backup threshold of 60 minutes and has not performed
a backup log operation for 7368 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed.
The database named SHARP that is mentioned in the above error message is now moved to another
server.
When I looked into the stored procedure and when i ran the below query from the Stored procedure
select primary_server
,primary_database
,isnull(threshold_alert, 14420)
,backup_threshold
,cast(0 as int)
from msdb.dbo.log_shipping_monitor_primary
where threshold_alert_enabled = 1
I can still see the database SHARP in the table msdb.dbo.log_shipping_monitor_primary. So,
is it the reason for failure? If so, what to do to update the table msdb.dbo.log_shipping_monitor_primary and to fix the issue.
Thanks

The database named SHARP that is mentioned in the above error message is now moved to another server.
When I looked into the stored procedure and when i ran the below query from the Stored procedure :
Since you said you moved database to different server can you please check that SQL Server service account( in new server where you moved database) has full permissions on folder where you have configured log backup job to back the transaction logs.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Log shipping is not restoring log files ata particular time

Hi,
I have configured log shipping and it restores all the log files upto a particular time after which it throws error and not in consistent sate. I tried deleting and again configuring log shipping couple of times but no success. Can any one tell me
how to prevent it as I have already configured log shipping from another server to same destination server and it is working fine for more than 1 year? The new configuration is only throwing errors in restoration job.
Thanks,
Preetha

Message
2014-07-21 14:00:21.62   *** Error: The log backup file 'E:\Program Files\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\Qcforecasting_log\Qcforecasting_20140721034526.trn' was verified but could not be applied to secondary database 'Qcforecasting'.(Microsoft.SqlServer.Management.LogShipping)
2014-07-21 14:00:21.62   Deleting old log backup files. Primary Database: 'Qcforecasting'
2014-07-21 14:00:21.62   The restore operation completed with errors. Secondary ID: '46b20de0-0ccf-4411-b810-2bd82200ead8'
2014-07-21 14:00:21.63   ----- END OF TRANSACTION LOG RESTORE     -----
The same file was tried thrice and it threw error all the 3 times.
But when I manually restored the Qcforecasting_20140721034526 transaction log it worked. Not sure why this is happening. After the manual restoration it worked fine for one run.ow waiting for the other to complete.
This seems strange to me error points to fact that backup was consistent but could not be applied because may be restore process found out that log backup was not it correct sequence or another log backup which was accidentally taken can be applied.
But then you said you can apply this manually then this must be related to permission. Because if it can restore manually it can do it with job unless agent account has some permission issue.
Ofcourse more logs would help
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

In Log-shipping what is load delay period on secondary server - Skipping log backup file since load delay period has not expired ....

During logshipping, job on secondary server is ran successfully BUT give this information
"Skipping log backup file since load delay period has not expired ...."
What is this "Load delay period" ? Can we configure this somehow, somewhere ?
NOTE : The value on "Restore Transasction Log tab", Delay Restoring backups at least = Default (zero minutes)
Thanks
Think BIG but Positive, may be GLOBAL better UNIVERSAL.

How to get the LSBackup, LSCopy, and LSRestore jobs back in sync...
Last I posted the issue was that my trn backups were not being copied from Primary to Secondary.
I found upon further inspection of the LS related tables in MSDB the following likely candidates for adjustment:
1) dbo.log_shipping_monitor_secondary, column last_copied_file
change last copied file column to something older than the file that is stuck. For example, the value in the table was
E:\SQLLogShip\myDB_20140527150001.trn
I changed last_copied_file to E:\SQLLogShip\myDB_20140525235000.trn. Note that this is just a made up file name that is a few minutes before the actual file that I would like to restore (myDB_2014525235428.trn). 4 mins and 28 seconds before, to
be exact.
LSCOPY runs and voila! now it is copied from primary to secondary. That appears to be the only change needed to get the copy going again.
2) For LSRestore, see the MSDB table dbo.log_shipping_monitor_secondary, change
last_restored_file
again I used the made up file E:\SQLLogShip\myDB_20140525235000.trn
LSRESTORE runs and my just copied myDB_2014525235428.trn is restored
** note that
dbo.log_shipping_secondary_databases also has a last_restored_file column - this did not seem to have any effect, though I see that it updates after completing the above and LSRestore has run successfully, so now it is correct as well
3) LSBackup job is still not running, the job still has a last run date in the future. Could just leave it and eventually it will come right, but I made a fairly significant time change, plus it's all an experiment....back to MSDB.
look at dbo.sysjobs, get the job_id of your LSBackup job
edit dbo.sysjobschedules - change next_run_date next_run_time as needed to a datetime before the current time, or when you would like the job to start running.
I wouldn't be so cavalier with data that was important, but that's the benefit of being in Test, and it appears that these time comparisons are very rudimentary - a value in the relevant log shipping table and the name of the trn file. That said, if you
were facing a problem of this nature due to lost trn files, corrupted, or some similar scenario, this wouldn't fix your problem, though it _might_ allow you to continue? But in my case I know I have all the trn files, it's just the time that changed, in this
case on my Primary server, and thus the names of the trn logs got out sync.

Shrink Log file in log shipping and change the database state from Standby to No recovery mode

Hello all,
I have configured sql server 2008 R2 log shipping for some databases and I have two issues:
can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No
Truncate" option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge and it will take time to restore in the DR site, so the reconfiguration
is not an option :(
how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need
to do this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator

1. can I shrink the log file for these databases: If I change the primary database from full to simple and shrink the log file then change it back to full recovery mode the log shipping will fail, I've seen some answers talked about using "No Truncate"
option, but as I know this option will not affect the log file and it will shrink the data file only.
I also can't create maintenance to reconfigure the log shipping every time I want to shrink the log file because the database size is huge
and it will take time to restore in the DR site, so the reconfiguration is not an option :(
2. how can I change the secondary database state from Standby to No recovery mode? I tried to change it from the wizard and wait until the next restore for the transaction log backup, but the job failed and the error was: "the step failed". I need to do
this to change the mdf and ldf file location for the secondary databases.
can any one help?
Thanks in advance,
Faris ALMasri
Database Administrator
1. If you change recovery model of database in logshipping to simple and back to full Logshipping will break and logs wont be resored on Secondary server as log chain will be broken.You can shrink log file of primary database but why would you need that
what is schedule of log backup. Frequent log backup is already taking care of log files why to shrink it and create performance load on system when log file will ultimately grow and since because instant file initilaization is not for Log files it takes time
to grow and thus slows performace.
You said you want to shrink as Database size is huge is it huge or does it have lots of free space. dont worry about data file free space it will eventually be utilized by SQL server when more data comes
2. You are following wrong method changing state to no recovery would not even allow you to run select queries which you can run in Standby mode. Please refer below link to move Secondary data and log files
http://www.mssqltips.com/sqlservertip/2836/steps-to-move-sql-server-log-shipping-secondary-database-files/
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

2012 SQL server log shipping problem

Scenario:
Site 1: 2012 Enterprise version 64-bit (11.0.3128.0) - Log shipping is enabled for four databases. Shipping logs over a WAN every 15 minutes to a DR site.
Site 2: 2012 Enterprise version 64-bit (11.0.3128.0) - Secondary server for log shipping.
Site two functions for a period of time with the databases in Standby/Read-Only mode, then the databases will mysteriously switch to "restoring..." mode and error 14420 Severity 16 State 1 will appear in the logs. I have located kb2987585
and this did apply to the situtation as the sector sizes were different, so as a work around I moved the log shipping shared folder on the secondary server to a drive with the same sector settings as the primary server but this did not resolve the issue.
Has anyone had this issue and can you offer potential solutions?
Thank you -

Hi,
I still consider the bug raised in
https://support.microsoft.com/kb/2987585?wa=wsignin1.0
is not fixed. I have seen lot of other users complaining. But at this point I need to have look at SQL Server errorlog
sp_readerrorlog
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Failed to send an environment change notification to a log shipping partner node while revalidating the login???

Hi All,
Recently I received the following error message in my SQL instance (Microsoft SQL Server 2012 - 11.0.5532.0 (X64)) :-
23/02/2015 5:09:05 PM
Error: 18456, Severity: 14, State: 51.
Login failed for user 'webapp'. Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. [CLIENT: 192.168.82.18]
23/02/2015 5:09:05 PM
Error: 18056, Severity: 20, State: 51.
The client was unable to reuse a session with SPID 98, which had been reset for connection pooling. The failure ID is 51. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this
error message.
I am using database mirroring instead of log shipping actually but why there's some log shipping related error message coming out? Is it some kind of bug error message? I am just wondering and hope can get some little help about this.
Thanks and highly appreciated.
Best Regards,
Han

Hi Harn,
According to the error message, as my understanding, the issue could be due to that the login 'webapp' has no access to the default database which is configured in log shipping. The database is offline or removed. You could run the command (select * from
msdb.dbo.log_shipping_primary_secondaries) to verify if that database is configured in log shipping. Another cause is that parallel execution occupies multiple worker threads. When you have many parallel executions, the number of available worker threads might
run out and you fail to login. Please help to post complete SQL Server error log for analysis.
To work around the issue, you could follow the two solutions below.
1.Change the default database for the login 'webapp' according to the following article:
https://msdn.microsoft.com/en-us/library/ms189828.aspx
2.Reduce the 'max degree of parallelism' as the following example.
exec sp_configure 'max degree of parallelism', 4;
GO
RECONFIGURE WITH OVERRIDE;
GO
Regards,
Michelle Li

Best way of handle Log Shipping in Physical Movement of SQL Server

Hi All
We are moving SQL Server physically from one rack to another in data centre. Just power off and move the server and network link up and power on and bring to same state before power off.
One of Server 2005 have Log shipping active. What is best way to maintain Log Shipping during this physical movement. I do not want to remove log shipping and re-configure from scratch.
Need help for clean and safe method to carry this activity.
Thanks in Advance

Thanks for reply...
No... I am not asking RACK migration. Just SQL SERVER...Here are my steps that I am like to do...
1. Stop application(s) that connect to the databases on this Server
Correct
2. Note of account under which SQL Server running for the purpose of permission of this account on folder(s) for L Log Shipping
OK
2. Stop Jobs using via making script for disable and enable jobs
Here I have doubt on Log Shipping jobs disable and enable that
You can use job( tsql) but why not use GUI.Log into SQL Server expand SQL server agent RK on job and disable it.
a. I should stop LS jobs manually as you recommended but not while running em I right?
Yes see job activity monitor on both primary and secondary server.It will show status executing for jobs,look out for LS jobs.
b. Shall I stop disable jobs first on Secondary or Primary Server?
First disable on Primary and then on secondary.
I faced a issue where shutting down SQL agent on Secondary caused Sec database to go in suspect mode.So make sure while you shutdown agent no job is running.If restore log job is running let it complete and then disable the job
c. On which server I should enable LS jobs first?
Primary
3. Stop SQL Server Services.
Run sp_who2 or select * from sys.sysprocessess to see any active transaction.Then move accordingly.
AND take same steps in reverse manner when power on after physical migration of Box.
Pls advise
Hope this helps
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

DBCC SHRINKFILE with NOTRUNCATE has any performance impact in log shipping?

Hi All,
To procure space I'm suggested to use below command on primary database in log shipping and I just want
to clarify whether it has any performance impact on primary database in log shipping and also is it a recommended practice to use the below command
in regular intervals in
case the log is using much space of the drive. Please suggest on this. Thank You.
"DBCC
SHRINKFILE ('CommonDB_LoadTest_log', 2048, NOTRUNCATE)"
Regards,
Kalyan
----Learners Curiosity Never Ends----

Hi Kalyan \ Shanky
I was not clear in linked conversation so adding some thing :
As per http://msdn.microsoft.com/en-us//library/ms189493.aspx
----->TRUNCATEONLY is applicable only to data files.
BUT
As per : http://technet.microsoft.com/en-us/library/ms190488.aspx
TRUNCATEONLY affects the log file.
And i also tried , it does works.
Now Truncateonly : Releases all free space at the end of the file to the operating system but does not perform any page movement inside the file. The data file is shrunk only to the last allocated extent. target_percent is ignored if specified
with TRUNCATEONLY.
So
1. if i am removing non used space it will not effect log shiping or no log chain will broke.
2. If you clear unsued space it will not touch existing data. no performance issue
3. If you clear space and then due to other operation log file will auto grow it will put unnecessary pressure on database to allocate disk every time. So once you find the max growth of log file let it be as any how again it will grow to same size.
4. Shrinking log file is not recommeded if its again and again reaching to same size . Until unless you have space crunch
Thanks Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem

SQL Server 2012 - DB Mirroring + Log Shipping + Multi-Subnet

Hi again,
So AG would be nice to have, but considering the costs of getting it, well, it is a no go for me at the moment (This is like a 1:20 ratio considering Std comes with server licencing and enterprise is only per 2 cores).
So, having 2 sites, with different subnet. Is it possible to configure automatic failover for DBM ? We are running Windows 2012 R2 which supports multi subnet failover. But what about DBM in this case ?
Can the witness be configured on a third site ? (I was thinking of having the following weights: Site 1:2, Site 2:1, Quorum:2 just to have no reconfig to do in case of Datacenter failure)
Also, in order to offload some of the backup load as the DB are somewhat big (1TB), I was thinking of having one additional node per site to which the logs are shipped and that are used to run the backups. The question being, is it possible to log ship from
each "primary" on each site rather than have the primary on site 1 do it for all the servers across the subnets ?
It would be a setup like this:
Site 1 Primary <---DBM---> Site 2 Primary (Hot failover)
Site 1 Primary <---LogShips---> Site 1 Secondary
Site 2 Primary <---LogShips---> Site 2 Secondary
And thus reduces the load on the link between the 2 sites.
I do hope to see AG in the future for Std as they are removing DBM in the next version.
Thanks,

The idea behind the cluster is to have a single IP on which the applications can reach the DB in case of a failover to the secondary site.
This requires a failover cluster instance - mirroring does not work this way.
Because as far as I understand it, either the application has to be aware and able to switch to the new DB primary, or we can use a multisubnet cluster or we can manually reconfigure the applications (so painful)
Mirroring has the failover partner attribute in the connection string that can be utilized. A multi-subnet cluster would require, again, a FCI.
AFAIK, DBM is not recommended for more than 10 DB on an instance due to the worker threads.
"It depends". There can be worker thread issues, but this will entirely depend on your hardware and architecture of processor/SQL Server. In 32-bit world it'll eat up all of your worker threads. In 64-bit world on a decent server it shouldn't be
a problem to have 10-20 out of the box.
I don't mind having to failover multiple database residing on the same instance and having to setup them per DB.
If any of your databases have a dependency on one another, this isn't going to work well as one database could be failed over and another might not be. Just food for thought.
What it sound like you really want is a failover cluster instance and use log shipping to have a "readable copy" somewhere even if it is behind on time. The problem comes in is that a cluster all has to be in the same domain and part of the same
cluster. Your thoughts involve a separate cluster - so I'm not sure why two different ones unless you have multiple environments you're trying to add some HA to.
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

The log shipping restore job restores a corrupted transaction log backup to a secondary database

Dear Sir,
I have primary sql instances in cluster node and it is configured with log shipping for DR system.
The instance fails over before the log shipping backup job finishes. Therefore, a corrupted transaction log backup is generated.how to handle the logshipping without break and how to know this transaction back is damaged.
Cheers,

Dear Sir,
I have primary sql instances in cluster node and it is configured with log shipping for DR system.
The instance fails over before the log shipping backup job finishes. Therefore, a corrupted transaction log backup is generated.how to handle the logshipping without break and how to know this transaction back is damaged.
Cheers,
Well when failover happens SQL Server is stopped and restarted on other node. So when SQL Server is stopped and it is doing Log backup the backup operation would stop and there would be no trn files . The backup operation wont complete and hence no backup
information would be stored in SQL Server MSDB and no .trn file would be generated.
You can run restore verifyonly on .trn file to see whether it is damaged or not. Logshipping is quite flexible even if previous log backup did not complete the next wont be affected because SQL Server has no information about whether backup completed
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Log shipping issue

Similar Messages

Maybe you are looking for