Monitoring, Management & Location Tracking

How to check the version of Airwave from the backup file, without restoring it.

MVP
MVP
Requirement:

We have a Airwave backup file. However, not sure of the version it belongs.

We will need a Airwave server or any Linux server, with its CLI access and ability to copy files using scp or ftp.



Solution:

We will need to copy the said file in question to /tmp or any location of a Linux or a Airwave server and execute a tar command specifying the file location "AMP-upgrade-version-history.log". This file on the backup contains the current version and also the past upgrade history.



Configuration:

once the file is copied, we will need to run the below command:

# tar xvf <backup file name> var/log/upgrade/AMP-upgrade-version-history.log

This command will only extract the file "AMP-upgrade-version-history.log" from /var/log/upgrade/, it will create a directory called "var" in the same location, from where we executed the command. 

 

For example:

I am in /tmp directory of my lab server, as shown below:

[root@localhost tmp]# pwd
/tmp

[root@localhost tmp]# ls -l
total 264884
-rw-r--r--  1 root     root          24 May 21 04:27 amp-backup-version
drwxr-xr-x  2 root     root        4096 May 17 04:13 hsperfdata_root/
drwxrwxr-x  3 visualrf apache      4096 May 17 04:13 java/
-rw-r--r--  1 root     root        1488 May 17 03:39 maketee.txt
-rw-r--r--  1 root     root        1488 May 17 03:38 make.txt
-rw-r-----  1 root     root   271209720 May 21 10:05 nightly_data001.tar.gz
drwxr-xr-x. 3 root     root        4096 Oct 13  2016 svn_old/
drwx------  3 root     root        4096 Jan 23 19:24 tmp19w3cw/
 

[root@localhost tmp]# tar xvf nightly_data001.tar.gz var/log/upgrade/AMP-upgrade-version-history.log
var/log/upgrade/AMP-upgrade-version-history.log
[root@localhost tmp]#
 

As expected the above command has created the directory  "var/" in /tmp as shown below:

[root@localhost tmp]# ls -l
total 264888
-rw-r--r--  1 root     root          24 May 21 04:27 amp-backup-version
drwxr-xr-x  2 root     root        4096 May 17 04:13 hsperfdata_root/
drwxrwxr-x  3 visualrf apache      4096 May 17 04:13 java/
-rw-r--r--  1 root     root        1488 May 17 03:39 maketee.txt
-rw-r--r--  1 root     root        1488 May 17 03:38 make.txt
-rw-r-----  1 root     root   271209720 May 21 10:05 nightly_data001.tar.gz
drwxr-xr-x. 3 root     root        4096 Oct 13  2016 svn_old/
drwx------  3 root     root        4096 Jan 23 19:24 tmp19w3cw/
drwxr-xr-x  3 root     root        4096 May 21 10:08 var/
 



Verification

We could open the file by either cat or less to see the version as shown below:

[root@localhost tmp]# cat var/log/upgrade/AMP-upgrade-version-history.log
Thu Jul 21 11:31:24 BST 2016 From: 8.2.0.2 To: 8.2.1.1 - Upgrade successful.
Thu Oct 13 22:53:31 IST 2016 From: 8.2.1.1 To: 8.2.2.1 - Starting upgrade.
Thu Oct 13 23:04:19 IST 2016 From: 8.2.1.1 To: 8.2.2.1 - Upgrade successful.
 

by the above output, we could understand that the last upgrade done on this backup was to 8.2.2.1. Therefore the backup version is 8.2.2.1.

 

Version history
Revision #:
2 of 2
Last update:
‎06-07-2019 06:49 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: