couple problems with DPM 2010

  • Follow


Hi, I have few problems:
1) on localized Windows 2008 R2, DPM 2010 RTM (eval) will restore Bare-metal 
recovery backup to a local folder that cannot be opened. The system will 
return "file/folder cannot be found error". The folder still occupies the 
space on the disk and the only option how to delete it is from the command 
line with "rd <folder> /s /q" issued on the parent folder. The only 
workaround I've found so far is to install English MUI pack and switch all 
settings to their english counterparts.
What's the solution to this?

2) Why is bare-metal recovery unsupported option (read: it's not available 
(in the list) during protection group creation/modification) when backing up 
servers that are in a workgroup? This is simply unacceptable and for us, it 
invalidates the whole idea of backing up servers in workgroups....

3) DPM won't get the complete list of computers from AD, unless the computer 
accounts are left in the default location (ie. Computers container). This is 
another unacceptable "feature". Once we join computers (servers) to the 
domain, we move them respective OUs. DPM won't find them with the auto  
discovery feature and it won't also find them even when you use a text file 
with the server list. Once we move the server to the Computers OU, DPM will 
find it....

These issue make it very hard to effectively use this product. Any 
information on how to solve these is welcome.
0
Reply Utf 5/10/2010 8:27:01 PM

1) Can you please let us know in which language you have hit this issue? We 
need DPM system locale as well as protected server system locale.
2) Unfortunately this was cut because as workgroup and un-trusted machine 
support came late in 2010 release.  But if you are just looking for 
Baremetal backup recovery scenario can you please try out the following 
work-around:http://scug.be/blogs/scdpm/archive/2009/12/09/system-center-data-protection-manager-2007-sp1-bare-metal-recovery-of-windows-server-2008.aspx. 
It might work but its not tested in our lab:
3) For the last one, I am not sure what is "OU" here, if it’s a user created 
group, then DPM don't enquire from other groups as there could be lots user 
created groups with different types objects. Can you try out if manually 
agent installation?

Thanks,
Praveen D [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

"Rambler" <Rambler@discussions.microsoft.com> wrote in message 
news:0DF73C52-3B6A-4720-A805-33CF7618EA3B@microsoft.com...
> Hi, I have few problems:
> 1) on localized Windows 2008 R2, DPM 2010 RTM (eval) will restore 
> Bare-metal
> recovery backup to a local folder that cannot be opened. The system will
> return "file/folder cannot be found error". The folder still occupies the
> space on the disk and the only option how to delete it is from the command
> line with "rd <folder> /s /q" issued on the parent folder. The only
> workaround I've found so far is to install English MUI pack and switch all
> settings to their english counterparts.
> What's the solution to this?
>
> 2) Why is bare-metal recovery unsupported option (read: it's not available
> (in the list) during protection group creation/modification) when backing 
> up
> servers that are in a workgroup? This is simply unacceptable and for us, 
> it
> invalidates the whole idea of backing up servers in workgroups....
>
> 3) DPM won't get the complete list of computers from AD, unless the 
> computer
> accounts are left in the default location (ie. Computers container). This 
> is
> another unacceptable "feature". Once we join computers (servers) to the
> domain, we move them respective OUs. DPM won't find them with the auto
> discovery feature and it won't also find them even when you use a text 
> file
> with the server list. Once we move the server to the Computers OU, DPM 
> will
> find it....
>
> These issue make it very hard to effectively use this product. Any
> information on how to solve these is welcome. 

0
Reply Praveen 5/11/2010 2:28:19 PM


Thanks for responding Praveen,
ad 1) both DPM and protected server are Czech localized (cs-CZ). If it 
helps, I can find out what was the folder name that Windows were unhappy 
about.
ad 2) Thanks, I'll try it out. Any idea when this might be added? Next 
release? Any timeframe?
ad 3) sorry, I guess I should've been more specific. As you surely know, 
when you join a computer to a domain, its computer account is (by default) 
stored in the "Computers" container. What we do after computer joins a domain 
is to move the computer account to different OU (say for example to OU named 
"RDS_hosts", so its DN is something like 
CN=<server_name>,OU=RDS_hosts,DC=contoso,DC=com). In this case, DPM won't 
discover the server in AD unless I put the computer account back to Computers 
OU

Two more problems that popped up:
4) one more problem - it happens quite often that the BMR/SystemState backup 
becomes inconsistent and when I run consistency check, it fails and this 
error is logged on the protected server: "The backup operation attempted at 
'‎2010‎-‎05‎-‎11T14:19:31.734934000Z' has failed to start, error code 
'2147942405' (General access denied error). Please review the event details 
for a solution, and then rerun the backup operation once the issue is 
resolved." That's nonsense, as the replica synch was running fine before that 
and no changes were done on that computer. The only workaround I've found is 
to remove BMR backup and re-add it again for the computer in question, then 
it synchronizes fine again....

