Backup Exec 20.3 Ala Carte License Update to Simple Licensing Backup Exec
Hello Experts, First of all, I am going to give you brief information related to my scenario. I have Backup Exec 20.3 on windows supporting 5 windows server with Ala Carte License. I want to buy Simple License Core Pack to change my Existing "Ala Carte license". My problem is, The current Backup Exec Server version is only 20.3 and the Backup Exec Simple License is featured on Backup Exec 22.2 My Plan is to Install new Backup Exec Server with Version 22.2 and activate the Simple License Core Pack then restore the Catalog of the old Backup Exec . Is this Possible? Hoping to receive clarification or different approach for this matter Thanks you in Advance.
DataDomain To StoreOnce Migration
Hello, I'm a new guy in my organization and was tasked to migrate our current NetBackup (7.7.3) storage system from Dell DataDomain to a new one, HPE StoreOnce 5260. I've searched for relevant information on Google but haven't had any success. Would you be able to supply any knowledge base articles, or a detailed guide for this process? From what I understand, StoreOnce offers a plugin for Veritas. Should I install this plugin initially, or is it necessary for the migration and operation at all? Thanks for your assistance.
NB Master Server migration to the new HW
Hello, I would like to migrate my current NB Master Server 10.1.1 running on Windows 2012 R2 (VMware) to the brand new server running on Windows 2022 (VMware), whole env. includes over 20 Dell DataDomains as target storages and over 20 Media Servers. Are there any general recommendations? Do you have any experience with similar migration? I found following migration toolhttps://www.veritas.com/content/support/en_US/downloads/update.UPD162444but I could not find any real cases how it works and so on. Other way how to do it would be catalog recovery but that would take too much time which I cannot afford at the moment. Or does it make a sense to build a new NB Master Server, do the re-configuration there of the storages, Media servers, policies etc. and leaving the old NB Master Server running behind till the backed-up data reach expiration point? Or is there any way how to export the configurations? How does it work with the certificates? Is it possible to have same token on both old and new NB Master Servers? Thank you. T.
Server Settings Migration Wizard 14.0
New version of Server Settings Migration Wizard (SSMW) is now available. The latest versions supports: Migration from 12.x to 12.5 Migration from 12.x to 14.0 Migration from Win 2012/2016 to Win 2019 For more information refer to the below links https://www.veritas.com/content/support/en_US/downloads/update.UPD397880 https://esd.veritas.com/378349/Veritas_Product_Files/EV/EV_Migrating_Using_Server_Settings_Wizard.pdf?authparam=1608196826_0c3a4c5cf52c11b085fa4ae5d7a2bdd4 Regards Amol
Enterprise Vault Database Migration from MS SQL 2012 Standalone to MS SQL 2016 AlwaysOn
Dear Experts, We are planning to move Enterprise Vault 12.3 Database from MS SQL 2012 R2 SP3 standalone to MS SQL 2016 AlwaysOn. Also AlwaysOn listener will use the custom port 49540. Below is the setup and steps I am considering to migrate the database. Appreciate if you can review the steps and give your expert advise if anything I need to consider during the migration process. Current Setup: Enterprise Vault 12.3 running on Two Node Veritas Cluster on Windows 2012 R2 Discovery Accelerator stanadlone server configured. Steps I am considering to migrate: 1) Stop all EV Services on all Servers 2) Change the Database Instance name using SetEVDatabase 3) Detach EV Database from SQL 2012 and Attach EV Database in SQL 2016 4) Backup the Database and Configure AAG with Listener with 49540 Port 5) Wait for complete sync to happen 6) Change EV Registry Entry for Directory Service (Kindly suggest if I need to mention the Port Number in registry. E.g. AAG_LISTENER_NAME,49540 OR or AAG_LISTENER_NAME Should be fine) 7) Change FingePrint Database Entry using SQL Query (Suggest whether I need to use AAG_Listener,Port_Number OR just AAG_Listener is fine) 8) Start EV Directory Service & Admin Service, Change the Vault Store Group Database entries (suggest whether I neeed to specify the Server with port name as mentioned in previous steps?) 9) Start All remaining Services 10) Wait for completely startup 11) Modify the EV Monitoring Database (Suggest need to specify portnumber along with AAG-Listener_name 12) Test Search and Archives 13) Modify the Config File for DA Server (Suppose I need to modify Server Name with Port number in config files? Suggestions please) 14) Start EVAMS 15) Login to EVDAAdmin portal, reflect change for EV DA database with appropriate portnumber AAG_LIS_Name,PortNumber 16) Retstart EVAMS Really appreciate your feedback and suggestions. Thanks,
