February 14, 2012 at 11:09 am
Hi ,
1.can i take full backup of the Logshipping database??
any impact on that database ( i mean LSN mismatching probs)
2.Log-shipping Working properly.
so please suggest me..we can configure MP(Maintenance plan) on log-shipping Database
1.Full backup,2.diff back up,3.database integrity,update stats,reindex and reorganize.dis is My idea.
so 4.can i take Tlog backup of logshipping database through MP? is it possible or any Mismatch of logship database.
Please suggest me...Good MP for Logshipping Databases.???(As production server 6TB)
please tell me ..exactly MP for logshipping DB's????(i know log shipping means automatically restoring Tlog backups)
3.for example every 3 mins Tlog backups are coming Through logshipping.so i haven't check restore job are failure last one hour and after database crash,dis scenario 1hour data loss..dis situation defiantly came,so dis scenario please suggest me( can i use Tlog backup through MP is it possible or any Mismatch of LSN logshiiping and MP)
please Suggest me
i have fully confusion-ed
SQL server DBA
February 14, 2012 at 11:37 am
You can take full backups of logshipped databases, full backups do not truncate the log or break the LSN chain.
You can run any other process on logshipped databases EXCEPT log backups. Only take log backups via the backup job created by logshipping else you will break the log backup chain and cause logshipping to fail.
Set up logshipping via the wizard and it will create all the jobs you require, backup, copy and restore
---------------------------------------------------------------------
February 14, 2012 at 8:27 pm
Thank You,
i know.
But little bit confused Again,
can i take Tlog backup of logshipping database through MP(Maintenance plan every 15 mins any impact on logshipping db's)?(Any Mismatch of LSN's)
is Good for Logshipping databases Or bad Practice.
please Suggest me..
SQL server DBA
February 14, 2012 at 11:40 pm
sounds good to me
will come back and leave further comments
seo tips[/url] | seo training | hairstyles[/url] | medium hairstyles[/url]
February 15, 2012 at 1:09 am
kranthi.india123 (2/14/2012)
Thank You,i know.
But little bit confused Again,
can i take Tlog backup of logshipping database through MP(Maintenance plan every 15 mins any impact on logshipping db's)?(Any Mismatch of LSN's)
is Good for Logshipping databases Or bad Practice.
please Suggest me..
i take it you are saying if you have two backup jobs for the transaction log, one being done via a maintenance plan, and the other being done by the logshipping wizard?
if you backup from each to the same location, then there shouldnt be any issues as the copy job for logshipping will copy any files which are not on the secondary node.
if you backup via logshipping to Z:\Backups\LogShip\DBName and via the MP to Z:\Backups\MP\DBName then yes this will cause you problems as the secondary will not have the full set of log backups
in my opinion dont bother with the MP as you already have log backups being done by the logshipping plans you already have in place, why duplicate the work load??????
February 15, 2012 at 2:29 am
i take it you are saying if you have two backup jobs for the transaction log, one being done via a maintenance plan, and the other being done by the logshipping wizard?
if you backup from each to the same location, then there shouldnt be any issues as the copy job for logshipping will copy any files which are not on the secondary node.
if you backup via logshipping to Z:\Backups\LogShip\DBName and via the MP to Z:\Backups\MP\DBName then yes this will cause you problems as the secondary will not have the full set of log backups
in my opinion dont bother with the MP as you already have log backups being done by the logshipping plans you already have in place, why duplicate the work load??????
Thank you..SSC eights..
yes..That defiantly Work Load.But I know ..Little Bit confused.
for example every 3 mins Tlog backups are coming Through log shipping.so i haven't check restore job are failure last one hour and after database crash,dis scenario 1hour data loss..dis situation defiantly came,so dis scenario I can Use MP for Tlog Backup for the logshipped DB's.please suggest me. and One More Important issue can i Shrink the logShipping Databases(.mdf files and .ldf)
SQL server DBA
February 15, 2012 at 2:30 am
Thank you..SSC eights..
yes..That defiantly Work Load.But I know ..Little Bit confused.
for example every 3 mins Tlog backups are coming Through log shipping.so i haven't check restore job are failure last one hour and after database crash,dis scenario 1hour data loss..dis situation defiantly came,so dis scenario I can Use MP for Tlog Backup for the logshipped DB's.please suggest me. and One More Important issue can i Shrink the logShipping Databases(.mdf files and .ldf)
SQL server DBA
February 15, 2012 at 2:43 am
kranthi.india123 (2/15/2012)
Thank you..SSC eights..yes..That defiantly Work Load.But I know ..Little Bit confused.
for example every 3 mins Tlog backups are coming Through log shipping.so i haven't check restore job are failure last one hour and after database crash,dis scenario 1hour data loss..dis situation defiantly came,so dis scenario I can Use MP for Tlog Backup for the logshipped DB's.please suggest me. and One More Important issue can i Shrink the logShipping Databases(.mdf files and .ldf)
I would never shrink any files unless there was significant disk space pressure and even then I would go and purchase more disks to increase the capacity before I even thought about shrinking as it causes more harm than good in my opinion.
Shrinking the log will reset the LSN's and you will need to reinitialize log shipping so not a good idea.
As for the first part of the question, I'm unsure what you mean.
Logshipping Tlog is happening every 3 minutes? Restore job is failing? Have you checked the history of the restore job? What are the error messages? Have you tried to fix the error messages?
I would NOT run Tlog backup via MP and Tlog backup via LogShipping for the same database, it just gets messy
February 15, 2012 at 4:14 am
Only back up the log via the logshipping jobs. There is no need for the duplication and the info in the logshipping tables will be incorrect
---------------------------------------------------------------------
February 15, 2012 at 5:35 am
Thank You So Much,
Yes..You are saying Absolutely Right.
Please Explain To me clearly(shrinking logshipping DB's),i Got your Point.
can i Shrink the Logshipping DB's??? (what type of impact on Logshipping DB's)
My .mdf file 250GB and .ldf file 500GB..what can i do dis situation????
According To your suggestion ,Shrinking the log will reset the LSN's and you will need to reinitialize log shipping so not a good idea.its Right.
and my 1st question is ..logshipping is Working and so dis situation,my restore job failures till last 1hour,i can't see the restore job running or not ,after logshipping primary Db's will be crash.so dis situation 1hour data will be loss..how can i escape dis situation??
please explain...
SQL server DBA
February 15, 2012 at 5:48 am
kranthi.india123 (2/15/2012)
Thank You So Much,Yes..You are saying Absolutely Right.
Please Explain To me clearly(shrinking logshipping DB's),i Got your Point.
can i Shrink the Logshipping DB's??? (what type of impact on Logshipping DB's)
My .mdf file 250GB and .ldf file 500GB..what can i do dis situation????
According To your suggestion ,Shrinking the log will reset the LSN's and you will need to reinitialize log shipping so not a good idea.its Right.
and my 1st question is ..logshipping is Working and so dis situation,my restore job failures till last 1hour,i can't see the restore job running or not ,after logshipping primary Db's will be crash.so dis situation 1hour data will be loss..how can i escape dis situation??
please explain...
I still dont understand your question.
Are you trying to say this..
Logshipping working OK
Then log shipping restore fails
How long will it be before primary DB crashes and how to avoid it?
February 15, 2012 at 5:52 am
A shrink does NOT break the log chain. Any idea why your log is so big?
Please clarify your other questions
---------------------------------------------------------------------
February 15, 2012 at 7:52 am
Thanks,
Example log will be corrupted or any one deleted of the Tlogs on copy folder of secondary server ,that situation Restore Job Failures.
dis situation restore job failures right till last 1hour,after logshipping primary server will be crash(for example:i mean To say morning 1AM i Won't leave That Day)so next day i can see the jobs ,restore Job failures,dis situation 1hour data will be loss..how can i escape dis situation??
Please Explain To me can i Shrink the Logshipped Databases(.mdf and .ldf files)
any impact of LSN's
SQL server DBA
February 15, 2012 at 7:56 am
Thank you.
i don't know that exactly situation,i think day to day more Transactions Will be came on that databases.
i can shrink the Logshipped DB's.so dis situation their is No LSN mismatch.right.
colud You explain To me clearly Logshipping Shrinking DB's??
SQL server DBA
February 15, 2012 at 8:16 am
If you lose a log backup in the chain for whatever reason you would need to reinitialise log shipping from a full backup.
Failover after Loss of the primary depends on the state of the primary. If you cannot reach it at all you need to restore the last log backup available to you and recover the secondary with
restore database dbname with recovery.
If the database is in a state where you can perform a tail log backup you should do that and manually restore that log backup to the secondary after all previous log backups are restored. For full details read this:
http://sqlskills.com/BLOGS/PAUL/post/Disaster-recovery-101-backing-up-the-tail-of-the-log.aspx
The fact a database is being Logshipped has no impact on how you shrink files. The same rules against shrinking also still apply.
For info on managing transaction logs see here[/url]
---------------------------------------------------------------------
Viewing 15 posts - 1 through 15 (of 42 total)
You must be logged in to reply to this topic. Login to reply