Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Performing a System State backup and restore on Windows Server 2008 (1035623)

Last Updated: 6/17/2020Categories: How toTotal Views: 13877Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

This article provides steps to backup the System State from the Primary server and restore it to the Secondary server on Windows Server 2008 environments.

Note: If you are performing this procedure on Windows Server 2003, see Backing up the System State from the Primary server and restoring it to the Secondary server on Windows Server 2000 and 2003 (1009790).

Resolution

Use this procedure when the backup of the System State is to be taken from the Primary (active) server and restored to the Secondary (passive) server. If the configuration of the server pair is different, contact VMware Support. For more information, see How to Submit a Support Request.

Note: The backup file at a minimum is as large as the System Volume and therefore requires at least an equal amount of free disk space. Ensure that sufficient free disk space is available before proceeding.

On the Primary Server:

On the Primary server, open a command prompt. Click Start > Run, typing cmd and clicking OK.

Run wbadmin start systemstatebackup -backuptarget:Drive_Letter:

If you attempt to perform a System State backup to a volume on which the System State file resides, you see this error:

ERROR - The location for backup is a critical volume.

Note: To fix this issue, see the Microsoft Knowledge Base article 944530.

If you perform the System State backup and store it on a non-critical volume, the backup completes successfully.

The backup file is created at <Drive_letter>:\WindowsImageBackup\<ComputerName>\SystemStateBackup\Backup Folder.

Copy the entire WindowsImageBackup folder from Primary server to a shared folder on the Secondary server. This is important as wbadmin expects a shared folder as a backup source location.

Note: If the WindowsImageBackup\<ComputerName>\SystemStateBackupfolder also contains backup folders corresponding to old backups, exclude the backups from the copy.

On the Secondary Server:

Unplug the Principal (Public) and VMware Channel network cables from the Secondary server.

Set the Neverfail Server R2 service to Manual using Windows Service Control Manager.

To get the backup version, run the command:

wbadmin get versions -backupTarget:”\\localhost\share name”

Perform the System State recovery with the command:

wbadmin start systemstaterecovery -backupTarget:”\\localhost\share name” -version:<version id>

For example:

wbadmin start systemstaterecovery -backupTarget:”\\localhost\share name” -version:01/14/2009-12:26

When the restore is complete, perform a server reboot. Multiple reboots may be required.

Verify that the network IP address settings are correct and ensure that the vCenter Server Heartbeat packet filter is enabled on the Principal (Public) network adapter and disabled for all channel network adapters.

If static routes were set up, check and correct them if necessary.

Launch the Configure Server wizard and click the Machine tab.

Change the Identity to Secondary and the Role to passive.

Click the Channel tab and verify that the correct channel IP addresses are displayed.

Click the Public tab and verify that the correct Principal (Public) IP addresses are displayed.

Click Finish.

If in a WAN environment, open a command prompt and navigate to <install_directory>\Neverfail\R2\Bin and run nfpktfltr getfilter. The response should be the Secondary server's Principal (Public) IP address. If the response is not the Secondary server's Principal (Public) IP address, run nfpktfltr setfilter secondaryIP. Confirm that the setting was applied by again running the nfpktfltr getfilter command.

Reconnect the Principal (Public) and channel cables to the Secondary server.

Set Neverfail Server R2 service to Automatic using Windows Service Control Manager.

Start vCenter Server Heartbeat.

Related Information

vCSHB-Ref-2243

Backing up the System State from the Primary server and restoring it to the Secondary server on Windows Server 2000 and 2003

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server 5.x のインストール及びアップグレードが次のエラーで失敗する：The Microsoft SQL server express edition installer returned error code: "2227044356" (2078392)

KB
•
VMware vSphere 4.x 上的 Microsoft Windows Server 故障切换群集：支持的配置指南 (2147663)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Heartbeat

Related Versions:

VMware vCenter Server Heartbeat 6.3.x

VMware vCenter Server Heartbeat 5.5.x

Take Our Survey

Support Assistant