DPM 2010 and Windows 2008 System State Backups

[Ash]

1. I am currently backing up 6 servers using DPM 2010. Windows 2003 R2 system
state backups run perfectly fine. Windows 2008 DFS servers, where there is a
second partition also works fine. However, 2008 servers (2 AD and one SVN
server) with a single partition consistently fail on System State Backups.
The volume backups on these servers function perfectly fine.

2. The AD and SVN servers have plently of free space, have the registry key
AllowSSBToAnyVolume enabled, PSDatasourceConfig.xml has filestoprotect as
"C:\WindowsImageBackup\*", local system state backups using wbadmin complete
successfully, vshadow does not produce any invalid paths that I noticed.

3. The following error is produced everytime (within 20 secs) the system
state backup is initiated for the SVN server (similar errors are produced for
the AD servers)

Backup attempted at '2/14/2010 6:05:38 PM' failed to start, error code
'2147942405'.

4. The following error is present in the DPM agent error logs on the SVN
server

2394 2980 02/10 16:30:07.527 26 agentutils.cpp(1766) |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F Failed:
Could not get the value of registry key name CopyBackupEnabled under
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Data Protection
Manager\Agent\2.0 , hr = 80070002: 0x80070002
2394 2980 02/10 16:30:17.292 22 fsutils.cpp(2888) |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F Failed:
GetFileHandleById failed to open file, frn:0x012F0000000081DE: 0x80070057
2394 2980 02/10 16:30:17.292 22 fsutils.cpp(2888) |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F Failed:
GetFileHandleById failed to open file, frn:0x012F0000000081DE: 0x80070057
2394 298C 02/10 16:31:18.572 24 cc_extcalls.cpp(517) [000000000026A6 |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F DM: TempErr: err=0x40 read=1 write=0
2394 1DE0 02/10 16:31:18.572 24 cc_extcalls.cpp(517) [0000000000271E |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F DM: TempErr: err=0x40 read=1 write=0
2394 298C 02/10 16:31:18.572 24 cc_extcalls.cpp(517) [000000000026DF |TaskID=8E42D133-13F3-41D7-8B91-21AAE53F398F DM: TempErr: err=0x40 read=1 write=0
2E74 27D0 02/10 17:00:15.002 39 aaxmlprocessingutils.cpp(49) |TaskID=5DBCFA75-563A-432D-879E-17C59B3C1E97 Failed: F: lVal : E_INVALIDARG: 0x80070057
2E74 27D0 02/10 17:00:15.018 39 vadatasourcestate.cpp(651) |TaskID=5DBCFA75-563A-432D-879E-17C59B3C1E97 GetModuleHandle
failed for Library [FileWriterHelperPlugin], Hr = [0x8007007e], will try
LoadLibrary

Any advice would be appreciated.

Thank you,

Ash

[Narendran Gunasekaran[MSFT]]

Can you try this:
This is Access denied error.
The following resolution has been suggested to fix this windowsbackup error
in this thread:
http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/e2711afd-4e82-4036-aab7-156fff279146

With the assistance of MS Support, using the procmon tool, we were able to
trace the issues down to these items:

1. Permissions on C:\System Volume
Information\WindowsImageBackup\Catalog directory, the path to it and the
GlobalCatalog & BackupGlobalCatalog files. Added the account of the role
performing the backup and SYSTEM with Full Control.

2. Permissions on wbadmin.msc. Added the account of the role performing
the backup with Full Control.

3. Permissions on the Properties key of
{4D36E972-E325-11CE-BFC1-08002BE10318}. Added the account of the role
performing the backup, SYSTEM and NETWORK SERVICES with Full Control. There
appears to be a process which is removing these permissions.

--
Narendran G [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ash" <A...@discussions.microsoft.com> wrote in message
news:03DB6960-6C9C-4A1A...@microsoft.com...

[Ash]

Narendran,

Thank you for the prompt response. I have a few questions

1. What is the "account of the role performing the backup"? From what I can
see, it is the SYSTEM account.

2. I was unable to set permissions on wbadmin.msc since only
"TrustedInstaller" has full permission.

3. I reset the Properties key permission under the CurrentControlSet. The
permissions were only set to SYSTEM:F. Is that right?

4. I tried running procman myself and I found a lot of "NAME NOT FOUND"
errors. Is that normal?

Thanks in advance,

Ash

"Narendran Gunasekaran[MSFT]" wrote:

> .
>

[Ash]

I believe I found my issue.

I had old system state replicas of DPM 2007 which needed to be deleted
before DPM 2010 could do system state backups (I got access denied errors
when I monitored wbadmin process using procmon). Once the old replicas were
deleted the system state backups with DPM 2010 succeeded.

Another user reported just removing and re-adding the BMR and SS resolved
their issue.

Ash

[Narendran Gunasekaran[MSFT]]

Hi Ash,
Can you zip the contents of <DPMInstallationFolder>\DPM\Temp folder,
Application and System event logs from the production server, and the
contents of %systetemroot%\Logs\WindowsServerBackup\* folder and send it to
ngunaOMITTHIS@microsoft[dot]com, to diagnose the issue.

--
Narendran G [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Ash" <A...@discussions.microsoft.com> wrote in message

news:EBDE9F4D-06EE-48AF...@microsoft.com...

[jammin j]

Ok, this is what I found, we had veritas backing up our server and removed it. When DPM tried to get the sys state, apparently it didn't like the veritas vss still hung in the system. I started a windows backup on our 2008 server C:\ and told the backup to only use windows based vss, in which it deletes all others. Then I reran dpm on system state for the 2008 server and walla!

---
frmsrcurl: http://msgroups.net/microsoft.public.dataprotectionmanager/DPM-2010-and-Windows-2008-System-State-Backups