Posted by: scdpm2010 | May 9, 2011

System Center User Group Bijeenkomst 7 juni!

In samenwerking met Hewlett-Packard (HP), die een ruimte beschikbaar stelt, organiseert de System Center User Group NL weer een bijeenkomst op dinsdag 7 juni 2011. De SCUG start om 12.00 uur met een lunch en presenteert daarna 3 sessies over de System Center 2012 producten. Het thema van de bijeenkomst is “Best of MMS” — een beknopte samenvatting van alle nieuwe zaken de in Las Vegas tijdens de Microsoft Management Summit zijn gepresenteerd.

De agenda ziet er als volgt uit:

 12.00 – 12.45: Lunch

12.45 – 13.00: Welkom

13.00 – 14.15: Virtual Machine Manager 2012 (Mark Blok)

14.15 – 15.30: System Center Operations Manager 2012 (Oskar Landman)

 15.30 – 15.45: Break 15.45 – 17.00: System Center Configuration Manager 2012 (Tom Klaver)

 17.00: Borrel

Wil je de SCUG bijwonen? Aanmelden kan via: info@scug.nl (o.v.v. naam en bedrijfsnaam). SCUG | Dinsdag 7 juni 2011 | Aanvang: 12.00 | HP, Startbaan 16 te Amstelveen

Advertisements
Posted by: scdpm2010 | April 20, 2011

Switching vss providers

I found this on technet cool info just what i need at the moment!

By Default, DPM 2010 will attempt to use a VSS Hardware provider to take snapshots of hyper-V guests located on a SAN. There may be circumstances when you might want DPM to use the in-box VSS Software provider instead of the installed VSS Hardware provider for your SAN when doing Hyper-V backups. This may be because hardware licensing has not yet been activated, or perhaps problems with the SAN (space considerations) etc. and prevents hyper-V backups from getting done.

To overcome that add the following Key on the Hyper-V host(s) you don’t want DPM to use the hadware vss provider.

[Software\Microsoft\Microsoft Data Protection Manager\Agent\UseSystemSoftwareProvider]

This should force VSS to use In-Box VSS Software provider. If at a later time, you want to revert back to using hardware VSS provider, delete the UseSystemSoftwareProvider value.

Posted by: scdpm2010 | March 18, 2011

Info on Storing SSB

A collegue of mine ran into an issue where he couldn’t create ssb(System State Backup) on a disk,  below an explanation and solution

 DPM uses inbox Windows Server Backup(WSB) to protect System State and WSB uses local disk to write the backup.
DPM then writes the backup from the disk to the tape. DPM by default selects the disk that has the maximum free
space available. In this case it looks like the disk selected is a critical volume. DPM sets a registry key “AllowSSBToAnyVolume”
under “SYSTEM\\CurrentControlSet\\Services\\wbengine\\SystemStateBackup” to allow System State Backup to happen even on
a critical volume.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup]

“AllowSSBToAnyVolume”=dword:00000001

Posted by: scdpm2010 | March 11, 2011

Are you in to DPM?

and attending MMS 2011? then BB18  is a must see!

not into DPM? then you will be after this session which offers us a first look at the new DPM version

C U There!

Posted by: scdpm2010 | March 11, 2011

Enabling non admin client recovery

and again a good post from belgium

Mike found a couple of errors in the documentation, below are the corect settings for more info use the link above.

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\ClientProtection 

create a new key called “ClientOwners” as REG_MULTI_SZ  (watch the S in clientowners)

add usernames in the followig syntax: DOMAIN\Username, DOMAIN\Username2  (comma separated)

Posted by: scdpm2010 | March 4, 2011

Hotfix Rollup 2 available

And again a lot of good stuff as you can see below

