Blog

Log shipping is a tried and true method in SQL Server for keeping a copy of your data on a secondary server. You have your primary and secondary server set up, and it’s working great. Are you monitoring it? Do you know what to do if you need to fail over to the secondary? Join Jes in this free 30 minute video to find out!

In case you missed it: Log Shipping Part 1: Preparing for Disaster!

Backups: More Important Than You Think

Grab my Backup & Recovery Step By Step training for more information on why backups and restores are so important, and how to perform them!

↑ Back to top
  1. Great webcast Jes.

  2. Awesome vid Jes…do you have this available in PDF? I just want to have the recovery steps available instead of having to keep following the video :)

  3. One of my friends told that we should not use BACKUP LOG [DBNAME] TO DEVICENAME WITH NORECOVERY during planned failover but instead we should use BACKUP LOG [DBNAME] TO DEVICENAME WITH NO_TRUNCATE,NORECOVERY.

    Also can you please provide me the T-SQL command to backup the log incase of unplanned failover (i.e. my storage on which the db resides failed but my instance is still up and running)

  4. Also can we use BACKUP LOG [DBNAME] TO DEVICENAME WITH NO_TRUNCATE instead of BACKUP LOG [DBNAME] TO DEVICENAME WITH NORECOVERY during planned failover

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

css.php