Re: Read your article on Log Shipping....

0 views

Skip to first unread message

barathan esakiappan

unread,

Jul 25, 2008, 6:09:19 AM7/25/08

to Larry Dinsmore, sqlth...@googlegroups.com

Dear Larry Dinsmore

Greetings!

That may be the cause in your log shipping , if your Maintenance Plan storing the transaction log backup in a different folder other than the one specified in LOG Shipping settings. If you use different folders for Maintenance plan and log shipping then the log chain sequence will not be maintained. So Log shipping is failed. In this case , the purpose of taking transaction log will also fail because of the chain of log sequences are not maintained.

So avoid having maintenance plan for transaction log backup while having log shipping. If unaviodable then use the same folder for storing log backups the both MP and LOG Shipping.

May be this will solve your problem. Let me know the status.

One more Question I want to ask you ... !?

Where are you from and what is your role in your job ...!?

With Regards

B.Esakkiappan

SQLThoughts

Discussions @ http://groups.google.com/group/sqlthoughts

----- Original Message ----
From: Larry Dinsmore <ldin...@klc.org>
To: barathan esakiappan <b_e...@yahoo.com>
Sent: Thursday, 24 July, 2008 8:57:25 PM
Subject: RE: Read your article on Log Shipping....

Thank you for your response and I am sorry it took me so long to reply. I checked the privileges and they seem to be set correctly.

Here’s what I think might be the problem. In addition to the log shipping there is a maintenance plan that backs up the transaction logs every hour (and does not ship). Is that killing me?

From: barathan esakiappan [mailto:b_e...@yahoo.com]
Sent: Monday, July 21, 2008 3:25 AM
To: Larry Dinsmore
Cc: sqlth...@googlegroups.com
Subject: Re: Read your article on Log Shipping....

Dear Larry Dinsmore

Thank you so much for reading my blog SQLThoughts.

This message you got from restore job history may be due to

i) -there is no recent full backup of the database so that the log backups can be performed. Take a full backup of the database for which you configured the LOG Shipping.

ii) Check the privilages for the SQL Server Agent Service user for the folder configured for storing the .trn file ( transaction log backup file ) . This may be a network shared folder for the both cases in which SQL Server in a domain or SQL Server in a non-domain scenarios.

I think any one of the above may solve your problem. Please let me know the feed back!

With Regards

B.Esakkiappan

SQLThoughts

Discussions @ http://groups.google.com/group/sqlthoughts

----- Original Message ----
From: Larry Dinsmore <ldin...@klc.org>
To: b_e...@yahoo.com
Sent: Thursday, 17 July, 2008 6:49:01 PM
Subject: Read your article on Log Shipping....

I really got a lot out of it, thanks. I have log shipping set up and am confused by this message in the restore job history “Skipped log backup file. Secondary DB:….” . Does that mean there was nothing to restore?

Larry Dinsmore

__________________________________________________
This electronic mail transmission is intended solely for the named
individual or entity to which it is addressed and may contain
information that is confidential, proprietary and/or legally
privileged. If you are not the intended recipient, do not read,
copy, retain, forward or otherwise disseminate this message or any
attachment. If you have received this transmission in error, please
notify the Kentucky League of Cities via reply e-mail or at
(859) 977-3700 and delete all copies of the message and any
attachment from your system.
___________________________________________________

Unlimited freedom, unlimited storage. Get it now

Share files, take polls, and make new friends - all under one roof. Click here.

barathan esakiappan

unread,

Jul 31, 2008, 1:08:08 AM7/31/08

to Larry Dinsmore, SQLTHoughts Discussion1, sqlth...@googlegroups.com

Dear Larry Dinsmore

Greetings!

It is nice to hear that your log shipping is working fine.

As the log is shipped in fixed time interval, and all table schema and database file structure changes are logged operations. So you need not worry about the structural changes in the primary Server. It will be automatically reflected in the Secondary Server.

However, adding additional log file or secondary storage files for the primary database requires a special consideration. For further reading in this topic please go to http://support.microsoft.com/kb/286280/

This article will help you more.

With Regards

B.Esakkiappan

SQLThoughts

Discussions @ http://groups.google.com/group/sqlthoughts

----- Original Message ----
From: Larry Dinsmore <ldin...@klc.org>
To: barathan esakiappan <b_e...@yahoo.com>
Sent: Tuesday, 29 July, 2008 7:03:28 PM
Subject: RE: Read your article on Log Shipping....

I modified my log shipping configuration to write the LS trans log backups to the same folder as the maintenance plan AND disabled the transaction log backup portion of the maint plan that had been in place and now it works great!

Thanks so much for your help!

I hope I’m not over staying my welcome but let me ask you this: Do structural changes to the database such as table structure modifications get shipped? My understanding of a transaction log is any data that is added, changed or deleted gets written to the trans log. If that is true then structural changes won’t get sent to the secondary server. Do you have to make the changes manually on both databases? Seems rather inefficient or maybe tedious is the better word.