my personal blog about systemcenter

Archive for November, 2013

Oracle Linux 6.4 Running with SystemCenter 2012 R2 and Hyper-V 2012 R2 Part 1/4

Categories: Data Protection Manager, Hyper-V, Linux, Operations Manager, SCOM, System Center, Windows Server 2012
Comments Off on Oracle Linux 6.4 Running with SystemCenter 2012 R2 and Hyper-V 2012 R2 Part 1/4

This will be a start of a small series with Installing , Protecting and Monitoring Oracle Linux running on Hyper-V 2012 R2 and System Center 2012 R2

First off is basic install , 2nd is protecting with Data Protection Manager and 3rd is Monitoring with Operations Manager and last creating template with Virtual Machine Manager

Oracle have released Oracle 6.4 Linux that have support for Windows 2012 R2 Hyper-V

https://blogs.oracle.com/linux/entry/oracle_linux_6_4_has

download can be from

https://edelivery.oracle.com/linux 

and the good news is

Free to download and distribute, including patches and updates

http://www.oracle.com/us/technologies/linux/product/overview/index.html

image

So as we dont have a template (yet) we need to create a new Virtual Machine from the VMM console

image

And find a name , Generation 1 is required for Linux VM’s

image

Attach the ISO and a select a disk

image

And select Oracle Linux for OS type

image

And a few minutes later the VM is ready to install

image

Start Installer

image

Select Basic Storage Device

image

And Yes to discard existing data

image

Select a host name

image

and we need a password

image

Select use all space

image

And we just need a basic server install

image

And we wait a bit to install

image

image

And 5 minutes later we have a running Linux VM

DPM Virtual Machine Recovery Hyper-V Clustering

Categories: Broken, Data Protection Manager, Disaster Recovery, DPM, Hyper-V, Virtual Machine Manager, VMM
Comments Off on DPM Virtual Machine Recovery Hyper-V Clustering

One task needed for planning for disaster recovery with DPM is the naming of the VM from a clustering point of view.

If all VM’s are created through VMM then will be prefixed with SCVMM but in this example we have created one VM from Cluster Manager and one from VMM

The scenario for this type of recovery is a “dead” cluster or VM’s that was deleted by mistake.

Being able to recovery directly would be preferred but thats not currently a option

image

This leaves us with VMMTESTB prefixed from a naming point of view with SCMMM and one without when selecting the VM’s from DPM

image

And the view from Cluster Manager

image

And after creating the protection group we are ready to test a recovery

image

And our view from VMM

image

If we need to recover the VM to the orignal source we can just select recover

image

And we can recover to the original instance

image

And to provoke a error

image

We kill the VM from both cluster and hyper-v

image

If we then tries to recover a VM to its Original Instance

image

The recovery dies as we dont have the origianal VM

image

So we need to create a empty VM

image

Point it to a dummy location ,the name needs to match the original VM name

image

And no VHD attached

image

In VMM we can not see the new VMTESTA and the VMTESTA that we delted , this scenario is if the cluster dies and needs to be rebuild but VMM isnt “gone”

image

We can then restore the VM directly

image

We then have the temp clustered VM , we need to delete that

image

And also on the Hyper-V Host , this can also be done from VMM to avoid having to open the settings to find the restore VM

image

And Configure Role

image

And select Virtual Machine

image

And Enable it for HA

image

And last clean up if the VM wasnt deleted from VMM , remove the VM that have missing state

A

Protecting Windows 2003 Workload Hyper-V DPM 2012 R2

Categories: 2003, Broken, Data Protection Manager, DPM, Hyper-V, Unsupported
Comments Off on Protecting Windows 2003 Workload Hyper-V DPM 2012 R2

So far one of the big issues with Data Protection Manager 2012 R2 is the lack of support for Windows 2003 Workloads , Yes 2003 is close to slipping out of patching and support but NOT as of writing , so people still need to protect their workloads.

If people are still on 2003 there is a reason , ISV being annoying , workloads being retired and 100 different options so its critical that we are able to protect it.

So if you plan to upgrade to 2012 R2 consider the impact of the 2003 servers , either leave the 2003 workload on a downlevel DPM server , or plan to upgrade to use Hyper-V integration

image

Trying to add a older agent result in Error 307 and is unsupported.

image

And trying to browse the 2003 agent says the same , dont work and isnt supported

image

But through the Hyper-V integration we can select our 2003 VM and add it to a protection group

image

At least we can add the server to a protection group

image

And after a few minutes we can see the 2003 server being protected through the Hyper-V integration

image

And from a recovey point of view we recover the whole VM

image

And browse down though the VHD and select single files to recover.

So we can protect 2003 servers if the workload is on Hyper-V and we dont need transaction backup SQL/Sharepoint/Exchange.

So its better than nothing but not much , hopefully Microsoft will reverse on this and add 2003 support to Data Protection Manager 2012 R2