Home > Error > Error - The Location For Backup Is A Critical Volume

Error - The Location For Backup Is A Critical Volume

Copyright © 2016, TechGenix Ltd. 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. Are there any database file / application installation on the D drive? This blog is related mostly to Microsoft Windows 2008, great virtualization - HYPER-V or its client, workarounds, tips & tricks.

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. Nirmal can also be found contributing to PowerShell based Dynamic Packs for ADHealthProf.ITDynamicPacks.Net solutions. network administrator tools Network Configuration Management Network inventory software Network Mapping Network monitoring / management Network Traffic Monitoring Patch Management Remote control software SharePoint Tools Software distribution and metering Storage and Try our product. © 1999 - 2015 Ahsay Systems Corporation Limited. http://www.backup-utility.com/res/backup-location-critical-volume-4348.html

Windows only allows you to separately backup one Registry subkey at a time. Change the value as below:Name: AllowSSBToAnyVolumeData type: DWORDValue data: 1 (“0” - Don't Allow, “1” – Allow If you want to go back the default setting, you can just switch from CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Think will help lots of ppl using W2K8 January 19, 2009 at 1:59 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Poo Ching

This means the temporary storage drive that you have specified is actually a critical volume. No Yes Did this article save you the trouble of contacting technical support? Veritas does not guarantee the accuracy regarding the completeness of the translation. If a system state backup is stored on a source volume, backup settings should be configured for full backups.

greno2 Posts: 1Joined: Tue Dec 21, 2010 7:25 pm Top by PG » Wed Dec 22, 2010 4:18 am Try this. 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 Now, you can download the thirty-day trial version of this server backup software. http://www.windowsnetworking.com/kbase/WindowsTips/WindowsServer2008/AdminTips/Miscellaneous/HowToAllowSystemStateBackupsToCriticalVolumesInWindowsServer2008.html This is a restriction impose by Microsoft's WBAdmin that the backup location of a System Backup cannot be on a critical volume.

PG Posts: 1021Joined: Thu Feb 18, 2010 5:57 am Top by ahh-say-what » Wed Dec 21, 2011 7:36 am Can anyone confirm this fix? 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 Backup system state to another location instead of the partition that is included in the backup.2. Microsoft has provided a workaround.

Tried many things but nothing has fixed this issue. ********************************************* 1 Info 2010/10/27 17:00 Start [ Windows Server 2008 (PC-NAME-HERE), BDB OBM ] 2 Info 2010/10/27 17:00 Start running pre-commands https://www.veritas.com/support/en_US/article.000034194 Support3 Posts: 6069Joined: Wed Jan 02, 2008 11:08 am Website Top by GDRBrian » Sat Nov 05, 2011 6:49 am Support3 wrote:You can actually enable System State backup to critical Any update on this issue? This scenario mostly exist in virtualization environment, do we really need to attached another volume for the purpose of backup system state?It is always recommended that store your backup at different

No Yes How can we make this article more helpful? Hence, you would never worry about the error that the location for backup is a critical volume. You cannot comment on this entry Your name: Email Your comment: Please enter the captcha code submit Records in this category Can I perform a "bare metal" restore?How to perform a paste the below into a txt file, rename to a .reg and merge into the registry on the affected machine ------------------------------------------- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup] "AllowSSBToAnyVolume"=dword:00000001 ------------------------------------------- PG

Sorry, we couldn't post your feedback right now, please try again later. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Using Windows 2008 native backup to test backup of System State causes "ERROR - He also recognized as a Microsoft Champ. All Rights Reserved.Privacy Policy | Terms of Use {{offlineMessage}} Store Store home Devices Microsoft Surface PCs & tablets Xbox Virtual reality Accessories Windows phone Software Office Windows Additional software Apps All

GDRBrian Posts: 4Joined: Tue Dec 14, 2010 7:08 am Top by Support3 » Mon Nov 07, 2011 9:56 am Can I ask what version of AhsayOBM are you using? The leading Microsoft Exchange Server and Office 365 resource site. To revert to the default behavior, set the value to 0 For more Information Please see the following KB.

Running other jobs such as Exchange and File System completes ok.

Besides backup, the restore feature of Backupper is also extraordinary as it enables you to perform dissimilar (universal) restore even if your Server is unbootable. Therefore, to backup system is highly recommended to replace it . The only thing worth mentioning is that the Windows 2008 R2 is virtual not physical but this shouldnt make a different. It is possible that updates have been made to the original version after this document was translated and published.

SafeBackup Policies & Legal Attributions Privacy Policy Terms & Conditions ©2014 SafeBackup, All rights reserved. This is because of the default behavior of Windows Server 2008. Read More Windows Server 2012/2008/2003/2000/XP/NT Administrator Knowledge Base Categories Windows 2000 Windows 2003 Windows 7 Windows 8 Windows NT Windows Server 2008 Windows Server 2012 Windows Vista Windows XP Products Software USB-Stick costs money which won't be payed by the customer.

Furthermore, how many volumes are there on the server. Please refer to the following document from Microsoft for detailsThanks. Change Registry subkey to allow you to write system state backup to a critical volume. Please excuse.

Please refer to the following document from Microsoft for details: http://support.microsoft.com/kb/944530/en-us Thanks. We will reward you accordingly if your articles are helpful to the communities. 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 Locate the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\2.3.

This behavior occurs because system state backups to critical volumes are blocked in Windows Server 2008.