4. Failover clustering Multiple servers join together to form a cluster. All of the nodes in a cluster are in a state of constant communication. If one of the nodes in a cluster becomes unavailable, another node will automatically assume its duties.
6. Database Mirroring Changes in the principal database are sent to a backup database called the mirrored database. If the principal fails, the mirrored database on a different SQL instance will be instantly available. Just protects user databases. The transaction log is monitored for changes to the principal database. changes are then copied out of the transaction log of the principal server and sent over the network to the mirror server.
7. Log Shipping An inexpensive protection against server failure.
8. Log Shipping Transaction log backups are periodically sent from the primary server’s database and applied to the database on the backup server. Log shipping can send the captured transaction logs to multiple destinations. All recovery for log shipping is manual. There is no automatic failover.
9. Designed for bidirectional replication and high availability scenarios Database changes can be made to any of the peer nodes, and each node publishes the updates to the other peer nodes. Peer-to-Peer Replication
10. Peer servers are continually available. Can be used by applications or used as distributed reporting servers. Does not offer any automatic failover Peer-to-Peer Replication
11. Enable databases to recover more quickly from unplanned downtime. As changes are made to the database, the changed pages are copied into the snapshot Restore the database by copying to it the original pages saved in the snapshot. Database Snapshots
12. Backup and restore process allows an entire database to be recovered to any given point in time. Full backup A full database backup is a complete copy of the database. Differential backup A differential backup copies only the database pages modified after the last full database backup. Transaction log backup The transaction log backup copies the changes that have occurred since the last full or differential backup. Transaction log backups may be applied after the last full or differential backup has been restored. Backup and Restore