Step 1: Save a copy of your BART 2.1/2.2 configuration file as a backup. The default location and file name is /usr/edb/bart/etc/bart.cfg directory.Step 2: Assume the identity of the BART user account and invoke the following command to stop the BART 2.1/2.2 WAL scanner program, bart-scanner, before upgrading to BART 2.3.Step 3: As the root user, upgrade to BART 2.3 with the yum upgrade command.
• If you have an existing BART RPM installation, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the edb.repo file, assume superuser privileges and enter:yum will update the edb.repo file to enable access to the current EDB repository, configured to connect with the credentials specified in your edb.repo file. Then, you can use yum to upgrade any installed packages:
• The following syntax uses the yum command to update to the BART RPM package file that has been downloaded to the current working directory. The local package file is installed by using the complete, RPM package file name:yum upgrade edb-bart-2.3.x-x.rhel7.x86_64.rpmMarking /home/edb/Desktop/edb-bart-2.3.0-1.rhel7.x86_64.rpm as an update to edb-bart-2.2.0-1.rhel7.x86_64==========================================================================================================================================================================================================================================================================================================================================================================================================================================================================================Step 4: The BART 2.1 files in the parent /usr/edb/bart directory are replaced by the BART 2.3 files. Check if the BART configuration file bart.cfg found in the /usr/edb/bart/etc directory is your original file used with BART 2.2/2.1. If it is not present, then you can use the configuration file saved in Step 1.Ensure the backup_path parameter of the BART 2.3 configuration file is set to a new directory and not to any existing BART 2.2/2.1 backup catalog. In other words, new full backups and incremental backups taken using BART 2.3 must be stored in a new BART backup catalog.
• If you are installing BART 2.3 on a remote host on which incremental backups are to be restored, (in other words, this is not the BART host), then the content of the BART 2.3 etc subdirectory does not need the addition of the bart.cfg file.Step 5: Check the setting of the PATH environment variable includes the directory location of the BART 2.3 bin subdirectory in the ~/.bashrc or ~/.bash_profile files of the following user accounts:
• The BART user account on the BART host. See Section 4.1, Step 3 for information.
• Note: The PATH setting should be the same as set for BART 2.2/2.1 since both versions use /usr/edb/bart/bin.Step 6: Repeat the installation process described in this section to upgrade to BART 2.3 on all remote hosts where incremental backups are to be restored using BART 2.3. See Section 220.127.116.11 for additional information on restoration of incremental backups on remote hosts.After upgrading to BART 2.3, you must take a new full backup of your system before performing an incremental backup.BART 2.3 cannot be used to perform incremental backups from parent full backups or parent incremental backups that were taken using any of the older BART versions than 2.3. Taking incremental backups using BART 2.3 is possible only from parent full backups and parent incremental backups that were taken using BART 2.3.