vxsnap create for SQL
Hi, I try to get a VSS snapshots for SQL, but I have a problem. This is my environment: I have distributed 10 database on 2 volumes and the logs in another one. E:\Database, with 5 database, size 100GB F:\Database, with 5 database, size 100GB J:\Logs_all_Database, with 10 logs for each database, size 50GB I have 3 volumes for the snapshots with the same size. If I take a snapshot for one database only this database quiesce, and get the snapshot with only one consistent database. My point is, can i get a snapshot for all the volume with only the name of the SQL instance, and get the quiesce of all databases on that volume? or I need to separate databases in individual volumes?Solved1.1KViews0likes3CommentsVeritas Storage Foundation for Windows 5.1 Volume Manager Disk Group fails to come online
We are trying to implement a 2 Node SQL server cluster on Windows 2008 R2 for last few days. We have so far successfully completed Windows cluster part and have tested quorum failover and single basic disk failover. Our challenge is that for shared storage between two nodes where we have got 30 LUNs from SAN but we need to have single drive. Since merging LUNs at SAN level is not an option for us and MSCS does not understand dynamic disk group created using winodws disk manager we have to use Veritas Storage Foundation for windows 5.1. We have successfully installed SFW 5.1 and created Cluster Dynamic Disk group and Volume on this disk group. This volume is visible in Windows Explorer without any issue. To add this disk group in cluster we followed below steps 1. In "Failover Cluster Manager" we created "Empty Service or Application" 2. Added "Volume Manager Disk Group" resource in the application. 3. After right clicking on the resource and selecting "Bring this resource online option" the disk group was brought online. To test the failover we rebooted the first node. The disk group failed over to the second node without any issue. To bring back disk group on node one again we restarted the second node, however this time on the first node the disk group could not come online with status was shown as "Failed". Since then we have tried rebooting both nodes alternatively, refreshed , rescaned disks but everything has failed to bring back the resource online. We have again followed all the steps from the start but same result. Can anybody suggest forward path?2.2KViews0likes4Comments