[RootRXXT]

Pre-Requisites for start your DR setup to Azure.

Create a new RG –
Inside the RG make sure that you have a Storage account and a VNET created in the same region.
Prepare Azure

In the Portal, click on All services and go to Recovery Services vaults

In the options blade select Getting Started, then select Site Recovery then select Prepare Infrastructure.

Run the deployment planner


Next select the option “no” to SCVMM

Create a new Hyper-V site, then add the Hyper-V host


To add the Hyper-V Host, click Add Hyper-V Server, install option 3 on the Hyper-V host. Once the installer is complete click register. You will be promted for a registration key, download option 4 and import the file on the page where it asks for the registration.


The Storage account and Vnet will auto populate if you created them before starting the process.


Lastly create a recovery policy.


Once done give it about 5min to create and complete the process.

In the Options blade now click on replicated items, then click add Hyper-V machines to Azure.


Select your Location and setup your target environment.


Finish the prompts and wait for the replication to finish (depends on VM size).


Now click on the VM and your full overview will be available.


Next let’s run a test failover –

Create another Vnet for testing purposes as you probably don’t want to cause issues in the Production environment.

Now go back to your Protected VM, and click test failover.

Now select your testvnet and RTO, when done click ok

Now click on the notification

And monitor the process


After the test failover finishes the VM appears in the Azure portal under Virtual Machines.

You should now be able to connect to the replicated VM in Azure.

To delete Azure VMs created during the test failover, click Clean up test failover on the VM.


This takes a while

For a full failover to Azure –

click the VM and Failover.

select the Latest recovery point.

Select Shut down machine before beginning failover.

After you verify the failover click Commit. It deletes all the available recovery points.

Fail back to the original location

To fail back Hyper-V VMs in Azure to the original on-premises VM, run a planned failover from Azure to the on-premises site as follows:

pick the source and target locations.

In Data Synchronization, select an option:

Synchronize data before failover (synchronize delta changes only)—This option minimizes downtime for VMs as it synchronizes without shutting them down.

Phase 1: Takes a snapshot of Azure VM and copies it to the on-premises Hyper-V host. The machine continues running in Azure.

Phase 2: Shuts down the Azure VM so that no new changes occur there. The final set of delta changes is transferred to the on-premises server and the on-premises VM is started.

Synchronize data during failover only (full download)—This option is faster because we presume that most of the disk has changed, and don’t want to spend time calculating checksums. This option doesn’t perform any checksum calculations.

It performs a download of the disk.

Initiate the failover.

If you selected the option to synchronize the data before the failover, after the initial data synchronization is complete and you’re ready to shut down the virtual machines in Azure then click Jobs, the job name and Complete Failover.

You can now sign into the on-premises VM machine to check that it’s available as expected.

The virtual machine is in a commit pending state. Click Commit to commit the failover.

To complete the failback, click Reverse Replicate to start replicating the on-premises VM to Azure again.

Will be posting some more Azure stuff, since it's one of the few thing im good at ahhaha.

[Klonopin]

Nice little tutorial, keep up with the HQ

[RootRXXT]

Nice little tutorial, keep up with the HQ

I gave up on my little User creation script, will pick it up once im done with infrastructure setup, will contact you when I get to that part again.