Backup Increment failed the operation failed because the vcenter or esx server reported that the virtual machine's configuration is invalid
Hi, i have some problem with backup VM increment with error : 0xe00095a7 - The operation failed because the virtual center or ESX server reported that the virtual machine's configuration is invalid. Final error category: Resource Errors For additional information regarding this error refer tolink V-79-57344-38311 i already doing troubleshoot with this link https://www.veritas.com/support/en_US/article.TECH139019 and then, i already reinstall RAWS and restart server after reinstall. The problem still occured, but the job full backup no problem. the job backup full successful. the problem occur just job increment. what should i do? note : windows server 2008 R2 standart bakup exec 2012 SP4 hotfix 217347
Server 2012r2 - Hyper-V GRT Errors
Hi I thought i'd join these forums and ask a question in case anyone can help me, Symantec support have had my call for over a week now with little responce other than taking more and more logs. Basically, we haveServer 2012r2 running Hyper-V. There are 2 VM's, one a DC, and the other Exchange. When we purchased the product we were advised that Small Business Edition would do what we needed. Upon installing it we found that although it could talk to Hyper V, it did not come with the Hyper V agent, so we had to do our backups with the physical agent. All backups worked perfectly at this point, both atAD level and Exchange level. I was annoyed that although I was sold it as a Hyper V backup solution, we did not get the correct agent to do the recommmended backup type. 3 months later suddenly my licensing panel goes from 'servers licensed 3, to servers licensed 1'. I ring Symantec and get told my many people (although there was a lot of confusion) that small business edition only is for 1 server :S... (I rang the Symantec Rep at the distrubution and he told me that him and all his team have been selling it for 3 servers for years, and clearly at one point it was for 3 servers as the license did say 3 servers' Symantec support were very keen to migrate me to 'Capacity Lite' edition, since I had no other option i took them up on it... A symantec rep for the UK rang me back after a few days explaining loads of people had been onto him about this licensing change and were not happy about it. Its something to do with Veritas but anyways... Being on Capacity Lite edition, this entitled me to the Agent for Hyper V. Great.. So I re-created my backup joband set it running onto my RDX solution. The full backup worked perfectly and i thought great. The next night, i do an incremental and i get 'V-79-40960-38531 - During Granular Recovery Technology (GRT) operations, the necessary boot configuration files could not be loaded. Backups that were enabled for GRT may not be available for restore.' The job completes with sucess with expections. And as the error message says, my files were not avaiable for restore, so this was a bit useless for me. Since i've not been getting too farwith Symantec, i've been looking into it myself and i've found Iget a lot of disk and ntfs errors in the last few mins of the backup job. I thought oh no and checked all the Raid Drives, everything is perfect. Not a single diskor ntfs error in the life of the server, by the way, everything in this setup is brand new although Live. I looked over the times where backups had ran for my 'physical agent' backups, no errors atall. The error logs refer to a volume that is certainly not a physical volume on the server, nor my RDX drive,see one of the screenshots where it refers to volume //?/ Is it trying to mount the VM's VHD's to catalouge the files? Full Hyper V backups run perfectly with no disk errors. I think this is related to why i get the GRT errors. I've currently made a seprate job for my DC which makes testing easier, as its incrementals take around 12 mins so i can troubleshoot issues. Could it be something to do with a system partition on the VM's? But then why does a full work.. ahh. So many questions :) Hopefully someone can help out. If i cannot get this going i'm going to have to do Agent based backups but I understand full recovery is a lot more difficult. I've had to raise this call to an advanced tech guy as the basic ones were asking me to turn it off and back on again.. Thanks DaveBE 15 Fails to duplicate Most recent full backup
Hi, i can´t get the duplicate thing work on the BE 15 installation (FP1 is installed, no other updates are available). I created a plain new backup of a virtual sql server (Hyper-V) with GRT enabled for SQL and with an additional Log backup. The full backup to disk run´s from 09:20 - 10:47 and is successful. The catalog thing runs from 10:47 - 11:31 and is successful. The duplicate job runs from 12:30 and has the job status Skipped. All data has a retention (Keep for) time of 4 Days ... This is the error message i receive.. Error category : Error : e000e054 - The job was skipped because the source backup job is not present. I deleted the job definition multiple times and created a new job straight forware, no editing afterwards. What´s wrong with BE 15?
V-79-40960-38467 - Virtual machine SERVERNAME has been excluded from the backup because it must be put in a saved state to back up
There have been several other posts with this error. Most of them unresolved. I have tried everything in them, hence new post. Hyper-V Host running Windows Server 2012 R2 Datacentre and Backup Exec 15 All updates for Backup Exec installed (same for Windows) 2 Virtual Servers included as Hyper-V backupsboth report: V-79-40960-38467 - Virtual machine "Servername" has been excluded from the backup because it must be put in a saved state to back up. There are no other servers (virtual or physical), just the Hyper-V host and 2 guests. One Guest runs Windows Server 2012 R2 Datacentre. The other runs Windows Server 2008 R2 Standard. I have run through the following articles: https://www-secure.symantec.com/connect/forums/v-79-40960-38467-virtual-machine-servername-has-been-excluded-backup-because-it-must-be-put-s https://support.symantec.com/en_US/article.TECH64287.html https://support.symantec.com/en_US/article.TECH209419.html https://www-secure.symantec.com/connect/forums/backup-exec-puting-hyper-v-vm-saved-state Although for previous versions of Backup Exec and Windows Server, ran through posts anyway. Everything checked already. I cannot use the option to untick the "Exclude Virtual Machines that must be put in a saved state to back up" as the servers have software that should be available 24/7 ideally. Also, you really shouldn't have to do this. SCVMM issues (2008 R1). We have never had SCVMM installed. Purely Hyper-V management The Hyper-V integration services are installed and the VSS integration service is enabled (inc. COM+, DTC services as well) Yes. Both virtual servers have latest integration services and have all the services enabled All virtual machine disks are configured within the guest operating system as NTFS-formatted basic disks. Yes Each virtual machine volume must specify itself as the storage location for its shadow copies Yes All integration services enabled on Hyper-V settings Yes - all other than Time synchronisation on one of the servers due to it being the PDC-E Domain Controller and syncing from external host Second server (not a DC) has all Integration Services ticked Ensure 20% disk space free on host and VMs Yes Ensure plenty of un-fragmented RAM is available on the host. Yes Backup Exec agents installed on VMs Yes Add reg key:HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore ---REG_DWORD:ScopeSnapshots:0x0 I have not done this yet. Also article says this is for Windows Server 2012 guest only. One guest is 2012 R2, other is 2008 R2. Reluctant to add change unless I know exactly what it does and why - no explanation provided Run backup as Remote Agent instead of Hyper-V VM selection I have not done this yet and will try at earliest opportunity but not really a good solution Any thoughts? Thanks. Sam Hobday @ Flair 4 IT
GRT backups of Exchange not truncating
When we do a GRT backup of our virtual Exchange server (Windows Server 2008 Ent) through our hyper-v host (Windows Server 2012 R2) with GRT enabled this does not truncate our logs. There are no errors on the job and says it's successful. When I check back in the log directory of exchange, all the logs from the databases still exist and have not been flushed. I'm running Backup Exec 2014 with SP2 + HF227745 Side note; when we run a backup of the Exchange server as if it were a physical machine the logs are truncated without issue (so it leads me to believe that this is not an issue with our Exchange server) I have a ticket out with Symantec for over 2 months now and the tech(s) that are assigned to my case don't seem to be making much leeway in steps to figure out what's wrong so I wanted to see if anyone else has experienced this issue and found a resolution?
