Unsolved
This post is more than 5 years old
6 Posts
0
6476
WINDOWS 2008 system state recovery through Networker 7.6
Hi,
I am working in large scale company and we are using Networker 7.6 and backhand as data domain. recently, one of our windows 2008 r2 server was failed and it's been rebulit again. Now, we have performed sytem state on this 2008 r2 machine through Networker 7.6 but we haven't got any success regarding it.
I have followed up EMC 7.6 DISASTER RECOVERY GUIDE to restore system state on windows 2008 r2 machine. I can not figure out what could possiblely go wrong while I have followed up these EMC guide.
Any comments/ answers regarding this issue will be appreciated.
Regards,
Pritesh
Stephanie_P
180 Posts
0
June 10th, 2011 06:00
Hi Pritesh,
The team is going to move this thread over to the Support Forums Community where it can be addressed.
Thanks,
Stephanie
RFritz11
244 Posts
0
June 10th, 2011 07:00
Hi Pritesh, We've moved your question to the Networker Support Forum where it should receive prompt attention. Thanks.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 14th, 2011 02:00
Hi Pritesh,
What is the error you get? The steps are:
- reinstall same OS and make sure network names are the same as before (do not join domain)
- make sure you have same patch level as before
- install NW
- run restore of whole machine (I suggest do it from CLI in case of many many many files)
- you will need to reboot afterwards
For real DR option (bare metal recovery), you would need to run 7.6SP2 on client which now enables you do that.
pritsehsolanki
6 Posts
0
June 14th, 2011 16:00
Hi,
I have followed up all the procedure mention in EMC 7.6 Networker Disaster recovery plan. The server I want to recover is rebuilt again, my question is, can i do system state recovery on rebuilt 2008 R2 server?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 15th, 2011 02:00
I believe this is not supported by MS or something - there was pretty big disscussion about that. I know it works on win2k8 (not R2)... actually I did test that on win2k8 AD server and it worked just fine. Nevertheless, if you want more help please show us steps you did (not what is written) and what error did you get.
pritsehsolanki
6 Posts
0
June 15th, 2011 17:00
I have follow up below steps as per 7.6 disaster recovey guide.
Task 1: Satisfy Windows hardware and operating system requirements
If you are recovering to a new or rebuilt host, ensure that the following requirements
are met:
◆The hardware configuration is the same as the original host configuration.
◆The same Operating System version and Service Packs are installed.
◆The same Server Roles and Features are installed. These server roles and features
must be installed before starting the NetWorker disaster recovery tasks. These
roles include but are not limited to:
Task 2: Satisfy the NetWorker client or storage node recovery requirements
To recover a NetWorker client or storage node requires:
◆
A reinstallation of the same Windows operating system including any patches.
◆
The hostname is the same as the original host.
◆
The hosts file is updated to have entries for the backup server and domain
controller (if applicable).
◆
The same release and patch level of the NetWorker software that was in use prior
to the disaster.
◆
The installation path of the NetWorker software prior to the disaster.
◆
Backup or clone volumes that contain the NetWorker client or storage node data.
Note:
Recovering a NetWorker Client and Storage Node
Task 3: Reinstall the NetWorker client or storage node software
If the NetWorker client or storage node software is not properly installed and running
on the host computer, you must reinstall it according to these instructions:
1. To reinstall the NetWorker client or storage node software, refer to the
appropriate
EMC NetWorker Installation Guide:
• If the NetWorker installation kit is available on a shared drive, reinstall it over
the network.
• Reinstall the NetWorker software to the same path location it occupied prior to
the disaster.
• To update the NetWorker software, first recover the NetWorker client or
storage node to its predisaster state, then perform the update.
2. Reinstall any NetWorker patches that were installed prior to the disaster.
3. Reinstall the temporary enabler code for each EMC backup product. For
temporary enabler codes, refer to the product Installation Guide.
4. If you are recovering a NetWorker storage node, ensure that the storage devices
the NetWorker server will use are correctly configured. Details are provided in
the appropriate
EMC NetWorker Administration Guide.
Task 4: Recover the NetWorker client or storage node data
Recovering the client is a two step process. First, recover the SYSTEM or VSS
SYSTEM save sets. Once these save sets have been recovered successfully, recover the
System Drive and all other local drives.
To recover the NetWorker client or storage node data:
1. Log on to Windows with local administrator privileges.
2. Ensure that all drives that contained system information prior to the disaster are
accessible. The system information includes the boot partition, system partition,
and the partition that contains the databases and database logs for the system
state components.
a. Any Server Roles and Features that were installed before the disaster must be
installed before performing the disaster recovery.
b. If the host was on a domain, do not join the domain at this time.
c. Use the Disk Management utility (diskmgmt.msc) to create volumes (other
than C:) if they existed before. Ensure that these volumes are the same size or
larger than the original volumes.
3. Start the
NetWorker User program.
4. Click the
Recover button.
5. In the
Source Client dialog box, select the computer you are recovering and click
OK
.
Recovering a Windows NetWorker client or storage node
87
Recovering a NetWorker Client and Storage Node
6. In the
Destination Client dialog box, select the computer you are recovering and
click
OK.
7. The computer’s directory structure appears in the Recover window. Mark all
SYSTEM or VSS SYSTEM save sets for recovery:
!
Do not select local drive data for recovery at this time.
IMPORTANT• Windows 2003 and Windows XP Professional:
– SYSTEM STATE:
– SYSTEM FILES:
– SYSTEM DB:
Alternatively, if you are using Windows 2003 and Volume Shadow Copy
Service (VSS) is licensed and enabled, or for Windows Server 2008, Windows
Vista or later, mark these save sets:
– VSS SYSTEM BOOT:
– VSS SYSTEM FILESET:
– VSS SYSTEM SERVICES:
– VSS USER DATA:
– VSS OTHER:
– VSS ASR DISK: (Windows 2003 only)
8. From the
Option menu, select Recover Options.
9. In the
Recover Options dialog box, select Overwrite Existing File.
If you do not select
Overwrite Existing File, the recovery process pauses before
any existing files are overwritten. A
Naming Conflict dialog box appears,
prompting you to indicate how the NetWorker software should resolve filename
conflicts.
10. Click
Start to begin the recovery.
Recovering a NetWorker Client and Storage Node
11. Check the log file to verify that no error messages were generated during the
recovery sessions. The NetWorker software logs information about the recovery
process to the \logs file. This file is overwritten each
time a recovery is performed. If there are error messages in the log file, you might
need to run the recovery again after addressing the source of the errors.
12. After recovery, reboot the computer to completely recover the system-protected
files and restart services that were automatically stopped prior to recovery.
If the host was a member of a Windows domain, it will rejoin the domain after the
reboot operation.
13. Log on to the host and recover the system drive and all local drives.
a. Start the
NetWorker User program.
b. Click the
Recover button.
c. In the
Source Client dialog box, select the computer you are recovering and
click
OK.
d. In the
Destination Client dialog box, select the computer you are recovering
and click
OK.
e. The host’s directory structure appears in the Recover window. Mark all local
directories and drives,
except for the NetWorker installation directory, for
recovery.
f. From the
Option menu, select Recover Options.
g. In the
Recover Options dialog box, select Overwrite Existing File.
h. Click
Start to begin the recovery
Note:
At the end, we have followd up these steps again and we were out of space on c: drive but we manage it and now windows 2008 R2 system is up and running perfectly.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 16th, 2011 03:00
ok, so to cut the story short, you had an issue with disk space which has been addressed and all is ok now, right?
pritsehsolanki
6 Posts
0
June 16th, 2011 21:00
Hi,
The logs says disk space issue, we have deleted some temp. files and user profile to make space during recovery and then machine boot up perfectly. The system manager checked the system but he said that "the system state recovery is not not successful". We are try to restore it again. Can you tell me how can I make sure system state has been restroed successfully windows 2008 server?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
June 17th, 2011 06:00
You really have to be more specific - you need to find out what hasn't been restored successfully. If system manager (who is admin I guess) stated that then he should give you a hand by saying which does not seem to be right.
As stated before, with win2k8, steps I used are:
- redeploy machine (without joining domain) and make sure patch level is the same as at the time when backup you plan to use for restore
- install same NW version
- restore everything
- reboot