http://www.brentozar.com/archive/2009/02/mirrors-arent-backups/ Your technology pain-relief experts. Wed, 08 Feb 2012 16:37:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://www.brentozar.com/archive/2009/02/mirrors-arent-backups/comment-page-1/#comment-7170 Brent Ozar Wed, 04 Feb 2009 17:43:36 +0000 http://www.brentozar.com/?p=2422#comment-7170 That's absolutely true. In order to get that level of protection, you also have to watch the SAN, because the SAN admin doesn't even need to stop SQL Server in order to take a snapshot at the disk level. Granted, the database might be corrupt, but he can try it a few times to get a good copy and you'll never know the difference. That's absolutely true. In order to get that level of protection, you also have to watch the SAN, because the SAN admin doesn't even need to stop SQL Server in order to take a snapshot at the disk level. Granted, the database might be corrupt, but he can try it a few times to get a good copy and you'll never know the difference.

]]> http://www.brentozar.com/archive/2009/02/mirrors-arent-backups/comment-page-1/#comment-7169 DavidStein Wed, 04 Feb 2009 17:05:14 +0000 http://www.brentozar.com/?p=2422#comment-7169 Too bad the guys at JournalSpace didn't consult with you 6 months ago. Too bad the guys at JournalSpace didn't consult with you 6 months ago.

]]> http://www.brentozar.com/archive/2009/02/mirrors-arent-backups/comment-page-1/#comment-7168 K_Brian_Kelley Wed, 04 Feb 2009 17:04:16 +0000 http://www.brentozar.com/?p=2422#comment-7168 Yes, I'm going to be nitpicky, but I'm a security guy and since you're pointing out a security shortfall (integrity and availability on the C-I-A triad) II think you need to better define "database protection." You are using it in a narrow scope, as in, "protect data loss or malicious data change." None of these solutions provide database protection from a confidentiality attack using the C-I-A triad. Something as simple as "net stop mssqlserver" and then copy off the .mdf, .ldf, and .ndf files. :) Yes, I'm going to be nitpicky, but I'm a security guy and since you're pointing out a security shortfall (integrity and availability on the C-I-A triad) II think you need to better define "database protection." You are using it in a narrow scope, as in, "protect data loss or malicious data change." None of these solutions provide database protection from a confidentiality attack using the C-I-A triad. Something as simple as "net stop mssqlserver" and then copy off the .mdf, .ldf, and .ndf files.

]]>