Here we summarize technical requirements for individual components. Archive Manager for Files basically consists of:
B)Archive Manager Server
C)ArchiveWeb Server (optional)
All can be installed on separate machines or on one machine.
For a machine where HSM part will be installed, the following optional prerequisites apply:
·.NET Framework 3.5 if not available, setup will continue but the following store types will not be functional in connection with the HSM system:
Amazon S3, Windows Azure, Caringo CAStor, EMC Atmos, FileNet IS, Hitachi HCAP, Nirvanix, Rackspace, Simple Foldering Store, XAM
·.Net Framework 4.5 on the HSM server if not available, Google Drive store will not be functional.
·Microsoft Web Service Enhancements (WSE) 3.0 - if not available, the iTernity store cannot be created.
Archive Manager Server
Archive Manager server requires .NET Framework 3.5 (including .NET 2.0) and .NET Framework 4.0 installed.
NOTE: In case of Windows Server 2008 R2 SP1 run the following command:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319 aspnet_regiis.exe -i
It is possible to install Archive Manager for Files on servers without IIS. However, this DISABLES the creation of HTML shortcuts and VNX archiving. It is also NOT possible to use MS Search as the full-text search engine.
ArchiveWeb Server (optional)
(Usually the same machine as Files Manager Server.) If ArchiveWeb feature will be deployed, install also .NET Framework 4.5 on the respective machine.
Prior to installation of Archive Manager a database must be available, since it is needed during installation. You may choose to use:
·ORACLE database or
·MS SQL database
For detailed information please see the following document:
- Prerequisites - Archive Manager for Files
This section gives you the overview of successful installation of Archive Manager for Files by the separate setup (not the Install package).
IMPORTANT NOTE: Besides the separate setup, Archive Manager can be installed by the Install package which performs all pre-requisite tasks and necessary configuration itself. For installing Archive Manager with Install Package see the short Archive Manager Quick Start Guide.
Archive Manager for Files basically consists of:
B)Archive Manager Server
C)ArchiveWeb Server (optional)
D)Database Server (available prior to installation)
All can be installed on separate machines or all can be installed on one machine.
If HSM store will be used:
1.A database for Archive Manager (either ORACLE, or MS SQL) and a database for HSM (either ORACLE, or MS SQL) must be ready for use.
2.Install HSM on the HSM Server (see the section Installation of HSM), provided that no HSM is installed yet.
NOTE: HSM can be shared by all Archive Manager products. It means that if you already have an HSM storage installed with other Archive Manager products, you may use it for Archive Manager for Files as well.
3.Configure HSM (see the part Configuring the HSM), which includes:
a)Create and specify a MediaStore (see the section Creating a MediaStore).
b)Create and specify a Schema (see the section Specifying a Schema).
NOTE: You may have a separate database server, a separate HSM server, and a separate Archive Manager server. Or, if you wish, you may have them all installed on one machine.
You may have a separate database for HSM, a separate database for Archive Manager. Separate databases are easier to backup.
In our documentation we will be using a separate database for HSM (HSMdb database) and a separate database for Archive Manager (MAM4FilesDB database).
B)Archive Manager Server
Install Archive Manager for Files as described in the Installation of Archive Manager for Files section.
Since version 3.07 it is possible to archive/backup files not only from the file servers (computers) where Archive Manager for Files is installed but from the remote servers as well. As a result the Enterprise Manager component of Archive Manager for Files can be installed elsewhere to control the processes remotely.
ArchiveWeb in an optional feature. It is installed by a separate setup Metalogix Archive Web.exe.
This application is used for viewing archived files over the Internet. A user can access archive via a browser by navigating to the ArchiveWeb:
With mobile device support your archive is at hand virtually anywhere. Pages fitting mobile device screen and simplified navigation contribute to the ease of use.
For more information on installation process and ArchiveWeb itself, please see the ArchiveWeb manual.
A database to be used by Archive Manager must be ready prior the installation.
This section describes installation and configuration of HSM. If HSM is installed remotely, i.e. if HSM is a separate server, one more step is necessary you have to make sure that HSM Base service on the HSM server runs under the Archive Manager super-user account (see the section Addendum Remote HSM Server).
To install HSM on your HSM server, follow these steps:
1.Run Disc \ Metalogix \ Archive Manager Installation Package \ HSM \ HSMSetup.exe.
2.On the Welcome page click Next.
3.On the Logon Information page specify the user account under which the application will be running. It must be in the format DOMAIN\Username.
4.On the Setup type page select Complete and click Next. Then click Install.
5.If the Windows Firewall is on and enabled, it is necessary to allow HSM components to communicate through Windows Firewall. The components (COM+ Network access and HSM services) will be added to the Windows Firewall Exception list. Click Next, then Install.
6.Upon successful installation of HSM, click Finish to exit the wizard.
When installation of HSM is complete, the Configuration tool opens. Here you need to configure HSM, i.e. you need to specify:
·database you will be using;
·media store where files will be archived.
To configure the HSM, follow these steps:
1.In the initial Configuration window select the HSM tab in the left pane. (By default Configuration tool can be found under C:\ Program Files (x86) \ Common Files \ PAM \ PAMConfig.)
2.Click the Configure button to start the Database Connection Wizard and update the configuration settings.
3.In the case that you are working with an MS SQL database, select the Microsoft SQL Server option and then click Next.
NOTE: For an Oracle database select the Oracle option.
4.On the next page please enter the requested data:
·If you have selected Microsoft SQL Server in the previous window, fill in these fields:
Server name (the name of your MS SQL server)
Initial catalog (the name of the database for HSM)
Table owner (name of the SQL Login that is a Table Owner (or the name of the SQL Schema))
Authentication (authentication type used for the database)
User name (database login user (the one you are using as a table owner), if applicable)
Password (enter the requested password, if applicable)
·If you have selected ORACLE in the previous window, fill in these fields:
ORACLE NET Name (ORACLE NET name, TNS name)
Schema (the name of the schema where HSM tables will be created)
User name (log-on user for the database with read and write rights to the table)
Password (log-on users password)
Afterwards, click Next.
5.Click the Finish button. Next, you will have to execute the database scripts.
6.Back in the Configuration window on the HSM tab the data you have entered are now filled in. Run the scripts by clicking the Execute scripts button in the Scripts section.
7.In the next window choose from the following options:
oUse the default credentials - scripts will be executed under the user that has been specified in the database connection
oUse different credentials - scripts will be executed under the defined user
When the desired option is selected, click Next.
8.Further, necessary scripts can be executed from the tool (Execute the database scripts by this wizard) or manual execution by the user is also possible (Get the database scripts and execute them manually). In either case, make your selection and click Next.
We have chosen to execute the scripts by the wizard. In the next dialog DB tables and procedures were created and confirmation dialog appeared.
Executing scripts manually is useful eg. in ase of big databases. In the next dialog scripts can be saved or copied to clipboard. Before continuing you will have to confirm successful completion of the task.
9.Back in the Configuration tool switch to the Advanced tab. Since the HSM system includes the Single Instance Store service, it means that identical files are stored only once.
In the Duplicate files detection section you may specify the duplicate detection method:
a)Select the Detect by content option, should you wish to use the size, checksum and content for detection.
b)Select the Detect by checksum option, should you wish to use the size and checksum for detection;
c)Select Do not detect duplicate files option, should you wish to disable this detection
In the Caching part:
Use caching in case of slow storages (tape etc.). HSM will cache the recently used files to speed up the retrieving process.
If Enable caching is checked, HSM will copy all retrieved files to an HSM internal cache. To set the Cache directory (which should be a local hard disk), use the Browse button next to the respective text box. If you have a cluster, the HSM will know that each installation has its own path.
Set the Minimum cache size and Maximum cache size as well. The Minimum size should be about 80% of the cache size. If the cache is full, HSM will delete files (the oldest first) until the cache reaches the minimum size.
NOTE: To set which specific store should be cached, go to Stores tab. Then select the store and click Manage to edit its configuration.
The HSM stores temporary files created during duplication detection, compression etc. in temporary directory. Its location can be set in Temp directory text box. Usage of environment variables is allowed in this box (e.g. %TEMP% denotes the temp folder of the currently logged on user).
10.Now click on the Stores tab. You need to create a MediaStore and you need to specify a schema here.
If you have created a store already, please start it now. It will be added to the list automatically.
Contrary to the Store section where stores can be just added to the list (not created), in the Schemas text box the user can create new Schemas directly.
To create a MediaStore, see the next part: Creating a MediaStore.
To specify a schema, see the part Specifying a Schema.
NOTE: You must have at least 1 store and at least 1 schema available in order to archive with Archive Manager. For each HSM store (MediaStore) assign a schema. Assigning more than one schema for the same HSM store where Archive Manager will be archiving files is also supported.