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!
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.
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 VenelinDigital event: The Future of VMware Is in Azure – July 16th, 2024
Take a deep dive into options for migrating and optimizing your workloads in a rapidly evolving VMware landscape. Join this free digital event and learn how Azure VMware Solution can support your VMware workloads while minimizing migration disruption. Register for this event with technical sessions for VMware administrators such as: Security—with topics on securing the management plane, role-based access control, patch management, and integration with Microsoft Defender for Cloud and Azure VMware Solution. Networking—with topics on hub-and-spoke vs. mesh network design, securing network traffic, traffic and networking monitoring, and hybrid deployments. Disaster recovery and resiliency—with topics on replication and cold site setup, business continuity, and easier vSphere migration with Azure VMware Solution. VMware integration with Azure services—with topics on data warehousing and data lakes, AI and machine learning analytics, DevOps solutions, and automation and lifecycle management. Join us for talks from industry leaders, technical sessions, and live Q&A. Register now > The Future of VMware Is in Azure Tuesday, July 16, 2024 9:00 AM–10:30 AM Pacific Time (UTC-7)
Azure Migration without VM Shutdown
We're in the process of shutting down the on-premises setup of our company environment running on VMware. We have a DC, SQL server, accounting server and a couple terminal servers used for remote access. I have created the necessary Azure migration assessment and ready to start the replication of the 1st batch of servers. Because we have a legacy custom SQL app, we must maintain standard Windows AD, so I'll be moving our DC virtual machine. Azure AD will not work thus the need to migrate our on-prem DC. My question is replicating and copying our on-prem domain controller from VMware up to Azure but keeping it running following the replication migration up to Azure. I know the normal process of replication is to shutdown the running on-prem VMs once the final delta replication has completed. However, I need to keep my on-prem AD environment running for about another month as I build the Azure environment in parallel. I understand that the two environments will not be in-sync if new domain users are created but this likely will not need to occur with the small size of the company. Basically, does the Azure migration process allow us to keep the migrated VMs running following the final replication sync? I'll do this replication during non-production hours so network activity will be zero. Thanks for any suggestions or input. Kennvme disk devices and mobility agent
Hi everyone, I'm doing some tests regarding the migration of Linux ec2 instances from AWS to Azure, I have followed the docs for the modernized experience described here but the installation on the ec2 vms fails because the instalelr cannot find a scsi disk the error is for example : "AddDiskDiscoveryInfo failed: Error: no attribute found for key scsi_bus" My undestanding is that the installer expect to find some scsi reference under the linux userspace and since it cannot find it exit with errors. The vm I'm trying to migrate is based on suse linux 12, the disks of that vm are mapped like this : lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 10G 0 disk ├─nvme0n1p1 259:1 0 2M 0 part ├─nvme0n1p2 259:2 0 20M 0 part /boot/efi └─nvme0n1p3 259:3 0 10G 0 part / nvme1n1 259:4 0 1G 0 disk and lsscsi does not return any output, so for modern linux kernels nvme devices and scsi devices are different things, I think that the mobility agent should consider this and have an alternate way to identify disks/partitions when nvme is found.
