https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMTkxIiwiaGFzaCI6ImExZDdmMDQzLWQ2ZGItNGFjYy04MzQ0LWUxOGJiMmY2ODBmMSJ9
Release Information for Veeam Agent for Oracle Solaris 2.0
| KB ID: | 3191 |
| Product: | Veeam Agent for Oracle Solaris 2.0 |
| Published: | 2020-06-04 |
| Last Modified: | 2020-11-13 |
Requirements
Upgrade from v1 is not supported, clean installation is required.
Upgrade from Veeam Agent for Solaris 2.0 RTM (build 2.0.0.123) is possible.
Please confirm that you are running version 2.0.0.123 or later prior to upgrading. You can check this using veeamconfig --version in Oracle Solaris command-line interface. After upgrading, your build number will be 2.0.0.126.
Please confirm that you are running version 2.0.0.123 or later prior to upgrading. You can check this using veeamconfig --version in Oracle Solaris command-line interface. After upgrading, your build number will be 2.0.0.126.
Solution
Please refer to What’s New and Release Notes documents for the detailed information about this release.
Be sure to review before the upgrade Known Issues and System Requirements sections of the Release Notes document closely.
Be sure to review before the upgrade Known Issues and System Requirements sections of the Release Notes document closely.
More information
This update has been superseded by Veeam Agent for Oracle Solaris 2.1.
| KB ID: | 3191 |
| Product: | Veeam Agent for Oracle Solaris 2.0 |
| Published: | 2020-06-04 |
| Last Modified: | 2020-11-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
