April 26, 2010 at 1:23 pm
I would like to setup a standby database from the primary database for reporting purpose. Iam thinking of doing Log Shipping but the tricky part is that after the end of each month for atleast two week standby database should not updated with the current data from primary database. it should start updating standby database after two week on every month.
Will the LOG Shipping be ok in this situation.?
April 26, 2010 at 3:52 pm
you could do this with log shipping but you would have to have the space on the reporting server to store two weeks worth of log backups. Hard to say how long it would take to restore that many log backups when you started it up again.
Else you could automate the process of reinitialising logshipping which would be
all log shipping jobs disabled,
full backup and restore with norecovery
move logs on primary out of share ( to be deleted once not required)
delete logs on secondary from share
reenable log shipping jobs.
If the database is small enough full restores might be easier.
---------------------------------------------------------------------
April 26, 2010 at 3:56 pm
If you have enterprise edition also take a look at snapshots with database mirroring.
---------------------------------------------------------------------
April 27, 2010 at 4:03 pm
Thanks guys,
I setup a Log shipping for testing purpose and getting following message in the alert job but no error in backup and restore job. How to fix it.
The log shipping primary database SCDC508DB.SVNATEST_MSCRM has backup threshold of 60 minutes and has not performed a backup log operation for 120 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14420). The step failed.
Executed as user: SUTTER-CHS\_SC_DSQL. The log shipping secondary database SCDC508DB.SVNATEST_MSCRM_LOGSHIP has restore threshold of 45 minutes and is out of sync. No restore was performed for 60 minutes. Restored latency is 30 minutes. Check agent log and logshipping monitor information. [SQLSTATE 42000] (Error 14421). The step failed.
April 27, 2010 at 4:58 pm
What is the schedule for log backup job, copy job & restore job?
how many mins or hrs you set for the option "alert if no backups occur within"? Ideally you should select 3 times the backup schedule. i.e if the backup occurs every 30 mins, then you select "alert if no backups occur within" as 90 mins
April 28, 2010 at 3:08 am
as alluded to above those values are all configurable in the gui. Just go back and edit the logshipping properties and relate thresholds to your job frequencies.
If you don't restore for two weeks you will need a restore threshold > 2 weeks.
---------------------------------------------------------------------
April 28, 2010 at 3:31 am
for this if your primary objective is restore should happen only after 2 weeks, for this you can directly create backup copy and restore manually and schedule it accordingly without using te logshipping actually but using the concept, i dont think in that way you will any error like this
April 28, 2010 at 8:06 am
Alert is setup for every 15 minutes
Backup is setup for every 1 hr
Copy is setup for every 1 hr
Restore is setup for every 1 hr.
I don't see any error in the backup, copy and restore job only alerts are throwing an error.
In this case should I setup alert every 3 hours. ?
April 28, 2010 at 8:18 am
Just confirming, may be I will try that option.
Actually, I wanted to stop the log shipping every month on 1st day for two weeks and then start log shipping again.
Is it possible that if I only stop Restore job for two weeks and let Backup and Copy job continue to run and then when I restart the Restore job, It should restore from the backup where it was stopped.
What will happend when I restart the restore job after two weeks, Will it restore from the time it was stopped. ?
May 2, 2010 at 10:29 pm
Hi Balbir,
by just disabling the restore job for some time this issue will not get solved, but i doubt it might land up u in much more trouble as both the DB's will never come into sink, for you can do one thing
1) if you more interested in logshipping than you can configure logshipping and disable all the jobs when you dont require the restore and when you want the restore to happen , just refresh the database with the latest full backup and and enable all the job's this could help you a lot.
this could even be automated.
2) manually create all the jobs for all the three (backup,copy& restore) and scedule them as needed!
check these i feel both of them could fetch you the purpose.
May 3, 2010 at 8:12 am
Ananth... Thanks for the reply.
Actually, I stopped the Restore process on Friday and let Backup and Copy process continue to run. On monday I restarted the restore process and it resotre successfully, I see some tables moved from source to destination.
Looks like that this is working..
June 23, 2010 at 8:04 am
balbirsinghsodhi,
When you stopped the Restore process on Friday and let Backup and Copy process continue did you remove any files from the Secondary Server?
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply