Académique Documents
Professionnel Documents
Culture Documents
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.
5
5
5
5
14
14
14
14
15
The Asigra Cloud Backup DS-NOC (Network Operation Control) is a J2EE (Java) application
that allows access to DS-Systems, BLM Archivers, DS-License Servers and DS-Billing Systems
through a Web-based interface.
DS-NOC is designed for three types of users: Service Providers, Sales Groups (and their Sales
Representatives), and End Users (of the Cloud Backup service).
Service Providers can:
use this Web site to manage and monitor all Asigra Cloud Backup products:
DS-System, DS-Billing, BLM Archiver, DS-License and DS-Client
configure DS-NOC, create and manage DS-NOC (Web site) users and
permissions
create Accounts / DS-Clients on DS-System
view DS-System / BLM / DS-Billing / DS-Client reports and logs
perform specific tasks on BLM Archiver
monitor DS-License Server / DS-System / BLM / DS-Billing / DS-Client, etc.
Sales Groups can:
use this Web site to manage and monitor DS-System Accounts / DS-Clients
belonging to their customers
create, manage, and monitor their Customer Account / DS-Clients
create a Subscription ID for their Sales Representatives
view reports, etc.
End Users can:
use this Web site to create new DS-Clients
download DS-Client Installation Packages and any other software provided by
the Service Provider
login to DS-NOC and view their DS-Client status, view reports, and request
and download Restorable Images from BLM
restore data via a web interface
This document contains instructions about installing the Asigra Cloud Backup DS-NOC. It
contains brief instructions about installing third-party software that is needed by the DS-NOC and it
contains detailed instructions about how to configure the DS-NOC.
The installation instructions for third-party products is brief and this document is not intended to be
a complete installation guide for these products. For additional information about installing the
third-party applications, please consult the installation manuals for these applications.
Version
PostgreSQL
1.7, 1.8
For the official list of this products supported Databases
and versions, refer to the Installation and Support Matrix.
9.1 (upgrade existing installations only)
9.2 (new windows and upgrade linux installations)
9.3 (new linux installations)
CPU
> 3 GHz
RAM
> 2 GB RAM
> 2 GB
Version
Windows 2012
x64 (64-bit)
UNIX Platform
Version
Standard / R2 (x64)
Datacenter / R2 (x64)
Make sure Microsoft IIS Server is not running, and that you are not running any other Web
Servers that are listening on port 80 of the DS-NOC machine.
3. Click Next. Change "HTTP 1.1 Connector Port" to 80 (the default is 8080). Select a
password for the admin user name and make sure it is assigned to the manager-gui
role.
4. Click Next. Select the path to the Java JRE which you installed in step 2.1.
When you reach this screen, enter the path to the Java JRE which you
installed in step 2.1.
The current noc.war file is larger than the maximum default upload size supported by
Tomcat. Therefore, before deploying the WAR file, you must perform the Tomcat
configurations described in the Knowledge Base article TROUBLESHOOTING:
Uploading WAR files larger than 50 MB on page 17.
2. Scroll down in the management window until you reach "WAR file to deploy". Click
"Browse" and select the "noc.war" archive. Now click "Deploy".
Connecting from a
remote computer
<IP_of_DS-NOC_computer>/noc/.
Make sure that you are not running any other Web Servers that are listening on port 80 of
the DS-NOC machine.
3. Follow the instructions that come with the Apache Tomcat installation.
4. Point the JAVA_HOME environment variable to a JRE v.1.7 (or higher) that is running
on the DS-NOC machine (i.e. the one you installed in step III.1 Installing Java JRE
1.7 (64-bit) on page 14).
Note: You can also point the JRE_HOME environment variable to a JDK v.1.7 (or higher) that is
running on the DS-NOC machine.
5. Start Apache Tomcat by running the following command that can be found in the
$CATALINA_HOME/bin directory:
startup.sh
8. To create a username and password, edit the tomcat_users.xml file that is found in
$CATALINA_HOME/conf. Add the following lines:
<role rolename=admin-gui / >
<user username=admin password=admin roles=admin-gui / >
<role rolename=manager-gui / >
<user username=admin password=admin roles=manager-gui / >
Note: Make sure you un-comment the Roles section in the tomcat_users.xml file.
9. Restart Tomcat with the following commands:
./shutdown.sh
./startup.sh
10. Open a Web Browser and access Tomcat by typing "http://localhost/" or http://
<IP_of_DS-NOC_computer>/ in the Web Browsers address bar.
11. Open Manager App. It will ask you for a username and password.
Use the one created in step 8 above.
php5-soap-5.2.14-0.7.24.1.x86_64.rpm
php5-soap-5.3.17-0.13.7.x86_64.rpm
php-soap-5.3.3-22.el6.x86_64.rpm
php5-soap-5.5.3-26.el6.x86_64.rpm
Summary
The default deployment of DS-NOC (with the noc.war archive file) will create a DS-NOC that is
accessible through the following context:
http://localhost/noc
or for remote machines: http://<IP_of_DS-NOC_computer>/noc/
However, the DS-NOC can be deployed in multiple contexts, allowing you to create separate DSNOC portals for use with specific customers.
Details
To deploy DS-NOC in a different context:
1. Make a copy of the noc.war archive file and rename it to the context you want to use.
For example: Use the context newsite, that can be accessed through the
address http://localhost/newsite (or http://<IP_of_DS-NOC_computer>/
newsite)
2. Follow the same steps to deploy the renamed file (newsite.war) on the Web Server.
3. Connect to the application via the new context (http://localhost/newsite or http://
<IP_of_DS-NOC_computer>/newsite) and configure the Database Host and
Database Name.
4. Continue with the same steps from the following installation section:
See II.4 Installing the DS-NOC (Windows) on page 10.
See III.4 Installing the DS-NOC (Linux) on page 15.
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.
Summary
By default, the Tomcat 7 Manager has an upload file size limit of 50 MB. As of the latest revision
date of this article, the DS-NOC WAR file has grown larger than this default limit.
Problem:
If you upload a WAR file larger than the configured limit, the Tomcat 7 Manager application reports
an error:
The server encountered an internal error () that prevented it from
fulfilling this request.
exception
java.lang.IllegalStateException:
org.apache.tomcat.util.http.fileupload.FileUploadBase$SizeLimitExceededEx
ception: the request was rejected because its size (54010957) exceeds the
configured maximum (52428800)
Reason:
Now the size of noc.war exceeds 50 MB, therefore uploading DS-NOC using
the Tomacat Manager will fail.
Solution:
There are two solutions if you encounter this problem.
Solution 1. Increase the value of max-file-size and the value of max-request-size.
1. Edit the file 'web.xml':
For Windows, the file 'web.xml' can be located under the following directory:
C:\Program Files\Apache Software
Foundation\Tomcat7.0\webapps\manager\WEB-INF\web.xml
For Linux, the file 'web.xml' can be located under the following directory:
/opt/apache-tomcat-7.0.25/webapps/manager/WEB-INF/web.xml
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.
Summary
This article gives instructions on how to upgrade and existing DS-NOC installation. Although the
upgrade process is simple, this FAQ may be helpful, particularly for customers performing an
upgrade of a DS-NOC installation for the first time.
Details
To upgrade an existing DS-NOC:
1. In Tomcat Manager > Undeploy DS-NOC.
2. Restart Tomcat Manager.
3. Deploy the new noc.war provided on the new release / service pack DVD or ISO.
This is described in II.4 Installing the DS-NOC (Windows) on page 10.
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.