March 13, 2010 at 7:16 am
I have a SQL 2005 cluster running in vms on VMware ESX 3i.
When I attempt to add a "New Backup Device" and browse to a drive that is not the default "Backup" location (R:\Microsoft SQL Server\MSSQL.1\MSSQL\Backup in this case), I am unable to see any drives except "R:" in the "Locate Database Files" window. I'm trying to backup to a drive which is a cluster resource that is online and which shows up under My Computer on the node it is currently owned by and can be browsed to, etc. There are other disks configured as cluster resources but the only disk visible in "Locate Database Files" is the drive specified as the SQL Data drive during installation.
I am able to successfully backup to the R: drive. but I want to use the T: drive as my Backup device/location.
The ACL looks the same on the T: drive as it is on the R: drive so I don't see a security problem
If I manually enter the path to the T: drive in the File box in the new backup device dialog then a backup device is set up under Server Objects -> Backup Devices in Mgmt Studio and I can select that backup device as the destination backup device but the backup fails.
Shouldn't the other local drives be visible in the "Locate Database Files" window?
Regards,
Shivrudra W
March 13, 2010 at 9:34 am
When dealing with a cluster, only shared drives that are dependencies of the SQL Server service are accessible from SQL Server
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 13, 2010 at 10:24 am
You can place the backups file anywhere but to refer by drive letter, the drive must within the SQL Server resource group. You can reference using UNCs in the format of \\servername\sharename\(directory) where directory is optional.
Note that you must use Cluster Administrator to define the share and the security. The share needs to belong to a resource group that has a Network Name, an IP and a dependency to the physical disks.
SQL = Scarcely Qualifies as a Language
March 13, 2010 at 6:49 pm
Yes, as others said drive should be in SQL server service resource group, check with windows team they can fix this for you.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply