DHCP Superscope Keeps reverting back after Deletion

Posted by Ahmed Nabil In | 1 comments»
I passed by this experience after the deletion of a DHCP superscope where the Superscope reverts back after the DHCP server is rebooted or after the restart of the DHCP service. To properly remove a DHCP Superscope, you can perform any of the following methods:

1.      Right click on the Superscope and click delete. It’s safe and won't have any impact on the Sub-scopes under this DHCP superscope. In fact you will receive a message that confirms the deletion without impacting or deleting any child scopes as per attached below.
DHCP Superscope deletion

2.      One other way is to deactivate the sub-scopes (under your DHCP Superscope), move these scopes and then activate them. After all sub-scopes are moved, the DHCP superscope was removed/deleted automatically.
DHCP Technical Documentation:

SQL 2012 Protection with DPM 2012 RTM fails immediately after the job starts

Posted by Ahmed Nabil In , | 1 comments»
I passed by this experience when i was setting a new protection group using DPM 2012 for the latest SQL database server 2012. As per Microsoft System Center 2012 - Data Protection Manager Release Notes http://technet.microsoft.com/en-us/library/hh848297.aspx DPM 2012 should backup and recover SQL 2012 Databases except if the AlwaysOn feature is enabled. The AlwaysOn feature is not supported under the current DPM 2012 RTM but expected to be fully supported with the release of the System Center 2012 SP1 (expected in the next few weeks).

DPM 2012 RTM release notes

Although my SQL 2012 DB AlwaysOn feature wasn't enabled the DPM job always fails immediately after it starts, Consistency check also didn't work as well. After some investigation and several trials it turns out that the NT AUTHORITY\SYSTEM account on the SQL server needs to have Sysadmin role/right

SQL NT Authority account

Briefly, To backup and recover SQL 2012 workload under DPM 2012 RTM

  1. Make sure the AlwaysOn feature is not enabled (Currently DPM 2012 RTM doesn't support it)
  2. Grant the SQL NT AUTHORITY\SYSTEM account SysAdmin Right.
  3. Remove the Protection group and add it again after applying the above changes.