DPM 2010 launch week @ MMS 2010: Part 1: Technical Introduction

April 27, 2010 at 5:34 pm in Uncategorized by mikeresseler

Hey All,

Back to normal life so I found some time to blog about the most important thing that happened on MMS 2010.  DPM 2010 has RTM-ed :-).  Yes, you read it correctly, DPM has RTM-ed on monday 20th of april on MMS.  Evaluation version is available at http://technet.microsoft.com/en-us/evalcenter/bb727240.aspx, EA and VL will be available in may and GA and MS Price list will be there on June the 1st.

For all those who love DPM, this was certainly something we were looking out for, and I certainly got spoiled over there.  No less then 5 break-out sessions, 1 instructor led lab and 4 hands-on labs were there for the DPM fan.

Here’s the overview of what you have missed when you weren’t there:

Break-out sessions

  • Technical Introduction to DPM 2010
  • Protecting Applications with DPM 2010
  • Protecting Windows Clients with DPM 2010
  • Virtualization and Data Protection, Better Together
  • Disaster Recovery and Advanced DPM 2010 Scenarios

Instructor Led Lab

  • Technical Introduction to DPM 2010 – Instructor Led Lab

Hands-on labs

  • Technical Introduction to DPM 2010
  • How to protect SQL Server with DPM 2010
  • How to protect SharePoint with DPM 2010
  • How to protect Exchange Server with DPM 2010

In this series of posts I will cover the five break-out sessions and the partner announcements.  Here is the overview:

DPM 2010 launch week @ MMS 2010: Part 1: Technical Introduction

DPM 2010 launch week @ MMS 2010: Part 2: Protection Applications

DPM 2010 launch week @ MMS 2010: Part 3: Protecting Windows Clients

DPM 2010 launch week @ MMS 2010: Part 4: Virtualization and Data Protection, better together

DPM 2010 launch week @ MMS 2010: Part 5: Disaster recovery and advanced scenarios

DPM 2010 launch week @ MMS 2010: Part 6: Partner announcements

Session 1: Technical Introduction to DPM 2010

The first session given by the backup guy himself Jason Buffington.  The technical introduction started with the reason why MS decided to built a backup solution.  Microsoft builds applications such as exchange, sql and sharepoint.  Third-party vendors are building solutions to protect these environments.  Microsoft found out that many companies waited to implement the new applications until the backup vendors are ready to protect the application.  With the years passing by and the applications evolving, the backup vendors had more and more issues in protecting the workload.  And that’s the reason why they decided to create their own solution.

Second important reason… When you are in disaster recovery mode, and you are trying to recover but something is failing, who do you turn to?  The backup vendor?  He or she will say it is an Microsoft issue.  And Microsoft?  They will say that the data isn’t written correctly on tape or on disk.  So here is a gap.  Now that Microsoft has its own backup solution it is much simpler.  Something wrong?  Microsoft support.  Their applications, their backup solution.  Fix it :-)

image

Here is an overview of what DPM is possible of protecting.  This slide has been showed already many times and you will see it on many more occassions.

The statement about DPM couldn’t stay away either.  Those who followed my DPM session @ Microsoft Belgium or watched it online through edge (link 1, link 2) will certainly remember this one:

System Center Data Protection Manager 2010 delivers unified data protection for Windows servers and clients as a best-of-breed backup & recovery solution from Microsoft, for Windows environments. DPM 2010 provides the best protection and most supportable restore scenarios from disk, tape and cloud — in a scalable, reliable, manageable and cost-effective way.

Next up was an high-level overview of the capabilities of DPM 2010

These are the platforms supported with DPM 2010

  • Windows Server® 2008 R2
  • Windows Server® 2008
  • Windows Storage Server 2008
  • Windows Server® 2003 R2
  • Windows Server® 2003 Service Pack 1
  • Windows Storage Server 2003 R2
  • Windows Unified Data Storage Server
  • Windows® 7
  • Windows Vista® Business or higher
  • Windows® XP Professional – Service Pack 2

And these are the applications supported with DPM 2010

  • Microsoft® SQL Server™ 2008
  • Microsoft® SQL Server™ 2005
  • Microsoft® SQL Server™ 2000 Service Pack 4
  • SAP® running on Microsoft SQL Server
  • Microsoft® Exchange Server 2010 – including DAG
  • Microsoft® Exchange Server 2007 – including LCR, CCR , and SCR
  • Microsoft® Exchange Server 2003 Service Pack 2
  • Microsoft® Office SharePoint® Server 2010
  • Microsoft® Office SharePoint® Server 2007
  • Microsoft® Office SharePoint® Portal Server 2003
  • Windows® SharePoint® Foundation Services 4.0
  • Windows® SharePoint® Services version 3.0
  • Windows® SharePoint® Services version 2.0
  • Microsoft® Dynamics® AX 2009
  • Windows® Essential Business Server 2008
  • Windows® Small Business Server 2008

