This page is continuation to SQL SERVER 1 PART 1
Below are the task that have been performed :
1. Creating SQL SERVER 2 (SQL2)
2. Using sysprep to clear configured settings.
3. Change the IP Address on Ethernet0 and Computer Name
4. Add a network adapter to the SQL2
5. Install .Net Framework 3.5
6. Change IP Address on Ethernet1
7. Discover and attach iSCSI virtual disk created during DC1
8. Install failover clustering feature on SQL2
9. Creating Failover Cluster using Failover Cluster Manager
9. Creating Failover Cluster using Failover Cluster Manager
1. Creating SQL SERVER 2 (SQL2)
SQL server creation using OVF file
Browse to the location of OVF file
Name for the new virtual machine: SQL2
Storage Path for the new virtual machine: D:/SQLServer2
2. Using sysprep to clear configured settings.
sysprep is used to deploy a Windows image to different PCs, you have to first generalize the image to remove computer-specific information such as installed drivers and the computer security identifier (SID). You can either use Sysprep by itself or Sysprep with an unattend answer file to generalize your image and make it ready for deployment.
System Cleanup Action : Enter System Out-of-BoxExperience(OOBE)
Check :Generalize
Shutdown Options: Reboot
3. Change the IP Address of Ethernet0 and Computer Name
On Ethernet0
IP Adrress: 192.168.10.2
Subnet Mask: 255.255.255.0
Preferred DNS Server: 192.168.10.100
Joining to the Domain sql.local
Computer name : SQL2
Member of : sql.local
Welcome message from domain sql.local
4. Add a network adapter to the SQL2 server
Connect at power on
custom: Specific virtual network
VMnet4
5. Install .Net Framework 3.5
6. Change IP Address of Ethernet1
On Ethernet1
IP Adrress: 192.168.20.2
Subnet Mask: 255.255.255.0
Append Primary and connection specific DNS suffixes
Append parent suffixes of the primary DNS suffix
Enable LMHOSTS lookup
Disable NetBIOS over TCP/IP
7. Discover, format, attach iSCSI virtual disk created during DC1Open the iSCSi initiator
Add target ip 192.168.10.100
Disk Management
Click Disk1 and bring online
The disk volume is attached and available on the server
Select Role-based or feature-based installation
Select SQL2.sql.local
Select Failover Clustering feature
9. Creating Failover Cluster using Failover Cluster Manager
Log out and sign in using domain user account
Adding both SQL1 and SQL2 to the cluster
Cluster Name: SQLFCI
Cluster SQLFCI being created
Now both SQL1 and SQL2 are in Cluster SQLFCI
No comments:
Post a Comment