Backup exec remote agent service stuck in stopping state.
I have face the below issue many times. Operating systame - Windows 2008 or Windows 2008 R2. Backup Exec 2012 having SP 3 installed. Most of the time when we restart the backup exec services, that time "Backup exec remote agent service" get stuck in stopping state. And in this stage we fail to stop and then start the service. Even taskkill command also desen't work to kill the beremote.exe process. And in this situation every time we require to reboot the server and then we found all backup exec services in running state properly. Does any one have solution on this? Regards, Santosh Pawar.1.3KViews1like4CommentsBackup Jobs are getting failed with V-79-57344-41488 - Due to one or more errors in \\server\E:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore.
Hello All, We are using Backup Exec 2014 SP2 In a Windows 2012 R2 server as a media server and taking backups of the Clients through Remote agent. Few are windows 2008 server and one of them is Windows 2012 R2 server. The issue started with the Win2012 R2 remote agent while backing up the backup is getting failed for the drives with the above mentioned error.The files are normal flat files. Media Server : Windows 2012 R2 64 bit Remote Agent : Windows 2012 R2 64 bit I have tried to take backup of those problematic folder through WIndows server backup however it got successful in that case. The account which we are using for taking backup is domain user however its been added to remote agents local admin too.But no luck. Would appreciate if any wrokariound or solution can be provided except asking for upgrade it to BE 15 ;) .Solved17KViews0likes10CommentsThe job failed with the following error
We have updated BackupExec from 2012 to 2014 and all job are running fine but on a few backup jobs i am receiving following error. In one job i am receiving following error.. Completed status: Failed Final error: 0xe000942a - Backup Exec did not find any resources to include in the backup. Check the backup selections for this job to make sure it includes resources that are available for backup. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-37930 and another job is failing with following error: Completed status: Failed Final error: 0x2000fe07 - FS_NO_MORE Final error category: For additional information regarding this error refer to link V-79-8192-65031 Please help me out in this...Solved5.4KViews3likes3CommentsDisk backups - automatic removal of expired files
I have a large disk storage that I do my backup to disk on then from there, backup to tape. I have an expiration date of 5 days. Question, what program does this cleanup and why does it work sometime and not other times?? Also, is there a place that you can set this program to run (specific date)? Thanks much CathySolved2.3KViews1like9CommentsBackup exec does not delete old jobs
Hi, I have this problem from time to time in about every version of backup exec I can think of over the years. From time to time, backup exec sends an alert saying to free space on the disk where it is backing up. So I have to manually delete the old .bkf files, even though the job is configured like this; Backup to a NAS, in the last case I had this problem,this NAS receives 1 backup per week, full, 2 servers backed up, 3 jobs in total (sql, exchange, data) Job is configured to keep for 2 days I would delete all the content of the directory where the backup is made, leaving only the 2 .cfg files. Then I would have a full wich will work, then next week when the second full would start, after a while, the job would still run until there is no free space (as I remember). So I manually delete the files of the first backup, go in alerts, respond to it, and the backup would countinue. This kind of problem happens from time to time, in about every type of configuration (we have multiple clients), to clients randomly. It seems that most of the time, it would delete old backups by itself, sometimes it does not, I have to do it manually. the only thing I could think of is when a problem appears during the backup and it does not complete, those .bkf files will not be deleted and over time, with other errors, these grow and take more and more space and are not deleted by backup exec automatically. We always use removable storage. Maybe there is a setting I did not see somewhere or something I must do to make sure that backup exec will delete old job as needed to free space. Any guidance would be appreciated. ThanksSolved6KViews1like9CommentsBacking up Active Directory: V-79-57344-33928 - (AD LDS) database was not found.
Hello, We have this error from time to time, but it usually fixes itself without any end user intervention. However I am getting this error three nights in a row now on one of our domain controllers. This started happening on Wed morning, and continued through Friday morning. In all three instances the error message in the log is: Job ended: Thursday, October 29, 2009 at 1:18:54 AM Completed status: Failed Final error: 0xe0008488 - Access is denied. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-33928 Errors Click an error below to locate it in the job log Backup- \\dc1.domain.com\System?State V-79-57344-33928 - Unable to complete the operation for the selected resource using the specified options. The Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database was not found. So I checked the selections and under the server in question, I can see System State > Active Directory > C:_WINDOWS_NTDS, and this is all checked off. I did a test Resource Credentials for everything in this backup and it all returnedsuccessfulso I'm at a loss. Under Settings > Microsoft Active Directory for this job properties we have all three boxes checked (GRC, Consistency Check, Continue if Consistency check fails.) Backup method is greyed out, but says Full - Back up entire Active Directory. We are using Symantec Backup Exec 12.5 for Windows Servers Media Server Version 12.5 Rev 2213 Administration Console 12.5 Rev 2213 Desktop and Laptop Option: Version 3.1 Rev. 3.41.32a Installed updates: Service Pack 2 Hotfixes: 324947 317436 325647 319242 324012 326004 323894 324011 Thanks for the help, we really do appreciate it!3.2KViews0likes11CommentsError V-79-100000-11223 VSS Snapshot Error
I am using Backup Exec 2014 - Server Version is 14.1 Rev. 1786 (64 Bit) I created a backup job on a new server with the standard Full/Incremental backup set. I did *not* select the Snapshot Option - that tab is completely blank. When I run the job, I get: -Snapshot Technology: Initialization failure on: "\\IGSBACEBGS017.gs.doi.net\Shadow?Copy?Components". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume. Some reasons for this could be: - The snapshot provider that you selected does not support the volume that you are trying to snap. Try selecting the default snapshot provider, and then run the job again. -A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot This server is 72 Terrabytes (native) but with formatting and RAID it shows as a 60 TB drive. The sector size is the standard 512. How can I back up my share? Doesn't Symantec Backup Exec work on large drives? Why does it try to force the snapshot option even though it is not selected? Thanks in advance for your help!!!Solved3.8KViews0likes5Commentsback up failed
I encountered this problem after the backup was done Completed status: Failed Final error: 0xe0000354 - Consistency check on Exchange objects cannot be performed because Backup Exec cannot find the required component CheckSGFiles.dll. Ensure that the Exchange Management Tools for Exchange Server is installed on the Backup Exec server. Final error category: Resource Errors For additional information regarding this error refer to linkV-79-57344-852I encountered this problem after the backup was done I couldn't find the solution online notethat the backup was done without any problems thanks1.2KViews0likes3CommentsError V-79-57344-34036
Hi, I have 2 incremental back ups storing on the same HDD, however one keeps failing when run to schedule with the details below. When I "Run Now" the job is succesful. The other incremental backup I have scheduled, runs successfull everytime. Backup- \\server.Local\E: Storage device "BackUp NAS101 Incrm" reported an error on a request to write data to media. Error reported: The specified network name is no longer available. V-79-57344-34036 - An unknown error has occurred. Job ended: 27 August 2013 at 19:41:41 Completed status: Failed Final error: 0xe00084f4 - An unknown error has occurred. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-340362KViews1like1CommentBackup Exec 2010 Error "There is not enough disk space"
Hello I am running Backup Exec 2010 R3 on Windows Server 2003 R2. For the past 2 weeks, I've hadthe followingrepeated failure message on some backup jobs: Storage device "Windows Full" reported an error on a request to write data to media. Error reported: There is not enough space on the disk. V-79-57344-34034 - An attempt to write data past the end of the media has failed. This and a few other backup jobs are backing up to a 1 TB local disk on the same server on which Backup Exec is running. These backup jobs have been running successfully for the last few years but now lately the backup disk is becoming full and some jobs are failing. No configuration changes have been made. I do see that backups from a 3 or 4 days ago are still present. By deleting them, the jobs continue. I must add that all of these backup jobs were created about 4 years ago by my predecessor and I have newly taken over these responsibilities.Backup Exec is very new to me and I have a few questions: 1. I would assume that the backup jobs where the data is written to harddiskare configured such that older backed files are purged automatically: is this correct? How do I determine this in the backup job's setup? 2. I have checked the Job Setup for each of the different backup jobs and I cannot see anything which indicates that a particular backup job is backing up to a hard disk instead of to a tape. How do I determine whether data is being backed up to hard disk or to tape? 3. I think that Catalogs are part of the backup process to hard disk process. I see that there are files in the ...\Program Files\Symantec\Backup Exec\Catalogs\BackUpServer folder dating back to 2009. Are these old files necessary? I would think that Backup Exec would automatically purge old unnecessary catalog files: is this correct, or do they need tobe purged manually? Or should theynot be purged at all? Thank you for your help. Yes, I know I need to read the user guide but it's over 1200 pages long and I need to get this issue resolved before I focus on training. Best regards, SuzanSolved1.8KViews1like4Comments