1 of 1 people found this helpful
Are you sure that this is a 2k8R2 only problem? I have seen this symptom present itself many times over the years when people try and snapshot the whole system drive partition. This manifests itself because BL tries to do normal file actions on special files like the pagefile, etc. Windows denies the attempt to access the file and you get an error message and abort like you have specified?
What is it that you are trying to accomplish? Snapshotting a whole system partition is not good idea for several reasons, but targetting specific items of interest is the best practice.
Win 2008 R2 is supported with BBSA 8.0.00. See the full support matrix here http://media.cms.bmc.com/documents/BMCBladeLogicServerAutomationPlatformSupport-8+0+00.pdf (must have a valid support login).
The specific footnote for Windows 2008 R2 says
Windows 2008 R2 support for Agent in BBSA 8.0.00. Windows 2008 R2 support for Patch and Provisioning added in BBSA 8.0.00 SP1. App Server support on Windows 2008 R2 planned for BBSA 8.1.00.
Thanks to both of you guys,
Actually I think the same, we shouldn't be making a snapshot of the whole file system but our client wants to use BL as a "disaster recovery" tool, which is maybe not such a good idea, anyway, thanks for your help.
That is a work case that will not work, especially for windows. We do not utilize VSS to backup files and we do not touch system state data. Since you would have to reinstall the OS and the applications on the system anyway, it is just best to point the snapshot at files and configuration items that you would need to track for changes. They make tolls that have a sole purpose of backing up operating systems and files. BL’s file backup mechanism should really only be employed to backup certain files or directories before a deployment, and oftentimes this is still more appropriately handled by a enterprise backup solution.
What about a whole line as record grammar? Will that work for you?