thank you very much. Please refer this video czcams.com/video/anWfLcPqFpo/video.html -- Windows Server 2016 failover cluster setup with Azure shared disk I will share soon.
Hello, i am migrating a cluster from on-prem to azure as lift and shift, in on-prem, heartbeat is configured for the cluster. I am not sure if we need that in azure as well, could you please suggest if Heartbeat is needed along with load balancer in azure? or we can delete\disable that heartbeat after migration? plz suggest
There are set of steps and configuration required prior to carry out the discovery and replicate the VM to Azure, check this link for setting up the Azure Migrate. learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-failover-cluster-instance-to-sql-on-azure-vm?view=azuresql
@@cloudpatashala7553 thank you for the response, this part of migrating and setting up the load balancer i am aware about and have done that. only confusion is, in on-prem we have heartbeat network configured for the cluster, do we need to configure the same in azure? if yes, how can we do that?
Hello sir, In create cluster wizard --> Select servers option when I select server's I'm getting error of " you don't have administrative privilege on the server " even I have admin access on server what should I do any permissions I need to assign over here ?
even though you have administrative access, it's essential to perform some troubleshooting steps to resolve this issue. Here are some steps to follow: 1. Ensure Administrative Access: Double-check that you indeed have administrative privileges on the server. Ensure that you are logged in with the correct administrative account. 2. Run as Administrator: When performing administrative tasks, it's a good practice to run the application with administrative privileges. Right-click the application (e.g., the cluster creation wizard) and choose "Run as administrator." 3. Check User Account Control (UAC) Settings: User Account Control (UAC) can sometimes interfere with administrative tasks. Temporarily disable UAC on the server or adjust its settings to a lower level. 4. Server Configuration: Ensure that the server's configuration, such as firewall settings, group policies, and security settings, doesn't restrict administrative actions. Check if any security software or third-party tools are interfering with administrative tasks. 5. Active Directory Permissions: If you are managing servers in a domain environment, ensure that your user account has the necessary Active Directory permissions. It may be necessary to check group memberships and permissions. 6. Server Role and Features: Ensure that the server has the necessary roles and features installed to support cluster creation if required. For example, if you are creating a failover cluster, both servers should have the Failover Clustering feature installed. 7. Logging and Error Details: Check the event logs on the server for any detailed error messages or events related to the failed administrative task. These logs may provide additional insights into the issue. 8. Network Connectivity: Verify that there are no network connectivity issues between your management workstation and the server. Firewalls or network configurations could block necessary communication. 9. Group Policy: Review group policies that may affect administrative access on the server. Group policies can sometimes restrict certain administrative actions. 10. Third-Party Security Software: Check if any third-party security software or antivirus programs running on the server are interfering with administrative tasks. Temporarily disabling or configuring these programs may help. 11. Local Security Policy: Review the Local Security Policy settings on the server and ensure they are not overly restrictive.
Great demo, ty so much for sharing it! could you pls also include the git repo to the script, creating and attaching shared disk?
thank you very much.
Please refer this video czcams.com/video/anWfLcPqFpo/video.html -- Windows Server 2016 failover cluster setup with Azure shared disk
I will share soon.
Hello, i am migrating a cluster from on-prem to azure as lift and shift, in on-prem, heartbeat is configured for the cluster. I am not sure if we need that in azure as well, could you please suggest if Heartbeat is needed along with load balancer in azure? or we can delete\disable that heartbeat after migration? plz suggest
There are set of steps and configuration required prior to carry out the discovery and replicate the VM to Azure, check this link for setting up the Azure Migrate.
learn.microsoft.com/en-us/azure/azure-sql/migration-guides/virtual-machines/sql-server-failover-cluster-instance-to-sql-on-azure-vm?view=azuresql
@@cloudpatashala7553 thank you for the response, this part of migrating and setting up the load balancer i am aware about and have done that. only confusion is, in on-prem we have heartbeat network configured for the cluster, do we need to configure the same in azure? if yes, how can we do that?
Hello, how can I assign a public IP to the cluster in Azure? When one cluster is down, it automatically shifts to the next.
Please refer below url link, it might be helpful
learn.microsoft.com/en-us/answers/questions/914767/how-to-assign-public-ip-address-from-old-cluster-t
how we can configure sql basic availability groups with same setup.
Please refer below Microsoft documentation
learn.microsoft.com/en-us/azure/azure-sql/virtual-machines/windows/availability-group-manually-configure-tutorial-single-subnet?view=azuresql
Hello sir,
In create cluster wizard --> Select servers option when I select server's I'm getting error of " you don't have administrative privilege on the server " even I have admin access on server what should I do any permissions I need to assign over here ?
even though you have administrative access, it's essential to perform some troubleshooting steps to resolve this issue. Here are some steps to follow:
1. Ensure Administrative Access:
Double-check that you indeed have administrative privileges on the server. Ensure that you are logged in with the correct administrative account.
2. Run as Administrator:
When performing administrative tasks, it's a good practice to run the application with administrative privileges. Right-click the application (e.g., the cluster creation wizard) and choose "Run as administrator."
3. Check User Account Control (UAC) Settings:
User Account Control (UAC) can sometimes interfere with administrative tasks. Temporarily disable UAC on the server or adjust its settings to a lower level.
4. Server Configuration:
Ensure that the server's configuration, such as firewall settings, group policies, and security settings, doesn't restrict administrative actions. Check if any security software or third-party tools are interfering with administrative tasks.
5. Active Directory Permissions:
If you are managing servers in a domain environment, ensure that your user account has the necessary Active Directory permissions. It may be necessary to check group memberships and permissions.
6. Server Role and Features:
Ensure that the server has the necessary roles and features installed to support cluster creation if required. For example, if you are creating a failover cluster, both servers should have the Failover Clustering feature installed.
7. Logging and Error Details:
Check the event logs on the server for any detailed error messages or events related to the failed administrative task. These logs may provide additional insights into the issue.
8. Network Connectivity:
Verify that there are no network connectivity issues between your management workstation and the server. Firewalls or network configurations could block necessary communication.
9. Group Policy:
Review group policies that may affect administrative access on the server. Group policies can sometimes restrict certain administrative actions.
10. Third-Party Security Software:
Check if any third-party security software or antivirus programs running on the server are interfering with administrative tasks. Temporarily disabling or configuring these programs may help.
11. Local Security Policy:
Review the Local Security Policy settings on the server and ensure they are not overly restrictive.
@@cloudpatashala7553 chat gpt is great right