5) When creating/modifying protection group, DPM won't find (as in expanding 
the tree of resources that can be backed up - such as volumes, shares, system 
protection) an SQL 2008 instance on the to-be protected server if that SQL 
instance is not located on the system drive. How to fix this? We have several 
servers that have SQL instance roots on different drives such as E:, F: etc.

Thanks in advance

"Praveen D [MSFT]" wrote:

> 
> 1) Can you please let us know in which language you have hit this issue? We 
> need DPM system locale as well as protected server system locale.
> 2) Unfortunately this was cut because as workgroup and un-trusted machine 
> support came late in 2010 release.  But if you are just looking for 
> Baremetal backup recovery scenario can you please try out the following 
> work-around:http://scug.be/blogs/scdpm/archive/2009/12/09/system-center-data-protection-manager-2007-sp1-bare-metal-recovery-of-windows-server-2008.aspx. 
> It might work but its not tested in our lab:
> 3) For the last one, I am not sure what is "OU" here, if it’s a user created 
> group, then DPM don't enquire from other groups as there could be lots user 
> created groups with different types objects. Can you try out if manually 
> agent installation?
> 
> Thanks,
> Praveen D [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> 
> "Rambler" <Rambler@discussions.microsoft.com> wrote in message 
> news:0DF73C52-3B6A-4720-A805-33CF7618EA3B@microsoft.com...
> > Hi, I have few problems:
> > 1) on localized Windows 2008 R2, DPM 2010 RTM (eval) will restore 
> > Bare-metal
> > recovery backup to a local folder that cannot be opened. The system will
> > return "file/folder cannot be found error". The folder still occupies the
> > space on the disk and the only option how to delete it is from the command
> > line with "rd <folder> /s /q" issued on the parent folder. The only
> > workaround I've found so far is to install English MUI pack and switch all
> > settings to their english counterparts.
> > What's the solution to this?
> >
> > 2) Why is bare-metal recovery unsupported option (read: it's not available
> > (in the list) during protection group creation/modification) when backing 
> > up
> > servers that are in a workgroup? This is simply unacceptable and for us, 
> > it
> > invalidates the whole idea of backing up servers in workgroups....
> >
> > 3) DPM won't get the complete list of computers from AD, unless the 
> > computer
> > accounts are left in the default location (ie. Computers container). This 
> > is
> > another unacceptable "feature". Once we join computers (servers) to the
> > domain, we move them respective OUs. DPM won't find them with the auto
> > discovery feature and it won't also find them even when you use a text 
> > file
> > with the server list. Once we move the server to the Computers OU, DPM 
> > will
> > find it....
> >
> > These issue make it very hard to effectively use this product. Any
> > information on how to solve these is welcome. 
> 
> .
> 
0
Reply Utf 5/11/2010 3:38:01 PM

1) To work-around can you please take a look at: 
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dataprotectionmanager&tid=8f521c41-8b81-4831-a3fd-b88051e1ac60&cat=&lang=&cr=&sloc=&p=1
4) I think you are using RC version of DPM, can you use RTM EVAL version as 
this issue is fixed in it.
5) Can you try vssadmin list writers on those machines? There should be a 
SQL Writer listed, if its not listed can you please try enabling SQL VSS 
writer service using services.msc? If SQL writer is listed we might need 
more details to diagnose the issue. Can you please open a PSS request for 
this?

