comments on my log shipping setup

  • hi,

    i am currently testing my log shipping and i would like to get some comments on my design:

    the step involved in order of execution are:

    1. restore last night's full backup to the standby server.

    2. delete old transaction log backup files (clean-up, to save some disk space)

    3. backup transaction log of production database and restore it in the standby server, runs every 5 minutes, scheduled job that runs from 6AM - 7PM.

    ann

  • And your restore process happens daily?

    Once you have the logs backing and shipping you can delay the restoration, then start up again, Or I would suggest you leave them continuously restoring, and not refresh the standby server (Unless of course shipping/restoration fails for some odd reason)

    What did you implement log shipping for? Warm Standby, or Please don't say it, as a reporting database?

  • dont worry, its a warm standby. =)

    yup, that's the very first step in my log shipping, the restoration of last night's full backup.

    i was testing it at first and i can't seem to make my log shipping continue to run the next day.  i checked the other jobs running and it turns out that the log is being truncated prior to backing up the database.  obviously, my very first restore on the standby server will be useless because the logs are all screwed up.  so what i did was to restore that backup and do log shipping the whole day.  that seems to fixed it up coz its been running for like 3 days and i havent had any problem so far.

    i want to test it first for a couple of days before i present the design to my boss.  so i'm kinda getting some feedbacks on this.

    ann

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply