October 21, 2008 at 6:06 am
I'm sure you can move the backups, but I don't think you move the logs. I see Quorum there. That usually means a cluster. Which further means that all the functional files for the databases need to be kept on a shared resource, the SAN, so that when the system fails over from one server to another, the drives are still available.
Since it is a cluster, I'd suggest backing up to a network resource, not a local drive.
"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
October 21, 2008 at 11:34 pm
Thanks for the reply Grant. I got the point now.
But with the present configuration will it affect the performance?
October 22, 2008 at 5:38 am
Now that's a really hard answer. A SAN should, in theory, perform almost as well as a RAID system, but with a lot more redundancy, safety, blah, blah, blah. BUT, it has to have a good configuration. Unless you're also the SAN administrator, you're dependent on that guy to set up the discs appropriately. A SAN disk can be stripped across tons of physical disks, making for decent performance, or it can all be crammed onto a single disk or worse, share a single physical disk with other SAN disks. I've just made it a point of communicating carefully with our SAN admins so that they understand our needs. They're good guys and are more than willing to help out once they understand.
"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 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply