Good day All,
We started updating Firmware on lot of Physical Servers and as part of Pre-requisites we started taking System state backup's and lot of 2008 Severs system state backup was failing.
In-case you guys are wondering what we will do with system state backup? can we restore the Server back in case of disaster well, check this article i have posted, 2 Servers was successfully restored with the process in this link
After some search and couple of these blogs really helped so what really the issue is?
Well let me see i can put in simple and there are lot of blogs which tells in-depth if you google on enumeration errors.. so what basically happening while taking System state backup is Backup process is making sure that all the image paths for the Service is correct and in that process if it sees any invalid paths it stops the backup process with error code...
http://blogs.technet.com/b/askcore/archive/2010/06/18/ps-script-for-blog-enumeration-of-the-files-failed.aspx
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03921757&cc=ca&dlc=en&lc=es
So for starters download the Powershell script, enable Script execution in PS and run the PS script.. you will see output something like this..
Service Name :
Service Caption :
Registry key :
Value :
Reason : The service path contains spaces, the whole path needs to be enclosed using double quotes
The good part about the script is it tells what needs to be done so be cautious when changing something in registry .. below are the few things i have seen as errors..
1. The service path contains spaces, the whole path needs to be enclosed using double quotes
2.The service path contains a forward slash. Only paths containing an inverted slash are supported
3.The service path does not have a proper path format. Only paths beginning with [<Drive>]:\ format
are supported.
4.The service path contains invalid characters. Characters < > : " | ? cannot be used in a file path
5.Non-Existed Volume
We started updating Firmware on lot of Physical Servers and as part of Pre-requisites we started taking System state backup's and lot of 2008 Severs system state backup was failing.
In-case you guys are wondering what we will do with system state backup? can we restore the Server back in case of disaster well, check this article i have posted, 2 Servers was successfully restored with the process in this link
After some search and couple of these blogs really helped so what really the issue is?
Well let me see i can put in simple and there are lot of blogs which tells in-depth if you google on enumeration errors.. so what basically happening while taking System state backup is Backup process is making sure that all the image paths for the Service is correct and in that process if it sees any invalid paths it stops the backup process with error code...
http://blogs.technet.com/b/askcore/archive/2010/06/18/ps-script-for-blog-enumeration-of-the-files-failed.aspx
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c03921757&cc=ca&dlc=en&lc=es
So for starters download the Powershell script, enable Script execution in PS and run the PS script.. you will see output something like this..
Service Name :
Service Caption :
Registry key :
Value :
Reason : The service path contains spaces, the whole path needs to be enclosed using double quotes
The good part about the script is it tells what needs to be done so be cautious when changing something in registry .. below are the few things i have seen as errors..
1. The service path contains spaces, the whole path needs to be enclosed using double quotes
2.The service path contains a forward slash. Only paths containing an inverted slash are supported
3.The service path does not have a proper path format. Only paths beginning with [<Drive>]:\ format
are supported.
4.The service path contains invalid characters. Characters < > : " | ? cannot be used in a file path
5.Non-Existed Volume
Couple of things i have noticed
1. Cluster Servers, the server is active on one node and the respective Service is active on that node, you will see that Service warning failure in the PS script you run.. in that case we couldn't never fix it.. before we do activity we failed over the node took the system state backup and then proceeded with firmware update..
2. Warnings in the Script can be ignored
3. the service path contains a reparse point. Paths containing a reparse point are not supported - can be ignored too..
As I progress and if i encounter more backup failure errors will update this post..
Hope this helps someone!!!!
No comments:
Post a Comment