http://support.microsoft.com/kb/2465832
This hotfix rollup resolves the following issues:

  • When you change the ports that are used by the Data Protection Manager 2010 Remote Access service, recovery jobs may fail.
  • On some client computers, the System volume runs out of space when local shadow copies are created and when the shadow copy storage is set to UNBOUNDED.
  • When you try to use one Data Protection Manager 2010 server to protect more than 1,000 client computers, you receive a warning that states that you cannot protect more than 1,000 client computers by using Data Protection Manager 2010. You receive this message even though Data Protection Manager 2010 can protect up to 3,000 client computers.
  • When you try to use one Data Protection Manager 2010 server to protect more than 1,000 client datasources, you receive a warning that you cannot protect more than 1,000 datasources by using Data Protection Manager 2010. You receive this message even though Data Protection Manager 2010 can protect up to 3,000 client datasources.
  • Data Protection Manager 2010 does not support the IBM System Storage TS2900 Tape Autoloader backup, recovery, or detailed inventory operations. The tape is left behind in the drive after any of these operations.
  • When you use Data Protection Manager 2010 Replication Agent to protect a 1.2 terabyte SQL server that has lots of .ndf secondary data files, Data Protection Manager 2010 Replication Agent crashes.
  • If you are not the administrator on a client computer, you cannot perform an end-user recovery of protected data on the client computer.
  • When there are many client computers that trigger client back up or client recovery operations, corresponding jobs are not triggered on the Data Protection Manager 2010 server. When the Data Protection Manager 2010 server enters this state, any later client backup or client recovery operations are not triggered on the Data Protection Manager 2010 server.
  • Data Protection Manager 2010 experiences slower performance if you try to protect more than 300 client datasources on a secondary Data Protection Manager 2010 server.
  • Data Protection Manager 2010 does not keep a recovery point for a client datasouce that was not synchronized during the retention period.
  • If there are many list items within of a SharePoint List in a SharePoint Content Database, the generation of a SharePoint Item level catalog will fail continuously for the SharePoint Content Database.
Posted by: scdpm2010 | March 1, 2011

Hyper-V recommended hotfixes

Yet again usefull info from the the forum.

RECOMMENDED Updates for Windows 2008 R2
========================================

 

Note: The hotfixes below contain the latest version of the file
specified.

 
VOLSNAP.SYS
===========
2460912 “0x0000007E” Stop error when you
create snapshots of a volume in Windows Server 2008 R2 or in Windows 7
http://support.microsoft.com/default.aspx?scid=kb;en-US;2460912

 
Clussvc.exe
===========
The Cluster service stops unexpectedly on a
Windows Server 2008 R2 failover cluster node when you perform multiple backup
operations in parallel on a cluster shared volume
http://support.microsoft.com/kb/2494162

 
CSVFILTER.SYS
=============
2494016 Stop error 0x0000007a occurs on
a virtual machine that is running on a Windows Server 2008 R2-based failover
cluster with a cluster shared volume, and the state of the CSV is switched to
redirected access
http://support.microsoft.com/default.aspx?scid=kb;en-US;2494016

 
MPIO.SYS
========
2277904 You cannot access an MPIO-controlled
storage device in Windows Server 2008 R2 after you send the
“IOCTL_MPIO_PASS_THROUGH_PATH_DIRECT” control code that has  an invalid MPIO
path ID
http://support.microsoft.com/default.aspx?scid=kb;en-US;2277904

 

 

Posted by: scdpm2010 | January 19, 2011

BIG DPM db?

do you have  a Huge DPMDB and the tbl_RM_Recoverysource. table is taking up all the space?

try the solution below taken from the DPM forum

UPDATE tbl_RM_RecoverySource
SET BackupMetadataXml=NULL
WHERE
IsValid=0
GO

DBCC SHRINKDATABASE (‘DPMDB’)
GO


Posted by: scdpm2010 | January 13, 2011

DPM 2010 datasheet and whitepaper

thnx to Ahmed Attia

Exchange Server

· Whitepaper : How to protect Exchange with DPM 2010

· DPM 2010 datasheet for Exchange

· System Center Data Protection Manager 2010 and Microsoft Exchange

SQL Server

· Whitepaper : How to protect SQL Server with DPM 2010

· DPM 2010 datasheet for SQL Server

Sharepoint

· Whitepaper : How to protect SharePoint with DPM 2010

· DPM 2010 datasheet for SharePoint

· Backup and Restore for SharePoint 2010: Protecting Mission Critical SharePoint Data with New Tools and Technologies

Windows server 2008 Hyper-V

· Datasheet : How to protect Hyper-V with DPM 2010

Windows 7

· Datasheet : How to protect Windows Clients with DPM 2010

Posted by: scdpm2010 | January 6, 2011

What is “initial Store”

ever wondered what the intial store thingie is when selecting a hyper-v box?
I found a great post in the DPM newsgroup explaining it

 

The initial store contains the security permissions for Hyper-V’s
Authorization Manager (azman). This is an xml file located in
%systemdrive%\ProgramData\Microsoft\Windows\Hyper-V\. You would only need to
perform a restore if this xml file becomes corrupt or is deleted somehow.

Backing up virtual machines and the initial store are independent of each
other. You only need to back up the initial store if you are using the
Authorization Manager in Hyper-V and don’t want to lose your settings.

For more information on Hyper-V Authorization Manager visit: http://technet.microsoft.com/en-us/library/dd283076(WS.10).aspx

Older Posts »

Categories