January 12, 2015 at 1:28 pm
Our SQL Servers are on VMware. All of the SQL data is stored on the SAN. The backups are also on the SAN (but it looks like a local drive). Since hardware problems seem to be eliminated with VMware, is there any reason to move the backups to a 2nd location on the SAN?
No, we don't have a 2nd SAN or other hardware to move them to.
Yes, they eventually make it to tape.
January 12, 2015 at 2:54 pm
There are a lot of what if's here like SLA's and RPO/RTO. The simple answer is no, you don't need to store it twice on the SAN. I would say you need a backup solution separate from the SAN. Something that stores your backups on faster media for a period until it can be saved off to tape and to provide faster recovery. We use Netbackup although I am sure there are a multitude of better products out there.
January 12, 2015 at 4:08 pm
If the SAN goes, and they do, you lose all your backups. Yes, I would absolutely have a second location. Tape at least.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply