For information about restoring the DHCP server
Hello.
My name is tyokoda512.
I have built a DHCP server
is 2008 R2 Windows Server.
It has a cluster configuration with
two servers MSFC.
I was carried out to restore the backup
of the DHCP server.
I've confirmed that it has been carried out
to restore display, and
"was to restore the database",
was actually not be restored.
The following log was logged when you
check the event log.
http://technet.microsoft.com/ja-jp/library/dd380148 (en-us, WS.10). aspx
Files that have been specified can not be found.
A restore is I think to be able to access the file
because it is carried out in the Administrator.
Please help me someone.
Thank you.
June 11th, 2012 6:43am
Hello Tyokoda,
Please try like this once http://technet.microsoft.com/en-us/magazine/ff621490.aspxRegards, Ravikumar P
Free Windows Admin Tool Kit Click here and download it now
June 11th, 2012 10:41am
Thank you for reply.
I'm sorry. My explanation was
the lack of information.
I was carried out how to restore this.
Despite the situation is displayed
"The database has been restored", the error
of the event ID1019 is printed,
do not be restored.
Thank you.
June 11th, 2012 7:48pm
I found a workaround.
I have a DHCP database logical drive: In the
state that created the folder in the
(D \), was to create a backup folder
there.
However, was able to successfully restore
by placing just below the D drive
the backup folder.
I was confirmed and security of the folder you created,
in particular the difference was not found.
But I get up to share with you
because it was found a workaround.
Free Windows Admin Tool Kit Click here and download it now
June 12th, 2012 8:17am
I found a workaround.
I have a DHCP database logical drive: In the
state that created the folder in the
(D \), was to create a backup folder
there.
However, was able to successfully restore
by placing just below the D drive
the backup folder.
I was confirmed and security of the folder you created,
in particular the difference was not found.
But I get up to share with you
because it was found a workaround.
June 12th, 2012 8:17am