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.
B2D 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..Upgrade 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.Upgrade 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.)? ThanksInstalling 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.
