Follow the procedure below to restore an unsuccessfully-upgraded system to its previous state. This approach only has value in upgrade scenarios where it's desired to use the earlier version of NetBackup that was originally present on the host. If the error is not fully understood or overly complex, the preferred path may be to restore the system to its previous state. The NetBackup installers are safe to re-run in environments where previous installation/upgrade attempts failed.ī) manually restore the system to its previous state (if the installers couldn't do it automatically) If the error is of a simple nature, such as insufficient disk space, the simplest path is to address the error condition and then retry installation/upgrade. Once the error is known, there are two high-level approaches:Ī) address the conditions responsible for the error and retry If not, the exact error may require manual steps to resolve. If so, NetBackup should be running and in position to perform backups and restores at the original release level. The install logs will report if the attempt to restore the earlier system state is successful. Did the installers recover and successfully restore my system to its earlier state? The most frequently-encountered errors may have associated Veritas support articles. Take note of which of the MSI packages encountered the error. Search in logs for the phrase "value 3" as a starting point. Following an unsuccessful installation or upgrade, review the latest logs produced in this folder. Where can I find more information about the error?Īll NetBackup MSI-based packages produce logs at %ALLUSERSPROFILE%\Veritas\NetBackup\InstallLogs. SolutionĬonsider the following information should a fatal error occur during installation or upgrade of NetBackup Server. The custom logic involves executing uninstallations and repair operations depending on 1) whether NetBackup was being upgraded or being installed for the first time and 2) the specific point in the overall installation sequence that the fatal error occurred. The NetBackup installers include custom logic to account for this. Because multiple MSIs are now involved, a single MSI's rollback is not guaranteed to restore the original system state. The packages are installed in that order. Windows only performs rollback for the MSI package that is actively being installed at the time of the fatal error changes to related or dependent products are not handled automatically by Windows.īeginning in NetBackup 8.3, NetBackup Server for Windows conditionally installs multiple MSI packages: Veritas NetBackup JRE, Veritas NetBackup Java GUI, and Veritas NetBackup. The purpose of rollback is to attempt to restore the system to its previous state should a fatal error occur during installation or upgrade. In some cases, manual steps may be required to restore the system to its previous state. But, environmental factors can influence the installation process in unforeseen and unexpected ways. Veritas works to minimize and protect against installation failure conditions, and the NetBackup installers attempt to recover automatically from fatal errors. Fatal errors can occur when installing or upgrading NetBackup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |