Backing up value add metadata

It is critical to back up your Big SQL and DSM metadata before performing a migration.

Before you begin

The following are prerequisites for backing up your meta data:

You must disable Big SQL high availability.
Ambari configuration groups are not supported. The upgrade script produces a warning message if you use configuration groups. If you override the warning, you must validate that the configuration of all nodes in all configuration groups is updated as part of the upgrade. It is recommended that you remove all configuration groups.
You must disable Yarn and Slider support for Big SQL.

About this task

Provides information on how to back up:

Data Service Manager (DSM) metadata
Big SQL metadata using the Big SQL python script bigsql_upgrade.py

Procedure

Install the Big SQL version 5.0.1 service definition:
1. Obtain the IBM Big SQL package . See Obtaining IBM Big SQL for details.
2. Execute the downloaded file; choose the migration option when asked. See Installing the IBM Big SQL package for details.
3. After the downloaded file has been executed, DO NOT enable the Big SQL 5.0.1 extension with the EnableBigSQLExtension.py script.
Back up the Ambari Server database.
Run the backup option of the Big SQL python script on the Ambari server node. (For details on the script, see bigsql_upgrade.py - Big SQL upgrade utility.)
1. The binaries of the new version of service Big SQL will be installed from a yum repository. If you want to check the URL, open /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml and locate the following code:
```
<repo>
  <baseurl>http://<local repo server fully qualified domain name>/repos/bigsql</baseurl>
  <repoid>IBM-Big_SQL-5_0_1_0</repoid>
  <reponame>IBM-Big_SQL-5_0_1_0</reponame>
  </repo>
```
  If needed, change the repository URL.
2. Back up your Big SQL environment by running the Backup option of the bigsql_upgrade.py python command. The Backup option performs the following actions on all nodes of the cluster:
  - Backs up the Big SQL catalog, metadata and configuration information
  - Installs the binaries for the new version
  - Temporarily disconnects the Big SQL service definition from Ambari
  To perform the backup phase of the upgrade, run the bigsql_upgrade.py script with the -m option and the value Backup. Include any additional options as documented in the bigsql_upgrade.py - Big SQL upgrade utility. For example, if you have configured Ambari for non-root access, you should use the -a option.
```
python /usr/ibmpacks/scripts/5.0.1.0/upgrade/bigsql_upgrade.py -m Backup
```
3. When the Backup phase is complete, the Big SQL service is no longer visible in the Ambari dashboard. However, it is operational, but not running. If needed, you can start the service from the command line and use it. In this case, the version executed is the initial Big SQL version.
(Optional in case the backup phase fails) Consult the master log output or the upgrade log located at /var/ibm/bigsql/logs/upgrade.log to identify and resolve the problem. After it is resolved, re-run the backup phase.
Backup DSM metadata. Save a copy of the following items from the DSM_Master node to a backup directory, such as /tmp:
- /usr/ibmpacks/IBM-DSM/$VERSION/ibm-datasrvrmgr/Config/default_rep_db
- /usr/ibmpacks/IBM-DSM/$VERSION/ibm-datasrvrmgr/Config/privileges.json
For example:
```
mkdir /tmp/dsm; cd /tmp/dsm
cp -rf /usr/ibmpacks/IBM-DSM/$VERSION/ibm-datasrvrmgr/Config/default_rep_db .
cp /usr/ibmpacks/IBM-DSM/$VERSION/ibm-datasrvrmgr/Config/privileges.json .
```

What to do next

The next step in the migration process is to back up the open source services. See Backing up open source services for details.