Video Screencast Help

Windows full system restore.

Created: 04 Sep 2012 • Updated: 28 Nov 2012 | 9 comments
Willie_SA's picture
This issue has been solved. See solution.

Master/Media server Solaris 10

NetBackup 7.1

Client Windows 2003 R2

Client server crashed and restore required.

Following normal NBU backups available: (as seen from Status of Backup in Activity  Monitor).

Full backup - All local drives                                     Tuesday

Incremental backup - All local drives                          Wed/Thu

System state - Backup of system state                     Saturday

SQL backup - Full SQL backup.                                Every day

What is the easiest/quickest to restore the complete system.

They are re building the OS and then load NBU client.

Comments 9 CommentsJump to latest comment

V4's picture

If they are rebuilding it no need to restore All Local Drives. Post OS is up and is having NBU client restore System State and then restore your recent SQL backup

If other files from all local drives are required  those can be restored post SQL and system state is done

Nicolai's picture

Procedure for restoring entire system:

HOWTO: Use NetBackup to perform a restore for a total and complete recovery of Windows 2008 client(s) that includes C: (and other system) drive(s), Shadow Copy Component, and System_State from a reliable full Windows-NT backup without IDR or BMR in the event of a Disaster (or need to fall back to a known working state).

If you have BMR Please use that approach.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

sazz.'s picture

As you mentioned you already have OS installed i guess you are doing the manula recovery.

If you are planning to do complete manual DR make sure it is the same original machine with the same OS and HF.

Don't joing the server in domin.

make sure same IP and hostname.

Install NBU client

once installed create the folders bpcd and tar under logs on \Veritas\NetBackup\logs

You mentioned about System state - Backup of system state  on Saturday? does it contain C drive as well? As per best practise you should include your C drive and shadow copy components for ws 2003. SCC contains your system state in 2003.

If you have the complete SCC and C drive for Saturday, restore that first and make sure to select overwrite existing files. Check the tar folder for the successfull restore. If it is fine, reboot the system.
If you check the symantec article it suggests you to restore everything first but that will be waste of time if some system componenet is missing and you are not able to make your system up.

Restore the SSC and C drive and try to make the system up and it will automatically come into domain if everything works fine.
Once the system is up you can restore the other syste drives and SQL database.

Willie_SA's picture

The system is restored now, BUT the SQL database still needs to be restored.

Can you please guide me through the SQL restore. Thank you

Nicolai's picture

That should be the job of the SQL dba. Unless you know SQL there are no change you can see if the restore went well. SQL uses a buil-in backup/restore tool - the dba should know how it work.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Willie_SA's picture

The backup is made through NBU policy with ALL_BCH script, so these images will be visible/usable from the client - as it seems the restore needs to be done from the NBU client software.

Have asked the DBA to assist - will see what happens.

Nicolai's picture

A perfect team then :-D

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Mark_Solutions's picture

Usual full restore process ...

Build server, install NBU client, do full restore with overwrite files selected and reboot after restore completes

Next restore Apps

If case of SQL use the SQL GUI on the client itself to browse and restore SQL - you will need to restore the Master database first whilst the SQL Service is in single user mode and database is marked as overwritable.

After re-start SQL Server service in normal mode and restore the other databases

Hope this helps

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

sazz.'s picture

Microsoft SQL Server Administrator’s Guide Page 82 shows about the DB recovery

Also admin guide contains everything about the SQL DR recovery.

Step by step procdedure also listed below