So, big weekend this weekend - moving data from the old single head Netapp to new active/active Netapp.
One of the tasks was to move the sqlserver databases, currently running as iscsi mounts to the Netapp. As these databases are largely obsolete in our environment and the fact that we find iscsi management very inflexible - we decided we would move to cifs.
We thought this would be an easy change - oh how we were wrong!
It seems that Microsoft has decided with sqlserver that you cannot use remote mounts, ie cifs, with its product!
The filesystem browser, ie choosing a backup destination, does not see the mapped drive at all.
Yet another reason why I much prefer Oracle over sqlserver! Good job most of our stuff is on oracle!
Sqlserver fail!
That is indeed the case - It -must- be on a local disk, even if that "local" is off on a lun somewhere. I have a suspicion that was done to totally avoid the performance hit that would have been part of the picture trying to run over the very chatty CIFS protocol. (It has a 64k blob limit, designed in as part of the RFC for the protocol...) It was designed WAY back in the days of Windows 3.11 and Lanman... bolted on to the side of TCP/IP as a routeable version of Netbeui...
ReplyDeleteuh, sql server has been able to use remote shares for databases for years, at least since sql server 2005, maybe before. Not that you would want to put a performance system on remote shares. You may want to investigate trace flag 1807.
ReplyDelete