Backup exec backup job failure
I directly ran a full backup, but the backup was always queued, and there was no rate. The rate was 0. After trying to restart all backup services, I ran the backup task again but there was still no rate. Moreover, I found that the backup service would automatically stop, causing the backup to hang inexplicably. The backup task cannot be continued. How to solve this situation?541Views0likes3CommentsBackup 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 ;) .Solved17KViews0likes10CommentsBack up is slower than usual
We are using Symantec backup exec15 and when we run the back up, It is slower than usual, In job history, previous Job rateis 1000MB/min but now it became 500mb/min , please advise what to do to increase the performance. it was taking only 7 hours to do the process before but now it is taking 1 day already. Thanks in advance!525Views0likes1CommentMigrating BE 2014 to BE 21 on a new server problems
We are currently running Backup Exec 2014 on a Windows Sever 2008 R2. We need to decommission that server and migrate BE to a new Windows Server 2016. We are aware that BE 2014 will not run on Server 2016, so we are looking for the most effective/supported method of migrating. We’ve tried the Migration Assistant, but that will only go from Be 2014 to BE 20. Having Installed version 20, the migration fails on source database credentials and incompatibility. Trying the manual migration method, the copying of the database via beutility appears to work but then errors when attempting to start the services, leaving us with an inoperative system. We tried installing BE 2016 but that fails to open. We’ve tried all installs/migrations etc through various administrator/domain admin accounts and get the same errors each time. Have we any options left? Is there a recommended\foolproof method of migrating our current Backup exec catalogues\data\jobs etc to a more up-to-date and supported version compatible with Windows Server 2016? Has anyone else attempted this, and found any workarounds?640Views0likes1CommentEmergency Help
Dears Kindly Your Experience to Provide Solution For Below Contiguous Case from 25 days Some one From Our Company Tried Backup Exec 2014 as trial and make backup over tape then cyber attacj happened erase all Server even backup exec server now we make new installation of one server and install backupexe then try to restore it say in restore server not trusted and ask for credential and dont know what credential so can help to restore without this password or what suggestion532Views0likes0CommentsError 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.8KViews0likes5CommentsSDR failed to connect to backup server
Hi, our backup server is BE 2014 SP1 on Windows Server 2008 R2 SP1. We are trying to restore full system of some clients by using SDR. However, after we boot the client to recover with the SDR boot CD, when it asksfor connections to the backup server, although we put in the correct username and password, it always says it cannot connect to the backup server. Both the backup server and clients are in WORKGROUP. There is no domain in this network. Have anyone encountered this issue before? Any advice? Thanks in advance.Solved2.4KViews0likes9Commentslinux RALUS agent and BTRFS
Hello, After successfully installed agent for linux onto an Ubuntu Server 20.4 I can browse all storage content from backup exe except some folder. This Ubuntu server use BTRFS file structure and some sub volumes are not browsable by the RALUS agent. I have this message : "Failure to browse "gitlab" The directory or file was not found, or could not be accessed". I can browse in home directory or /root but not in certains sub folders like /var/lib/btrfs/subvolume/. How to give acces to these folders for RALUS agent ? Thanks :)1KViews0likes3Comments