Error - The Location For Backup Is A Critical Volume
Provider Compare Backup ProductsView Differences among Editions AOMEI PXE Boot - FreeFor Backup and Recovery Solutions AOMEI OneKey RecoveryOneKey System Backup Download AOMEI Backupper Standard - Freeware AOMEI Backupper Free Trial - 30-Day Support Support Center Help Documents Product Upgrade Forum Contact Us Sales FAQ Freeware Recommended AOMEI Backupper Overview All Features of AOMEI Backupper Screenshots Videos What Our Users Are Saying Awards and Reviews AOMEI Backupper Changelogs License Types Company Partners Join Our Newsletter Help Us Translate - Gift AOMEI OneKey Recovery Create a factory recovery partition and one key backup system and restore system for Desktops and Laptops. Learn More>> AOMEI Backupper Features System Backup Disk Backup Files/Folders Backup Partition or Volume Backup Schedule Backup Incremental & Differential Backups Command Line Backup Universal Restore System Restore Disk Restore Disk Clone System Clone/Migration View More >> AOMEI Backupper Introduction Free Download Help Documents Features List Backup Tutorials Video Tutorials New Features Change Logs Technical FAQ AOMEI’s Free Software AOMEI Backup Software AOMEI Partition Software AOMEI Windows PE Builder AOMEI PXE Network Boot Tool AOMEI NTFS to FAT32 Converter How to Fix "The Location for Backup Is a Critical Volume"?The ScenarioWhile you try to write system state backup to a critical volume (which is the volume that the state file are stored on, usually C: drive) on a Server running Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012, you will receive the following error:"The location for backup is a critical volume." In Windows Server 2008"The backup storage location is invalid. You cannot use a volume that is included in the backup as a storage location." In Windows Server 2008 R2"You cannot use a volume that is included in the backup as a storage location." In Windows Server 2012The CauseBy default, Windows Server 2008 or latter version of Windows Server does not allow to backup system state to critical volumes. Windows Server 2003 does not have this restriction to backup to critical volume.The SolutionThere are three ways to work this around.1. Backup system state to another location instead of the partition that is included in the backup.2. Change Registry subkey to allow you to write system state backup to a critical volume. Note that modifying the registry incorrectly may cause serious problems so that you need to reinstall Windows. You would better backup the registry before changing it. Windows only allows you to separately backup one Registry subkey at a time. Therefore, to backup system is highly recommended to
In Windows Server 2008? by Nirmal Sharma [Published on 14 Jan. 2009 / Last Updated on 13 Oct. 2008] This article explains a registry hack you can use to allow System State to be backed up to a critical volume in Windows Server 2008. When you try to backup the System State backup on a critical volume on a computer running Windows Server 2008, you will get the error message. This is because of the default behavior of http://www.backup-utility.com/res/backup-location-critical-volume-4348.html Windows Server 2008. It doesn't allow you to take backup of System State data on a "Critical Volume". You can change this behavior by hacking the following registry entry: KEY_NAME: HKLM\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup ENTRY_NAME: AllowSSBToAnyVolume VALUE: (0) - Don't Allow, (1) - Allow See Also The Author — Nirmal Sharma Nirmal Sharma is a MCSEx3, MCITP, http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2008/AdminTips/Miscellaneous/HowToAllowSystemStateBackupsToCriticalVolumesInWindowsServer2008.html and was awarded Microsoft MVP in Directory Services. In his spare time, he likes to help others and share some of his knowledge by writing tips and articles for various online communities. Nirmal can also be found contributing to PowerShell based Dynamic Packs for ADHealthProf.ITDynamicPacks.Net solutions. Latest Contributions Checking Active Directory Replication Status by Source and Destination Domain Controllers 27 Sept. 2016 Running Prerequisites check before installing a New Active Directory Domain 7 Sept. 2016 Is There Any Way to Clear DC Locator Cache on Windows Client Computers? 25 Aug. 2016 Hyper-V Windows Failover Cluster and IsAlive Operation (Part 2) 25 Aug. 2016 Hyper-V Windows Failover Cluster and IsAlive Operation (Part 1) 2 Aug. 2016 Featured Links Newsletter Subscription By subscribing to our newsletters you agree to the terms of our privacy policy Never miss an article by subscribing to our newsletter! Windows Server 2012 / 2008 / 2003 & Windows 8 / 7 networking resource site By subscribing to our newsletters you agree
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs https://www.veritas.com/support/en_US/article.000034194 Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research http://clintboessen.blogspot.com/2009/08/system-state-backup-in-server-2008.html Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Using Windows 2008 native backup to test backup of System State causes "ERROR - The location for backup is a error - critical volume" Article:000034194 Publish: Article URL:http://www.veritas.com/docs/000034194 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages error - the Subscribe to this Article Manage your Subscriptions Problem Using Windows 2008 native backup to test backup of System State causes "ERROR - The location for backup is a critical volume" Error Message ERROR - The location for backup is a critical volume. Solution Sometimes it is necessary to use the Windows 2008 native backup program to test system state backups in order to confirm if an Operating System issue is the reason for a problem affecting the operation of Backup Exec. SYMPTOMS When attempting to perform a backup of a Windows Server 2008 system state, to a volume on which the system state file resides, the following error is received: "ERROR - The location for backup is a critical volume." CAUSE This behavior occurs because system state backups to critical volumes are blocked in Windows Server 2008. RESOLUTION Review the following Microsoft KB Article 944530 to change the default
no more NTBackup so system state backups now need to be done using the 2008 backup utility. First you need to ensure that the backup features are installed including the command line ones in features under server management.You are then able to use the wbadmin command to backup the system state of a server by using:wbadmin start systemstatebackup -backuptarget:e:Please note that server 2008 by default does not allow you to backup to a network share or the critical volume (which is the volume that the system is installed on, ususally c:). If you do you will get this error:ERROR - The location for backup is a critical volume.If you only have one drive letter c: on a server and you need to back up to it, you can get around it by following Microsoft Knowledge Base 944530.Prerequisites to perform system state backups to critical volumes:- Make sure that the target volume has no shadow copy before the backup starts.- If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.- Periodically check that no other user or program maintains a shadow copy on the target volume.- Do not keep volume level backups and system state backups in the same location.- The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes.To enable the system state backup files to be targeted to critical volumes, you must set the value of the AllowSSBToAnyVolume registry entry under the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\Set the value of this entry as follows:Name: AllowSSBToAnyVolumeData type: DWORDValue data: 1 Create the key called SystemStateBackup:Create the DWORD called AllowSSBToAnyVolume:Give the DWORD AllowSSBToAnyVolume a value of 1:It will then go ahead and perform the task: Posted by Clint Boessen at 7:48 PM Labels: Windows Server General No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Clint Boessen [MVP] clint.boessen@avantgardetechnologies.com.au Clint Boessen's Blog Clint Boessen Perth, Western Australia, Australia Microsoft Infrastructure Engineer MVP, MCSE, MCSA, MCTS, MCP MCITP: Enterprise Messaging Administrator MCITP: Enterprise Messaging Administrator 2010 MCITP: Server Administrator MCITP: Enterprise Administrator TS: SCOM My TechNet Posts Join My RSS Feed View my complete profile Awards Labels Active Directory (108) AD LDS / ADAM (11) Applications (39) Backup Exec (12) Citrix (