Data Protection Manager 2010 AKA DPM v3
I ended up coming in a bit late for this one due to meeting a few people I know.
So far what I’ve picked up is that DPM v3 can grow storage volumes as required.
DPM v3 can back up laptops over ×××. This supports XP, Vista and Windows 7. It scales to 1000 clients per DPM server. Disconnected clients will continue to backup using VSS according to DPM policies. This is not DirectAccess aware now. It was a huge request but release timing prevented it. I’d guess it’ll be in SP1.
What I missed:
> Self service restore for users from Windows Explorer (Previous Versions) or Microsoft Office. Windows 7 clients get a system tray icon with a bit more information.
> Self service restore for SQL DBA’s
> The store scales much more than 2007
> We get R2 Hyper-V support CSV and alternative host recovery
Client policies can include specific folders and exclude specified file types. Users can also include specific folders (optional for the admin via policy). This is new for typical corporate backup. Products live Iron Mountain’s Connected/LiveVault had this for ages. You won’t get moaning alerts when the client is offline. You get 14 days allowance for the client being offline – then you get an alert. The client has a simple synchronise now button when they get back to the corporate network to synch their VSS backups to DPMv3.
Now they talk about DPM2DPM4DR, i.e. DPM replication to a DPM site in a DR site. This is done by setting up another DPM site and then installing an agent on the primary DPM server. You can do this in 2007. A powershell cmdlet allows failover. v3 includes a GUI click to do this. You can do production site DPM to DR DPM to tape. You can then use the DR tape to recover in the production site … or the DPM store. The process of selecting what to backup from the primary DPM to the secondary is that you pick which items it has backed up. So you can tier your data backup .. maybe not everything needs to be backed up to the secondary/DR DPM. You also can decide to use a different synchronisation schedule depending on your bandwidth. This is also a block level differential backup like the primary backup.
> Scalability per DPMv3 server: 100 servers, 1000 laptops, 2000 databases
> Increased fan-in of data sources per DPM server
> Up to 80TB per DPM server
> Automatic protection of new SQL/MOSS data sources
> Decreased inconsistent replica errors
> Reduced alert volume
> Automatic rerunning of jobs and improved self healing
Worst case scenario is that you lose 14 minutes and 59 seconds worth of data because it backups up every 15 minutes. By restoring SQL to “latest” it recovers not only the DB but replays the logs to the very last transaction that was committed in the TX log.
You can produce scheduled reports of backup status for protection groups, servers or data sources, e.g. a DBA can get reports on their databases in their mailbox every morning.
Bare metal recovery for Windows Servers is now a check box.
The 2007 – 2010 upgrade path is … You must be on 64 bit 2008 or higher OS to do an in-place upgrade.
Beta is out now. The RC is after XMas 2009. The RTM will be Spring 2010.
Non-AD machines will be supported in DPM 2010 (not in the beta. It will be in the RC). It sounds like it will be drowned in scripting. I think they should talk to the OpsMgr team. X.509 is the future. OpsMgr isn’t as clean as it could be in this regard but it’s easy enough.