Installation BLM
Installation BLM
Installation BLM
Guide
Disclaimer
Information in this document is subject to change without notice and does not represent a
commitment on the part of ASIGRA Inc.
ASIGRA Inc. makes no representation or warranty, express, implied, or statutory, with respect to,
and assumes no responsibility for the accuracy, completeness, sufficiency or usefulness of the
information contained herein.
This document may contain sample screen shots, used to demonstrate Asigra Cloud Backup
procedures. All information appearing in this document is used for illustration purposes only, and it
should be considered fictitious.
Copyright
The software described in this document is furnished under a license agreement. It is against the
law to copy the software on any medium except as specifically allowed in the license agreement.
Asigra, the Asigra logo, Asigra Cloud Backup, Recovery is Everything, and Recovery License
Model are trademarks of Asigra Inc. All other brand and product names are, or may be
trademarks of their respective owners.
Asigra Inc.
All rights reserved. Confidential.
www.asigra.com
It is strongly recommended that you and the selected storage vendor perform input/output
performance tests on the target BLM Storage Location using the Asigra I/O Load Test
Tool and any other tools provided by the storage vendor. These tests can help you to
verify the speed and reliability of the selected storage, as well as to determine (from a
technical perspective) which hardware performs better in comparisons between storage
vendors.
I) Supported Platforms
For the official list of this products supported Operating Systems and versions, refer to the Installation
and Support Matrix. This can be found on the Installation DVD in the following path:
\Documentation\Release_Information
Windows Platform
Version
Windows 2012
x64 (64-bit)
UNIX Platform
Version
SUSE Linux
x64 (64-bit)
Windows 2008
x64 (64-bit)
2 CPU (Dual)
3 GHz or greater
RAM
4 GB RAM or more
Buffer (Staging)
Consolidated Archive
Software
Version
PostgreSQL Server
(For blm database)
If you are going to use a remote database, you must install it on a supported operating
system and make sure that the time zone is the same as the one on the BLM Archiver.
Read the instruction comments in the pg_hba.conf file, and refer to the PostgreSQL
Administrator's Guide.
Note: Make sure you remove the "#" sign (un-comment the line).
2. In <pg_data_path>/pg_hba.conf, replace all un-commented lines (ones that do not
start with #) with the following lines:
# TYPE
DATABASE
USER
CIDR-ADDRESS
METHOD
local
all
all
host
all
all
127.0.0.1/32
md5
host
all
all
<ip-address>/<CIDR-mask>
md5
md5
where:
If postgres is remote, you must switch to the BLM Archiver computer and
install the PostgreSQL Utilities, then type:
> psql -h <ip-address_of_postgres_server> -d template1 -U postgres
> \q
Read the instruction comments in the pg_hba.conf file, and refer to the PostgreSQL
Administrator's Guide.
2. Set a password for the database user postgres (The BLM Archiver must use this
username / password to connect to the PostgreSQL server):
> psql template1 postgres
> ALTER USER postgres PASSWORD '<enter_password_text_here>' ;
> \q
DATABASE
USER
local
all
all
host
all
all
CIDR-ADDRESS
METHOD
md5
127.0.0.1/32
md5
Note:
The user 'postgres' must also have ownership of the file pg_hba.conf, otherwise postgresql
will not start.
3. Restart the PostgreSQL service as root user with the following command:
#/etc/init.d/postgresql restart
IV.3.2b) To configure PostgreSQL on a remote computer (other than the BLM Archiver):
1. Switch to user postgres to perform the configurations using the command:
# su postgres
Note: Make sure you remove the "#" sign (un-comment the line).
Note 2: The user 'postgres' must also have ownership of the file postgres.conf, otherwise
postgresql will not start.
3. In <pg_data_path>/pg_hba.conf, replace all un-commented lines (ones that do not
start with #) with the following lines:
# TYPE
DATABASE
USER
CIDR-ADDRESS
METHOD
local
all
all
host
all
all
127.0.0.1/32
md5
host
all
all
<ip-address>/<CIDR-mask>
md5
md5
where:
If postgres is remote, you must switch to the BLM computer and install the
PostgreSQL Utilities, then type:
> psql -h <ip-address_of_postgres_server> -d template1 -U postgres
> \q
V) Before Installing
Make sure that:
1. The BLM computer meets the minimum hardware and software requirements.
2. The time on the target BLM computer is correct.
3. You have logged in as the target BLM computers Administrator (Windows) or root
user (Linux).
4. PostgreSQL is running.
2.
3.
4.
5.
6.
7.
[Option B] Run the Installation Center for Windows Products (setup.exe) located in
the root directory of the installation DVD.
The Installation Center is a common launcher for all Windows-platform
installations. It allows you to choose the specific installation package you
want, without the need to browse the installation DVD.
Choose the Setup Language:
English
German
A pre-requisite check is performed on the installation machine. This scans the
hardware and Operating System for compatibility (see II) Hardware & Software
Minimum Requirements on page 5).
Click "Next". The Welcome screen appears.
Click Next. The license agreement screen appears. You must accept the license
agreement to continue.
Click Next. The Choose Destination Location screen appears. The BLM Archiver files
will be installed to this directory.
Click Next. The Select Components to Install screen appears.
BLM GUI
BLM Archiver
Click Next. The Enter PostgreSQL database credentials screen appears.
Database Host: Enter the IP or hostname (use 127.0.0.1 if the database is
running on the local computer).
User name: Enter the PostgreSQL database username.
User password: Enter the PostgreSQL database password.
Note:
If the BLM database does not exist, a pop up message appears asking you if you want
setup to create the BLM database. Click Yes.
If the BLM database does not exist, a pop up message appears asking you if you want
setup to create the BLM database. Click Yes.
Note: Check the Open-Files Limit for the BLM daemon and the Linux kernel
The system administrator should check that the parameters for open file limits match the expected
load on the BLM service. If you find errors in the BLM Event Log like "Too many open files...", you
must increase one or both of these parameters:
1. The local limit that applies to the BLM daemon is found in the following line in the BLM
startup script ("/etc/init.d/blmdaemon"):
ulimit -n NUMBER
2. The parameter for the global maximum number of open files available in the system is
found in the Linux kernel. You should set "fs.file-max" in the "/etc/sysctl.conf" file and
then run "sysctl -p" from a root shell. Consult your Linux kernel documentation for
more information.
If connection is successful, check the BLM Archiver Event Log for errors.
If a Graphical Interface is not installed on this UNIX Operating System, the BLM
Archiver GUI cannot be run locally. Instead, the BLM Archiver GUI can be run from a
remote machine to connect to this BLM Archiver daemon.
Depending on your selections, some different screens will appear. These differences are noted
below.
1. Make sure:
You have logged on as user root
Database is running (postgreSQL)
If you are upgrading an existing BLM Archiver Installation, you should backup
the existing BLM Archiver database. For postgreSQL, use the command:
# pg_dump -U postgres blm > /<installation_path>/blm.dmp
2. Run the installation program from the corresponding folder on the installation DVD:
For Linux, the folder is:
/Software/BLM_Archiver/Linux_64_bit/blm_setup_linux.bin
11. To specify a different destination folder, type a valid path on the local computer and
press Enter.
12. A confirmation command line appears. Press [1] and Enter to continue.
BLM Archiver Installation Guide
v13 [Revision Date: January 30, 2015]
Asigra Inc. All Rights Reserved.
Summary
In order to migrate an existing BLM Archiver that is running on a physical server to a Virtual
Machine, follow these general upgrade steps:
Prepare a Virtual Machine (VM) with the same Operating System (or an
Operating System from the same family) as you are currently running on your
physical BLM Archiver machine. Ensure that the Operating System installed
is listed as supported in the Installation and Backup & Restore Support
Matrix document.
Shutdown the BLM Archiver service / daemon on the physical machine.
WARNING: Service downtime will begin at this moment.
Ensure that the BLM Archiver database is accessible from the remote VM and
the online storage is accessible from the remote VM with the same Staging
Buffer path(s) and Consolidated Storage path(s) used by the physical
machine. (If you need to perform a database migration or storage migration
as well, please contact Asigras Technical Support department.)
Install the BLM Archiver software, point to the old production database and
storage location.
On the DS-License Server, configure the IP address and license parameters
of the new VM BLM Archiver.
Start the BLM Archiver and immediately configure the DS-License Servers IP
where the new BLM Archiver installation on VM will validate its license (BLM
GUI > Setup Menu > License Server).
The information provided in this document is provided "AS IS", without warranty of any kind. ASIGRA Inc. (ASIGRA) disclaims all warranties, either express or implied. In no
event shall ASIGRA or its business partners be liable for any damages whatsoever, including direct, indirect, incidental, consequential, loss of business profits or special
damages, even if ASIGRA or its business partners have been advised of the possibility of such damages. Asigra Inc. All Rights Reserved. Confidential.