BE15 compatibility with BE 21
Hi all My client have BE 3600 R4 appliances with BE15 but it starts the decommision of this devices. Before it decommised the appliance, I need to implement a new BE console over a physical server with Windows Server 2012. My question is, it is possible to implement the new console with BE 21 and restore de backup images created with the BE 15 software on teh appliances? Thanks for your support.1.1KViews0likes3CommentsBackups failing after enabling DFS on server
I have a file server setup that everyone in my organization uses as a network drive to save their documents to (D: drive). Backup exec has worked just fine backing it up until I enabled DFS on the server this past week. Now backup exec runs for 3 minutes and then errors out and says: The job failed with the following error: The directory or file was not found, or could not be accessed Directory DfsrPrivate\ was not found or could not be accessed. None of the files or subdirectories contained within will be backed up I noticed on the D drive (the drive all the data I'm wanting backed up resides) there is a hidden folder on there now called DfsrPrivate and its a shortcut to a differnet location. I tried ommitting that directory and re-running the backup and it does run, but it only backs up like 30 MB of data and I have about 75GB of data on that drive. Am I missing something simple here or what?885Views0likes1Commentthe infamous ralus agent with lib load errors on SLES
Hi, I installed ralus agent 20.4 on a fresh SLES 15. Install went trhough without error. Ran a test backup and that says success on BE Server. Yet When I start ralus agent with sudo ./beremote --log-console & I get NDMPDMainThreadFunc spawned: grpid=1, tid=-2123458816 : FS_InitFileSys : libbedsnt5.so could not be loaded: 0x 2 (2) : libbedssql2.so could not be loaded: 0x 2 (2) libbedsxchg.so could not be loaded: 0x 2 (2) : libbedsxese.so could not be loaded: 0x 2 (2) : libbedsmbox.so could not be loaded: 0x 2 (2) : libbedspush.so could not be loaded: 0x 2 (2) : libbedsmdoc.so could not be loaded: 0x 2 (2) : libbedssps2.so could not be loaded: 0x 2 (2) : libbedssps3.so could not be loaded: 0x 2 (2) : libbedsupfs.so could not be loaded: 0x 2 (2) : libbedsshadow.so could not be loaded: 0x 2 (2) : libbedsoffhost.so could not be loaded: 0x 2 (2) : loaded libbedsvx.so Do these have to be loaded for ralus to work properly ? I searched and found quite a few fellow-ralus-experimenters with the same log entries but I havent found anyone who successfully got rid of them. then further down: libbedssmsp.so loaded at index 11 libbedsra.so could not be loaded: 0x 2 (2) libbedsdb2.so could not be loaded: 0x 2 (2) libbedsvmesx.so could not be loaded: 0x 2 (2) Initializing FSs FS 1 failed to initialize: 0xE000FE46 Do I need the FS 1 initialized for ralus to work properly? Oh and Veritas engineers, could you consider compiling ralus for more linux distros ? thanks chris900Views0likes1CommentBE2015 adding Enterprise Option but EO is BE2016
So I'm wanting to add Enterprise Option to BE 2015 for CASO but the link I get form Veritas with my entitlement number takes me to BE2016 Feature Pack 1... My issue is this .. I still have 2003 servers runing AD and this is why I cannot go to BE2016 yet. If I install this option is it going to take me to BE2016... Is there a link to previous version of Enterprise option? Do I just need the SLA key and enter it which "unlocks" the option in BE2015? Thanks in advanceSolved1.9KViews0likes3CommentsBackup Exec 2010 R3 stuck on verify
Hi, I'm using HP tape drive (LTO4). The job gets stuck on verify part (somewhere between 20-40% of the progress). After cancelling the job, Byte Count immediately forwards to the value that is 100% of completion. Looking at Job History, every single Backup and Verify operation has status Completed, without any errors or exceptions. Backup is set for 3 servers (2 remote agents), all of them are Windows Server 2008 R2. What can cause this problem, how can I solve it? I've tried the LiveUpdate (BE was updated, but it didn't solve the problem), deleting tape drive, restarting Remote Agent services.2.6KViews0likes7Comments