Forum Widgets
Latest Discussions
LAB: Set up DR for SQL in Azure VM by using Always on feature
Why create DR for SQL in azure VMs? Creating a disaster recovery (DR) plan for SQL Server in Azure Virtual Machines (VMs) is crucial to ensure business continuity and data protection. Azure VMs offer flexible and scalable solutions for high availability and disaster recovery, such as Always On availability groups, failover clustering, and geo-replication. These features help minimize downtime and data loss during unexpected events, ensuring that your SQL Server databases remain accessible and resilient. By leveraging Azure's built-in DR capabilities, organizations can meet their recovery time objectives (RTO) and recovery point objectives (RPO), safeguarding critical business operations. Architectural diagram Steps Create two SQL Server VM, one for on-premises and another for azure (for sake of lab I am creating both in azure vm. The experience is same for both scenario) Follow the below steps in both SQL VMs to prep for DR. Set domain for sql servers Restart VM (Very Important to make changes effective) Make sure the sql servers are joined to same domain system--> Advanced setting--> computer name-->Change domain Restart VM Create Secondary VM using SQL supported image ( I am selecting standard SQL edition option) Add roles and features In Features select Failover clustering Complete installation Enable Always on feature Repeat step for both VMs Create a primary db in SQL1 In primary create test database and add data -- Create the database CREATE DATABASE userdatabase; -- Switch to the new database USE userdatabase; -- Create the table CREATE TABLE userinfo ( email VARCHAR(255) NOT NULL, name VARCHAR(255) NOT NULL ); -- Insert dummy data into the userinfo table INSERT INTO userinfo (email, name) VALUES ('john.doe@example.com', 'John Doe'); INSERT INTO userinfo (email, name) VALUES ('jane.smith@example.com', 'Jane Smith'); INSERT INTO userinfo (email, name) VALUES ('alice.jones@example.com', 'Alice Jones'); INSERT INTO userinfo (email, name) VALUES ('bob.brown@example.com', 'Bob Brown'); SELECT * from userinfo Create cluster Create Availability group Now you can see both servers are part of same availability group test failoverRegister now for the Migrate to Innovate Summit
Join the summit on March 11, presented in partnership with Intel. Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI. Join us to: Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads. Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure. Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations. Register now > Migrate to Innovate Summit Tuesday, March 11, 2025 9:00 AM–11:30 AM Pacific Time (UTC-7)
Migrating Windows Server from 'Hybrid Azure AD Join' to 'Entra ID Join (Cloud-Only)'
Hi everyone, I need help with a scenario where I’m looking to move a server ( non DC ) from Microsoft Entra Hybrid Joined to cloud only (Entra ID) Joined only. The goal is to stop relying on the on-premises AD domain and make the server authenticate only through cloud-based accounts (Azure AD accounts). I’d appreciate any guidance, documentation or best practices on how to properly handle this migration while ensuring minimal disruption. Has anyone done this transition before? What steps and considerations should I be aware of in terms of network configuration, Cost.... etc? Thanks in advance for your help!
Invalid Storage Account
I’m trying to migrate a Resource Group across subscriptions but one VM in particular throws up this error The Move Resources request contains VMs which are associated with invalid storage accounts. Please check details for these resource ids and referenced storage account names. (Code: MoveResourcesHaveInvalidState, Target: Microsoft.Compute/virtualMachines) Storage Account 'storageaccountname' either does not exist or is in an invalid state. (Code: MoveResourcesHaveInvalidState, Target: /subscriptions/subscriptionID/resourceGroups/RGName/providers/Microsoft.Compute/virtualMachines/ The referenced storage account does not exist and I have cycled the options on the boot diagnostic storage account to no avail
Trouble Installing Microsoft Site Recovery - Process Server Service Keeps Terminating
Hey everyone, I'm in the middle of migrating our on-premise servers to the Azure cloud, and I've hit a snag that I can't seem to get past. I'm at the step where I need to install the Microsoft Site Recovery agent on our appliance, but I'm stuck on the last part—validating the server configuration. Every time I run the installer, it fails during the validation step. At the same time, I've noticed that the "Process Server" service keeps getting terminated, and I'm unable to enable it again. Has anyone encountered this issue before? Any tips on how to get past this, or what might be causing the Process Server service to keep failing? I'm really stuck here and could use some advice! Thanks in advance for any help.
Migration of Exchange environment from On Prem to Azure
As cloud first approach, we are trying to migrate our on prem mail servers to Azure(We are not planning for O365 as of now for these email domains as of now). Due to lack of PaaS options is Azure as of now, best way will be to decommission the current on prem Infra including all the internal and external email servers. But as Port25 is disabled by default, can anybody suggest any tested and secured way to construct a High Available B2B Email infrastructure in Microsoft Azure? Please note, we will still be using the current on prem Internet and Intranet Domains for this Infra and we will have the On Prem Network and domain extension to Azure Subscription.Azure VMs migration from one tenant to another
Hi Community, I have a task to move/migrate Azure VMs from subscription on one Azure tenant to subscription on another Azure tenant. Moving the subscription is not an option. I think I can treat the VMs as "Physical or other" and use Azure Migrate with an appliance. Is there any another way? Can I treat is as Hyper-V to Azure Migration? Will I need an appliance server for discovery and replication? Regards Venelin
