Designing Disaster Recovery … on a budget
This article is still under construction.
There are several options for disaster recovery and high availability. There's host based solutions, array based solutions, and virtualization solutions. Which to pick? We're going through a pretty crazy test of products, but we have the same problem as everyone else, we have tons of different storage vendors. So do you pick host based replication solutions, probably not. Do you pick array based solutions, sure, those will work. What about adding another layer of complexity to the solution and add an in-band virtualization solution? Or implement something like EMC RecoverPoint and only worry about replication with one thing, and keep array based solutions for specific tasks? So many things to choose from.

OpsMgr 2007 – No graphs in emailed reports
Some of you may have found that there are no graphs in your emails (scheduled reports) from SCOM 2007. I posted this up on the MSMOM email distro and Kevin Holman pointed me to a KB article.
http://support.microsoft.com/kb/972821
Just add this to your ReportingServicesService.exe.config file in the \ReportServer\bin
<dependentAssembly> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore"publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" /> </dependentAssembly> <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="Microsoft.ReportingServices.ProcessingCore"publicKeyToken="89845dcd8080cc91" culture="neutral" /> <bindingRedirect oldVersion="9.0.242.0" newVersion="10.0.0.0" /> </dependentAssembly>
Place this between the tags:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> </assemblyBinding>

