Backup Exec 21 to Backup Exec 22
Hello Everyone, I have a new windows server 2019 with Backup exec 22 installed. I want to have all the servers we backed up to go to the new server but want to do so one server at a time to test everything and ensure it works, especially with the June updates. I keep reading that there can be issues if the backup server has a different name from the original backup server. We will not be moving the old data over to the new server we just want to start new basically.791Views0likes1CommentBackup Exec 2012 - LiveUpdate Stuck on SP 1a
Greetings, Every time I start the update using LiveUpdate to SP 1a, within a few seconds for starting the download, it fails with error LU1825 - Update might of gotten corrupted. I have since manually downloaded and installed the update. The issue is I still have the error on Liveupdate for SP 1a. How can I clear out this possible corruption so I can get updates using LiveUpdate again? Thanks, RobbSolved829Views0likes2CommentsB2D Jobs gone after migrating to new Server
Trying to upgrade to BE20 eventually. Upgraded W2008R2 server to W2012R2 and then had to uninstall original BE2014 (did not work after OS upgrade). Installed new copy of BE15 and did not touch the Ext HD BEData folder that was used for B2D. Was able to use a VM copy of the original W2008R2 w/ BE2014 (vm ran on different PC w/o the EXT HD)and upgraded to BE15 and then W2012R2, so physical server and VM servers are the same OS and BE15 versions. The upgrade to BE15 did not put a BEData folder on the C: system drive. Can't put the VM on the network to use migration assistant so followed article100020224 "How to migrate (move) Backup Exec from one system to another with the same version of BE, Windows and same or computer names". Followed instructions and copied the Catalogs\Data folders to the clean install of BE15. They mention "create a folder where the new Backup to Disk folders will reside and copy the saved off .bkf file(s)", but this doesn't make sense to me as the fresh install created that, but I want to use the existing one ont the EXT HD. In any case, BE15 runs, sees the EXT HD online and limited to "read-only" under storage tab, but when I click on it, it only shows Job History entries and not the Jobs or backup sets from before. In addition, if I try to do a test restore, the past backups dates are not there to choose from. Is there something else I can do to have theExt HD BEData folder fully recognized (Jobs, etc.)? Tnx..594Views0likes0CommentsUpgrade Install Location_Remote Administtrator Files
Hi. I am attempting a BE15 install in hopes of upgrading the existing BE2012, on a server that I already upgraded to W2012R2(BE2012 is not working b/c of un-startable BE services after the OS upgrade) from W2008R2. I am at the install "Destination" stage and when I choose "default location" , which is the existing BE2012 location, I get the msg "Remote Administrator files are available at the following location:C:\Program Files\Symantec\Backup Exec\ Make sure you select a new destination folder". How do I get past this error message w/o picking to install (hopefully upgrade) BE15 at a different location than this? If this upgrade is not possible b/c BE2012 isn't running on the newly upgraded server, what is the best approach? Is it to use the Migration Assistant (will this work for BE2012 to BE15) as stated in article 100001807? Tnx.729Views0likes0CommentsUpgrade from Backup Exec 2012 to 2014 AFTER upgrade to W2012R2
Hi. I upgraded W2008R2 to W2012R2 because of MS end of support without realizing that my installed BE 2012 was not compatible with W2012R2. So now BE2012 won't launch. I have the install media and a license for BE2014. Can I do an install and have it upgrade the existing BE2012 version? If so, is it a straight forward upgrade, and if not what is the best way to install BE2014 and apply my old settings (catalogs, job history, tape drive drivers, etc.)? Thanks1.6KViews0likes3CommentsInstalling 20.4 unable to authenticate with the user and password
Veritas support has been absymal on this. I have been speaking with several technicians for the past two weeks and none of them have provided any resolutions. I am trying to update Backup Exec 16 to 20.4 as standalone. The serever passes most of the enviroment checks successfully but has a warning that the current user does not have permissions to log on to SQL server instances that have a designation of '**' even though the account i am logged in tohas full permissions to the SQL database, can act as part of the OS, log in as service account, and create tokens. The Backup Exec SQL Upgrade Check will randomly fail. sometimes it does, soemtimes it doesnt. I'm unsure why because the SQL instance is within the compatibility range at 2008 R2S2 and cannot be upgraded. If i make it to the start instal screen, it will refuse the domain credentials we used to set up the backup server initially, suceed with local adin credentials, run for 30 minutes then fail again saying it was unable to authenticate with the user and password provided, which have been tested in RDP. Please someone help.1.4KViews0likes2CommentsBeckup Exec 16 upgrade to 20.2
We are trying make an upgradefrom version 16 to 20.2. We found tips from this forum and from Verias pages. At first stage, OS is Windows Server 2008, so we made new installation of Windows Server 2012. New installation of BE 16 and Live Update to last version. We made copy of old Catalog folder to new Catalogs folder (copy and rename), copy of BEX* files from Data folder and made copy of database with beutility.exe. We made a new item in registry etcpath for deduplication engine. We found that new installation was in path Program File\Symantec while new installation is at Veritas. So there was needed editBackupExecDeduplicationStorageFolder\etc\pdregistry.cfg from Symantec to Veritas. After these steps BackupExec 16 start working. All looks good and the same as in old WS2008. We tried make an established trust to one of servert and tried first backup. Succesfully. BTW Deduplication engine starts 20 minutes and has 7GBs in memory. At this we has been tried to run upgade to 20.2. No warning for prerequisities (only not installed ADK). But installation failed.The return code from the MSI is: 1603. We found that setup must be run as administrator. Next setup is more quick and installation failed too. We tried to run deduplication engine and wait till Starting of service has been changed to Started exactly before last steps after that setup quickly fails. We tried installation without without licences as trial. We tried maintanance of database, We tried made shorter path from which is iso mounted. Not helped anything. No solution. Not found help for error codes from attached log. Till solution we've started normal backuping in version 16.Solved1.8KViews0likes2CommentsBackup Exec 2010 Serial Key?
Hey Guys, im trying to find out what my serial number is on my server so i can upgrade to latest version of backup exec. I can find the license keys etc in backup exec but not the serial number. Anyone know where i can find this? Thanks in advanceSolved3.8KViews1like5CommentsBackup Exec 2015 - Agent For Windows???
Hello all - I am currently upgrading my servers (FROM:Windows 2008 R2 withBackup Exec 2010 R3,TO:Server 2012 R2 with Backup Exec 2015). I do not recall everneeding a separate - 'Agent for Windows' when I purchased my licenses Backup Exec 2010 R3. *Therefore my question is, will I now be missing functionality that I had before with 2010 R3?* Thanks in advance! :)4.5KViews0likes19CommentsBackup Exec 2010 to 2014 migration failed
When I try to migrate Backup Exec 2010 R3 SP4 to BE 2014 it failed during database migration. In BKUPINST log I found this lines when error occures: 09-04-2014,16:02:27 : upgradeViaSQLScript2 using CDBOperation SQLInstance=(null) SQLScriptFile=DBUpgrade13.5-2c.sql 09-04-2014,16:02:27 : dbutil RunSQLScript: DBUpgrade13.5-2c.sql SQLServer:BES2010 SQLInstance:BkupExec DatabaseName:BEDB 09-04-2014,16:02:27 : OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BEDB;Data Source=BES2010\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0 09-04-2014,16:02:27 : upgradeViaSQLScript m_JobMigInternal=0 09-04-2014,16:02:27 : upgradeViaSQLScript2 using CDBOperation SQLInstance=(null) SQLScriptFile=DBUpgrade13.5-2d.sql 09-04-2014,16:02:27 : dbutil RunSQLScript: DBUpgrade13.5-2d.sql SQLServer:BES2010 SQLInstance:BkupExec DatabaseName:BEDB 09-04-2014,16:02:27 : OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BEDB;Data Source=BES2010\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0 09-04-2014,16:02:30 : upgradeViaSQLScript m_JobMigInternal=0 09-04-2014,16:02:30 : upgradeViaSQLScript2 using CDBOperation SQLInstance=(null) SQLScriptFile=DBUpgrade13.0-leros.sql 09-04-2014,16:02:30 : dbutil RunSQLScript: DBUpgrade13.0-leros.sql SQLServer:BES2010 SQLInstance:BkupExec DatabaseName:BEDB 09-04-2014,16:02:30 : OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BEDB;Data Source=BES2010\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0 09-04-2014,16:02:32 : Invalid column name 'finaljobstatus'. 09-04-2014,16:02:32 : dbutil RunSQLScript: execute sql cmd failed. sql statement: CREATE FUNCTION [dbo].[ResourceContainer_GetProtectionInfo] ( @ResourceContainerID uniqueidentifier ) RETURNS xml AS BEGIN declare @retValue xml DECLARE @disableUseAnchorDate bit SELECT @disableUseAnchorDate = 0 -- dbo.[ResourceContainer_GetDisableUseAnchorDate]() IF @disableUseAnchorDate = 0 BEGIN SET @retValue = dbo.[ResourceContainer_GetProtectionInfoUsingAnchorDate](@ResourceContainerID) END ELSE BEGIN declare @ 09-04-2014,16:02:32 : dbutil RunSQLScript:Stop execution sql script 09-04-2014,16:02:32 : dbutil RunSQLScript: failed: 0x80040e14 09-04-2014,16:02:32 : OS ERROR: 0x80040e14 (-2147217900) 09-04-2014,16:02:32 : Starting schedule upgrades. 09-04-2014,16:02:32 : Not doing schedule upgrades due to previous errors. rc=0x1 09-04-2014,16:02:32 : Done with schedule upgrades. 09-04-2014,16:02:32 : upgrade135x ends rc=1 09-04-2014,16:02:32 : Job Migration Failed + 09-04-2014,16:02:32 : Failure 1 running migration library 1 09-04-2014,16:02:32 : Destructor BEMigrate Freeing library: C:\Program Files\Symantec\Backup Exec\Migration\pvlupgrade.dll 09-04-2014,16:02:32 : Destructor BEMigrate Freeing library: C:\Program Files\Symantec\Backup Exec\Migration\jobmigration.dll 09-04-2014,16:02:32 : Destructor BEMigrate Freeing library: C:\Program Files\Symantec\Backup Exec\Migration\catupgrade.dll 09-04-2014,16:02:32 : Destructor BEMigrate Freeing library: C:\Program Files\Symantec\Backup Exec\Migration\pvlupgrade.dll 09-04-2014,16:02:32 : Destructor BEMigrate Freeing library: C:\Program Files\Symantec\Backup Exec\Migration\postmigrationprocessing.dll + 09-04-2014,16:02:32 : BE Migration Tool execution failed 09-04-2014,16:02:32 : Migration returned value: 1 Did anybody have that kind of problem during migration? Any help would be appreciated. SoxSolved1.7KViews0likes8Comments