Also given was a short overview of what it can do with your application loads

File Services:

  • Windows Server 2003 through 2008 R2
  • Self-Service End-User Restore directly from Windows Explorer or Microsoft Office (yes, support from end-user recovery starting from Office 2003 or later)

SQL:

  • SQL Server 2000 through 2008, including SAP®
  • Protect entire SQL instance – auto-protection of new DB’s (Just select an instance and every new database within that instance is discovered and protected!)
  • Ability to protect 1000’s of DB’s using a single DPM server
  • Self-Service Restore Tool for Database Administrators (Let your SQL admins recover their databases their selves.  No more backup administrator intervention!)
  • Recover 2005 databases to 2008 servers (Great feature to test the compatibility of line of business applications onto the 2008 version of SQL)

Sharepoint:

  • Office 14, MOSS 2007 and SPS 2003
  • Auto-protection of new content databases within Farm
  • Protect the Farm, Recover an Individual Document (Item-level recovery for sharepoint 2010 now without the need of a dedicated recovery farm!)

Exchange:

  • Exchange 2003 through 2010
  • Optimizations for SCC, CCR, SCR, DAG and ESE offloading

Hyper-V:

  • Host-level backup of Hyper-V on WS 2008 R2
  • Cluster Shared Volumes (CSV) support
  • Seamless protection of Live Migrating VMs (VM moved to another host?  DPM follows it to keep protecting it!)
  • Alternate Host Recovery
  • Item Level Recovery (Mount a vhd and restore only certain files out of the virtual machine!)

More information about the Client support

  • Support for XP, Vista, and W7
  • Backup over VPN and breaking news on MMS… Direct Access is supported in the RTM version!
  • Scale to 1000 clients per DPM server
  • “Unique user data” only
  • Not the whole machine, so that the OS is not repeatedly backed up
  • Integration with local Shadow Copies for Vista & W7
  • Centrally configured from DPM admin UI
  • End User enabled restore from local copies offline and online, as well as DPM copies
  • Admin enabled restore from DPM copies

One of the most heard comments on DPM 2007 was that it wasn’t enterprise ready.  The team worked hard in changing this and they succeed:

Scalability

  • 100 Servers, 1000 Laptops, up to 2000 Database per Server
  • Significantly increased fan-in of data sources per DPM server
  • Up to 80 TB per DPM server

Reliability 

  • Automatic re-running of jobs and improved self-healing
  • Automatic protection of new data sources for SQL & MOSS
  • Decreased “Inconsistent Replicas” errors
  • Reduced Alert volume

Licensing

image

 

Of course there had to be some explanation about the licensing.  One of the cool features of DPM is that it only has one agent.  Yes there are 2 versions of it, the 32 and 64 bit version, but in the end it is one agent.  You want to protect workstations? 1 agent, you want to protect exchange? Same agent.  System state? One agent.

Is it the same for the licensing?  No, there are three different licenses for the agents as you can see in the screenshot:

  • Client DPML
    • 1 workstation protected means 1 client DPML.
  • Standard DPML
    • A server where you only protect files or system state will cost you 1 standard DPML
  • Enterprise DPML
    • A server where you protect application workloads such as exchange, sql, sharepoint, Bare Metal Recovery or DPM2DPM4DR (DPM to DPM for Disaster Recovery, more on that in part 5: Disaster recovery and advanced scenarios)

Do you need to calculate this for yourself?  No, from the moment you start to protect something, DPM will calculate itself what kind of license you need.  It is even getting better, you can deploy on every server or workstation a DPM agent with your favorite deployment tool.  If it is not protected, you don’t pay anything and the agent will be sitting there, disabled, waiting to start working when YOU decide it.

Where does DPM situates?

image

The above screenshot shows the positioning of DPM.  It is a part of the System Center suite and is both used with the “big brother” versions of system center and with “little sister” SCE.  If you are still deciding on what to use as your management solution, make sure that you check out the SMSE and SMSD licenses for the suite.

That’s it for part 1, next parts will be more in depth of what has been told here.

Till then,

Cheers,

Mike