Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase «««123

Log shipping error Expand / Collapse
Author
Message
Posted Friday, June 20, 2014 4:45 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 5:55 AM
Points: 82, Visits: 233
Yes , recovery model is Full, I have talked to my sysadmin, he doesnt have time slot so that he put backup stratgy like this.but i wanted to set log shipping . would it possible to set log shipping with same backup startgy. Please advise
Post #1584284
Posted Friday, June 20, 2014 4:49 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 5:31 AM
Points: 455, Visits: 1,677
Ok, please answer every question as fully as possible;

1) why are you log-shipping at all? What are you hoping it will achieve for you (or is this purely experimental for your own knowledge)?

2) why are you only backing up the log once a day?

3) is this a production environment?

4) are you "the DBA" or is there another DBA on-site?

Thanks
Post #1584286
Posted Friday, June 20, 2014 5:02 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 5:55 AM
Points: 82, Visits: 233
Hi, thanks for the reply,

1) I am giving you answer for your first question, log-shipping will help to decrease the disaster recovery. if production server will go down , user will sit odlw they can use secondary database.

2) I am not taking log backup. one more DBA is there he is taking , he asked , but he is finding time slot to run log backup frequently. for that one we are planning . we are just strtup comapny , so it will take some time to grow.

3) this one alredy included in 2nd question , please see the 2nd point.

4) this question , i have already given.


I have some doubt. please clarify.

1)by that time can we configure log-shipping in this environment, hence log backup is runing once in everyday.
2) shall i stop taking log backup , so that chain will not break.
Post #1584290
Posted Friday, June 20, 2014 5:04 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 5:31 AM
Points: 455, Visits: 1,677


2) I am not taking log backup. one more DBA is there he is taking , he asked , but he is finding time slot to run log backup frequently. for that one we are planning . we are just strtup comapny , so it will take some time to grow.

That's probably your problem right there, then. How often is he taking log backups (which are separate to the one you take)?
Post #1584292
Posted Friday, June 20, 2014 5:20 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 5:55 AM
Points: 82, Visits: 233
oncein a everyday
Post #1584298
Posted Friday, June 20, 2014 5:36 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 5:31 AM
Points: 455, Visits: 1,677
Ok, that is almost certainly why your log-shipping isn't working. Your first task (if you really want to set up log-shipping) is to get him to stop that completely. If you don't do that this won't work.

- Next (and this is just what I would do), go back to your log-shipping job on the Primary server, and reconfigure it from scratch. Just dump everything and start again. (It's not working anyway, so who cares, right?) This time configure all of the jobs (that's LSBackup, LSCopy and LSRestore) to run more frequently than once a day. How frequently depends on your environment and how much data is changed etc. Plucking a number out of the air, let's say every 15 minutes. Set your jobs to run every 15 minutes.

- When you've done that, run each job manually once and observe what happens. So on the primary, run LSBackup, go to Job History and check that is has completed properly.

- Then go to the secondary and run LSCopy. Wait for it to complete successfully. Go into your log-shipping folder and check that the log backup file is physically there.

- If all is good so far, run your LSRestore job manually once too. Check the Job History and see that your 1 log file has been restored successfully. Monitor the whole process for the first few hours (not continuously- just check it now and then).

All of the above will only work if you are taking no other log backups. If your DBA takes extra log backups separately this won't work. S/He won't even need to take any anyway because you are taking them every 15 minutes.

Does that make sense?
Post #1584303
Posted Friday, June 20, 2014 5:52 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 5:55 AM
Points: 82, Visits: 233
Thanks Beatrix , I will follow the same. Thanks for your valuable time and helping me in this scenario.
Post #1584307
Posted Friday, June 20, 2014 5:53 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Today @ 5:31 AM
Points: 455, Visits: 1,677
Good luck!
Post #1584308
« Prev Topic | Next Topic »

Add to briefcase «««123

Permissions Expand / Collapse