Infoscale Enterprise Upgrade
Hello Team, We have an Infoscale cluster hosted Veritas Enterprise Vault. This cluster consists of two nodes in the main site and one node in the DR site, configured with VVR replication. We are planning to upgrade IS from version 7.4.2 to 8.0.2. What is the best approach to minimize downtime during the upgrade process? Option 1: Stop replication, upgrade all nodes simultaneously, and then restart replication. Option 2: Upgrade the DR node first (without stopping services or replication from the HQ), fail over to the DR site, and then upgrade the HQ nodes. Option 3: Upgrade the DR node first (without stopping services or replication from the HQ), stop replication, and then upgrade the HQ nodes. Thank you.
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.
First time upgrading - checking my steps
Hi All Looking to do my first EV upgrade, normally this has been actioned by another colleague who has since retired. Currently we're on EV 12.1.2 and looking to go to 12.5.3. Our environment is: 4x Win2012 servers (2 x storage/task servers and 2 x indexing servers), SQL 2012 server, Storage is handled by CIF shares. We're currently running onprem Exchange 2016 servers. We don't use EV reporting, discovery or any smtp/journal archiving Pre-change: Confirm backups of application servers and SQL Confirm AV off Confirm disk space Run deployment scanner check Get new clients packaged ready to deploy Change Day: Stop all EV services and set to manual Check all MSMQ are empty Copy and backup EV folder for webapp.ini and web.config files Upgrade all 4 servers but DO NOT reboot until all are done Run cmdlet Start-EVDatabaseUpgrade to upgrade SQL db 12.5.3 install on all 4 servers a) have I got the above steps correct? b) my previous colleague would also put the Vault Stores in Backup mode, is this necessary since I'm stopping the EV services and changing them to Manual startup for the duration? c) he also noted something about Check Statistics have been dropped on Vault SQL Databases, what is this? d) Do I need to upgrade OWA extensions on each Exchange server as well? e) the client app deployment is handled by another team, does it matter if the server is 12.5.3 but the client is 12.1.2 for a short duration? f) any other step I'm missing? Thanks in advance.
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 article 100020224 "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 the Ext 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.