We are currently running a Windows 2003 SP1 Enterprise w SQL 2000 SP4 clustered solution.
My issue is that currently we have almost every drive letter used and the DB admins are talking about db partitioning and using mount points to get us beyond the limitation of drive letters.
I haven't been successful at finding anything about these mount points, how they work, how timefinder/srdf/tsim works with them, etc and am hoping someone can shed some light and point me in the right direction...I'd also be interested to hear your opinions/experiences to both methods.
Adding mount points in Windows Server With the disk available to the Windows Server operating system, right-click and select New Simple Volume. Specify the size as you would normally add a drive. Select Do Not Assign A Drive Letter Or Drive Path
Perform the drive format and assign a label as normal. Once the New Simple Volume Wizard is completed, the drive will be inventoried in the list of disks. MountPoint3 has been added and now select Change Drive Letter And Paths
When the Change Drive Letter And Paths option appears, point the drive to a path on the local filesystem. example, point to C:\MountPoints\MountPoint3. With this configuration, the path will use a different controller than the C:\ drive for the I/O operations across all drives. redirect the drive to the MountPoint path.
Once your configuration is complete, all of the mount points will appear in the subfolder you created. The ¿folder¿ icon for the mount points is a shortcut to a drive; the ¿folders¿ are redirecting the drive to the path on the parent drive.
Consolidating the drives, especially in shared storage configurations, can greatly simplify searching and organization for large systems on a Windows server. This functionality is not new to Windows, but it looks a little different now in Windows Server 2008.
Thanks for the very thorough reply! It helps a lot.
I would also like to know how timefinder/srdf works with this.. is each mount point a separate device and thus create an associated bcv for each? device groups everything else the same?
Darrell, I use mount points heavily in our Microsoft SQL clusters due to drive letter limitations. Those clusters are also production sources for TimeFinder clone and bcv operations. From a TimeFinder perspective it is still a device mounted to a production host. It does not matter if the host mounts the LUN as a drive letter or a mount point. The mount point is only a host specific reference and will not affect replication operations.
Darrell, were the reply's to your post able to answer your questions? If so, please mark the helpful and correct posts and also mark the thread as answered. Doing so helps others identify what posts were the most useful.
Sorry, it has been awhile since I have opened this thread. I am currently revisiting this issue. I think I understand about the timefinder replication. How about mounting and unmounting the mountpoints using symntctl? We use this as part of our procedures. Does this work with mountpoints as well?
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1127
0
Posted October 20th, 2009 08:00
symntctl mount -sid 123 -symdev 0BAD -path G:\exchange2007\stg\db1
symntctl unmount -path G:\exchange2007\stg\db1