Note: Your Data Connector must be running software version 1.1.0 or later to support installing future upgrades and hotfixes.

Depending on your deployment requirements, you can install the upgrade package using one of the following methods:

• In-place Upgrade: Upgrading the existing Legacy Data Connector by uploading a new software package to replace the existing software.
• External Upgrade: Deploy a new Legacy Data Connector, install the latest .OVA package file on the new Data Connector, back up the configuration file from the old Data Connector, shut down the old Data Connector, and then move the configuration file over to the new Data Connector.

For more information, see the section, Installing the Upgrade Package on this page. 

Upgrade Prerequisites

Ensure that you have completed the following before upgrading:

• Contact your Infoblox representative about how to obtain the upgrade software package.
• Ensure that you have properly set up and configure an external server to which you upload the upgrade package. The Legacy Data Connector supports SCP and FTP servers.
• Check the connection between the Legacy Data Connector and the external server to which you plan to upload the upgrade package.
• Ensure that the connection between the Legacy Data Connector and the destination server (Infoblox reporting server and Infoblox cloud destination) is up and running.

Installing the Upgrade Package

Follow these procedures to install the software upgrade package on the Infoblox Legacy Data Connector:

1. Upload the upgrade packet to an external SCP or FTP server.
2. Log in to the Legacy Data Connector CLI.
3. Download the upgrade package from the external server using the admin.system.upgrade > load CLI command.

Example:

admin.system.upgrade > load <scp|ftp>://loginname@serverIP:[port:]path

where path is the <path of the upgrade package>

Note: This operation might take a longer time depending on network conditions.

Enter password:

Received upgrade package. Validating...

Upgrade package is ready

ok 

Note: <path of the upgrade package> is the absolute path to the file on the server. 

4. Before you upgrade, you can check the current status of the upgrade package using the admin.system.upgrade > status CLI command:
Example:

admin.system.upgrade > status
System version: 1.1.0-123456
Upgrade version: 2.0.0-348708
Upgrade package: DataConnector_2.0.0-123456_2016-04-13-12-01-01_x86_64.upg
No upgrade or revert operation is running
ok

5. Obtain a manual backup of the existing configuration file on the Legacy Data Connector and export it to an external server of your choice, as follows:

admin.support > backup [scp|ftp]:// <log in name> @ <server IP> / <path of the backup>

Note: If you are performing an external upgrade, you must restore this backup file on the new Legacy Data Connector. For an in-place upgrade however, backing up the configuration file is a best practice. 

Example:

admin.system > backup scp://jdoe@10.0.1.1/DataCollector-7.3/backup-restore
Enter password:
Backup file dc_backup_dc-xyz_dc-xyz.com_20170324090152.tgz is created.
Uploaded backup to jdoe@10.0.1.1
ok

The backup file is created in this format: dc_backup_dc-infoblox yyyymmddhhmmss.tgz

6. Optionally, use the data.destination > stats CLI command to view pipeline statistics and the number of output files in queue waiting to be transferred to the destination server (such as the Infoblox reporting or Infoblox cloud server). If there are a lot of output files, the Legacy Data Connector might not be able to transfer all the data to the destination servers before the configured timeout period. In this case, you can decide whether to terminate the upgrade when the timeout period expires or continue with the upgrade. If you select to continue with the upgrade, the Legacy Data Connector proceeds to transfer the remaining output files to the destination server after the upgrade is complete. If desired, you can also force an upgrade on the Legacy Data Connector after the timeout period. However, be aware that data loss might happen if there are still output files waiting to be transferred when you force an upgrade after the timeout period expires.

Note: A large number of output files in queue, could be an indication that the Infoblox reporting or Infoblox cloud server is busy or the connection is down. Check the connections between the Legacy Data Connector and these servers to ensure that the connections are up and running.

Example: data.destination > stats

Cloud output stats: 

Reporting output stats: 

7. Apply the uploaded upgrade package and perform the upgrade using the following CLI command:

admin.system.upgrade > apply [timeout] [force]
where

timeout is the number of seconds the system waits for the output files in the Splunk forwarder and dc_cloud_out containers to be transferred to the corresponding destination servers before starting an upgrade. The default is 600 seconds. Note that if there are still output files in queue on the Legacy Data Connector when the timeout expires, the upgrade will terminate. However, if you choose to continue with the upgrade, Legacy Data Connector disables the data input so there is no new data being collected. After the upgrade is complete, Legacy Data Connector resumes the data transfer for the output files that are remained in the containers.
force is used to perform a force upgrade when necessary.

Example:
admin.system.upgrade > apply 300
Upgrading from version 1.1.0-cloud-xxxxxx to version 2.0.0-xxxxxx

Wait up to 300 sec. to forward all files
Upgrade will be cancelled after wait time is expired if data are not completely forwarded.

Proceed with upgrade? (y/n): y

27% complete Data forwarding

8. To verify that the upgrade package has been installed successfully, use the admin.system.upgrade > status command to check the system versions.

Example:

admin.system.upgrade > status

System version: 2.0.0-348708
Revert version: 1.1.0-123456
No upgrade or revert operation is running

ok

9. This step applies only to an external upgrade in which you have configured a new Data Connector and need to move the configuration file from the old Data Connector to the new one. For an in-place upgrade, this step is not necessary because the restoration of the configuration file is automatically performed during the upgrade.

After you have successfully installed the upgrade package on the new Data Connector, use the admin.system > restore commands to restore the configuration file you obtained earlier from the previous version of Data Connector.
Example:

admin.system > restore scp://jdoe@10.0.0.10:/
DataConnector-7.3/backup-restore/dc-backup-20160411173718.tgz
Enter password:
Received backup package from jdoe@10.0.1.1.:
admin.system > restore
The following backup file(s) in the system:
dc-backup-20160411173718.tgz
dc-backup-20160322303030.tgz
dc-backup-20160211101010.tgz
admin.system > set restore dc-backup-20160411173718.tgz
File dc-backup-20160411173718.tgz is restored
ok

Note: After upgrading the Legacy Data Connector to version 3.0.0, you must manually reconfigure the Legacy Data Connector and register the Legacy Data Connector with the NIOS Grid. For more information, see Configuring and Registering the Legacy Data Connector Virtual Appliance.