I can't find topis on this forum so I created one.
Who is so brave and upgarded to 20.1 ? not in test environment but on production?
I have mixed virtual and phisical servers and I want to be sure that after upgrade I will stay on this version without downgrade...
Do we need to wait for the first hotfix?
Another user's experience will not be relevant to you. He may have problems with a particular release, but you may not. Conversely, he may have no problems with it, but you do. Each environment is different. You should do your own testingth satisfy yourself that it is suitable for your environment.
Just tried to upgrade from V-Ray 16 to 20.1, just to find that Deduplication is no longer included with my upgraded license...
Doesn't even install without forcing me to remove dedup from my install, losing all my historical backups.
It seems like Veritas is not honoring the features I pay for.
Hoping this is just a technical bug.
If its a VM, take a snapshot of the VM before the upgrade else preserve the Data and Catalog folder from BE 16 if you ever have to go back to earlier configuration. Since dedupe version is changing (DD7 to DD10), and it will make changes to the storage, it is recommended to backup the storage on a Tape or secondary location (recommended way to backup dedupe folder is from under the BE server -> select dedupe storage from Shadow Copy Component). Dedupe storage will need to be restored if you need to go back to version of dedupe which came in BE 16. The upgrade instructions mention it.
I would wait, I have installed it into a production SCCM environment. I am unable to click on veritas update without it hanging. I am also having problems with SDR, receiving an error that a newer version of the Windows Assessment and Deplyoment kit is already installed on the computer.
I recommend waiting also. After upgrading only a couple sites, I've come across multiuple issues including being unable to edit jobs that point to the upgraded dedup storage and backups of hyper-v servers are failing everywhere. Even on new installs of BE 20, Hyper-V backups fail to verify with a vhdx corrupt error yet restores from those failed jobs work fine.
I am excited about many new features however. Most notably is the multi-core Dedup agent.
We have seperate BE servers installed. I've found one to "test" 20.1 on and it has been an absolute nightmare so far. It doesn't recognize the OST devices and had to add after the fact. Backup jobs are not completing and are hanging at queued. I think I've had around 4 hours of support on the phone so far. I'm not so certain this version has been tested well.
I was trying to send a private message when I saw that you tagged HP Storeonce. Is that the OST appliance which you are using Philipv ? if yes was it was seen that the Issue about slowness started post upgrading the plugin from version 2 to 4 or you havnted tested with plugin version 2 ? all cases that have come to support have been for HPE storeonce and not for any other storage vendor. Having said that as a part of the Issue documented here https://www.veritas.com/support/en_US/article.100041761 BE engineering has a fix (not available outside for now) which has tuning for all the OST vendors that BE supports and this has also helped with HPE Storeonce. If you are interested then you can email. https://vox.veritas.com/t5/CPEP-List-of-Interactions/CEP-4396-Backup-Exec-20-2-BETA/td-p/850623
I stopped installing v20 after the second customer due to the issues. They are both Techsoup non-profit customers so I don't believe they are elegible for support. They are small organizations, simple to wipe and start over. I'll eventually get to the larger clients with support contracts. I disabled the torpedo interface, we'll see how it goes. I also noticed a hotfix for the inability to update backup jobs to dedup storage after the upgrade, grats on that one, it was a show stopper.