-- 
Thanks,
Praveen D [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights

"Rambler" <Rambler@discussions.microsoft.com> wrote in message 
news:0D03B731-7766-432D-BD9B-989E204B9EC5@microsoft.com...
> Thanks for responding Praveen,
> ad 1) both DPM and protected server are Czech localized (cs-CZ). If it
> helps, I can find out what was the folder name that Windows were unhappy
> about.
> ad 2) Thanks, I'll try it out. Any idea when this might be added? Next
> release? Any timeframe?
> ad 3) sorry, I guess I should've been more specific. As you surely know,
> when you join a computer to a domain, its computer account is (by default)
> stored in the "Computers" container. What we do after computer joins a 
> domain
> is to move the computer account to different OU (say for example to OU 
> named
> "RDS_hosts", so its DN is something like
> CN=<server_name>,OU=RDS_hosts,DC=contoso,DC=com). In this case, DPM won't
> discover the server in AD unless I put the computer account back to 
> Computers
> OU
>
> Two more problems that popped up:
> 4) one more problem - it happens quite often that the BMR/SystemState 
> backup
> becomes inconsistent and when I run consistency check, it fails and this
> error is logged on the protected server: "The backup operation attempted 
> at
> '‎2010‎-‎05‎-‎11T14:19:31.734934000Z' has failed to start, error code
> '2147942405' (General access denied error). Please review the event 
> details
> for a solution, and then rerun the backup operation once the issue is
> resolved." That's nonsense, as the replica synch was running fine before 
> that
> and no changes were done on that computer. The only workaround I've found 
> is
> to remove BMR backup and re-add it again for the computer in question, 
> then
> it synchronizes fine again....
>
> 5) When creating/modifying protection group, DPM won't find (as in 
> expanding
> the tree of resources that can be backed up - such as volumes, shares, 
> system
> protection) an SQL 2008 instance on the to-be protected server if that SQL
> instance is not located on the system drive. How to fix this? We have 
> several
> servers that have SQL instance roots on different drives such as E:, F: 
> etc.
>
> Thanks in advance
>
> "Praveen D [MSFT]" wrote:
>
>>
>> 1) Can you please let us know in which language you have hit this issue? 
>> We
>> need DPM system locale as well as protected server system locale.
>> 2) Unfortunately this was cut because as workgroup and un-trusted machine
>> support came late in 2010 release.  But if you are just looking for
>> Baremetal backup recovery scenario can you please try out the following
>> work-around:http://scug.be/blogs/scdpm/archive/2009/12/09/system-center-data-protection-manager-2007-sp1-bare-metal-recovery-of-windows-server-2008.aspx.
>> It might work but its not tested in our lab:
>> 3) For the last one, I am not sure what is "OU" here, if it’s a user 
>> created
>> group, then DPM don't enquire from other groups as there could be lots 
>> user
>> created groups with different types objects. Can you try out if manually
>> agent installation?
>>
>> Thanks,
>> Praveen D [MSFT]
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>> "Rambler" <Rambler@discussions.microsoft.com> wrote in message
>> news:0DF73C52-3B6A-4720-A805-33CF7618EA3B@microsoft.com...
>> > Hi, I have few problems:
>> > 1) on localized Windows 2008 R2, DPM 2010 RTM (eval) will restore
>> > Bare-metal
>> > recovery backup to a local folder that cannot be opened. The system 
>> > will
>> > return "file/folder cannot be found error". The folder still occupies 
>> > the
>> > space on the disk and the only option how to delete it is from the 
>> > command
>> > line with "rd <folder> /s /q" issued on the parent folder. The only
>> > workaround I've found so far is to install English MUI pack and switch 
>> > all
>> > settings to their english counterparts.
>> > What's the solution to this?
>> >
>> > 2) Why is bare-metal recovery unsupported option (read: it's not 
>> > available
>> > (in the list) during protection group creation/modification) when 
>> > backing
>> > up
>> > servers that are in a workgroup? This is simply unacceptable and for 
>> > us,
>> > it
>> > invalidates the whole idea of backing up servers in workgroups....
>> >
>> > 3) DPM won't get the complete list of computers from AD, unless the
>> > computer
>> > accounts are left in the default location (ie. Computers container). 
>> > This
>> > is
>> > another unacceptable "feature". Once we join computers (servers) to the
>> > domain, we move them respective OUs. DPM won't find them with the auto
>> > discovery feature and it won't also find them even when you use a text
>> > file
>> > with the server list. Once we move the server to the Computers OU, DPM
>> > will
>> > find it....
>> >
>> > These issue make it very hard to effectively use this product. Any
>> > information on how to solve these is welcome.
>>
>> .
>> 
0
Reply Praveen 5/12/2010 2:35:50 PM

re 1) thanks, using 8.3 format didn't came to my mind. I'll use that 
workaround for now - is this issue something the devs are looking into? Will 
it be fixed with some hotfix?
re 4) I'm running RTM Eval AFAIK (agent version is 3.0.7696.0)
re 5) yes, SQL VSS writer is running on those machines

"Praveen D [MSFT]" wrote:

> 
> 1) To work-around can you please take a look at: 
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.dataprotectionmanager&tid=8f521c41-8b81-4831-a3fd-b88051e1ac60&cat=&lang=&cr=&sloc=&p=1
> 4) I think you are using RC version of DPM, can you use RTM EVAL version as 
> this issue is fixed in it.
> 5) Can you try vssadmin list writers on those machines? There should be a 
> SQL Writer listed, if its not listed can you please try enabling SQL VSS 
> writer service using services.msc? If SQL writer is listed we might need 
> more details to diagnose the issue. Can you please open a PSS request for 
> this?
> 
> -- 
> Thanks,
> Praveen D [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights
> 

0
Reply Utf 5/12/2010 8:29:01 PM

4 Replies
656 Views

(page loaded in 0.109 seconds)

Similiar Articles:
















7/22/2012 4:11:38 AM


Reply: