サポートと今すぐチャット
サポートとのチャット

Quadrotech Archive Shuttle 10.3 - Installation Guide

Planning for the Archive Shuttle Databases

Archive Shuttle uses the following Databases:

·The Archive Shuttle Directory database. There is just one of these; it hosts all configuration and non-item based metadata.

·The Archive Shuttle Item database(s). There is one of these for each source Link (e.g. one per Vault Store). These databases do not have to be on the same SQL Server as the Archive Shuttle Directory database. Each Item Database can be on a separate SQL Server, if required.

Microsoft SQL Server must be installed and set up before you install Archive Shuttle. The collation requirement for the SQL Server installation must be case-insensitive, accent-sensitive (CI, AS); case-sensitive and accent-insensitive installations are not supported.

Microsoft SQL Server must be on a dedicated server, either physical or virtual. It is not supported to have it on the same server as the Archive ShuttleCore server. It is not supported to have the Microsoft SQL Server shared with any other software, for production use.

Before installing the Archive Shuttle Core Components, make sure the account that will be used has “dbcreator” rights in Microsoft SQL Server.

info

NOTE: SQL is only relevant within your environment when installing Core (see Quadrotech Archive Shuttle Compatibility Guide for more). If you are installing within the cloud, Quadrotech maintains SQL for you.

The following versions of SQL Server are supported with Archive Shuttle:

Version

Supported?

SQL Server 2005

No

SQL Server 2008

No

SQL Server 2008 R2

No

SQL Server 2012

Yes

SQL Server 2014

Yes

SQL Server 2016

Yes

SQL Server 2017

Yes

info

NOTE: Having the latest service pack installed is recommended.

SQL Editions

Although Enterprise Edition of Microsoft SQL Server is recommended, Standard Edition may be used if the SQL instance uses the recommended (not minimum) resources associated with the size of migration you are performing. Planning for additional time will be required to accommodate regularly required offline maintenance.

Silent (Unattended) Installation

Archive Shuttle Core and the Archive Shuttle modules can be installed using a silent / unattended method. The general format of the command line is as follows:

msiexec /i <package> /quiet /l*v <msilog.file> PARAMETER1=”Param1 value” PARAMETERx….

There is a special parameter called ADDLOCAL where it is possible to either specify ALL (for all features to be installed), or list the ones that are required from the tables below.

Unattended Installation of Archive Shuttle Core

 Modules Installer

Features

ASAdminModuleFeature


ADCollectorModuleFeature


EVCollectorModuleFeature


EVExportModuleFeature


EVImportModuleFeature


EVProvisioningModuleFeature


ExchangeImportModuleFeature


ShortcutPostprocessModuleFeature


NativeFormatImportModuleFeature


Office365ModuleFeature


Parameters

APPLICATIONFOLDER

Modules root installation path, single module can be overridden

ASADMINMODULEFOLDER


ADCOLLECTORMODULEFOLDER


EVCOLLECTORMODULEFOLDER


EVEXPORTMODULEFOLDER


EVIMPORTMODULEFOLDER


EVPROVISIONINGMODULEFOLDER


EXCHANGEIMPORTMODULEFOLDER


SHORTCUTPOSTPROCESSMODULEFOLDER


NATIVEFORMATIMPORTMODULEFOLDER


OFFICE365MODULEFOLDER


SERVICEACCOUNT

Service account to be used

SERVICEPASSWORD

Service account password to be used

ASWEBSERVER

Archive Shuttle web server

LOGFOLDER

Log file folder

USE_HTTPS

USE_HTTPS=1 to enable HTTPS

ALLOW_OVERRIDE_DATABASE_NAME

This enables an option in the installer to allow the Archive Shuttle Database name to be specified.

MAINDBNAME

Can be used to specify a different Archive Shuttle Directory Database name.

Unattended Installation of Archive Shuttle Modules

 Modules Installer

Features

CoreFeature


WebserviceFeature


WebUIFeature


Parameters

APPLICATIONFOLDER

Archive Shuttle Core root installation path, specific features can be overridden.

ASSERVICEFOLDER


ASWEBSERVICEFOLDER


ASWEBUIFOLDER


SERVICEACCOUNT

Service account to be used

SERVICEPASSWORD

Service account password to be used

LOGFOLDER

Log file folder

LICENSE_FILE

Path to license file to user

ASWEBSERVER

Archive Shuttle Web Server

MAINSQLINSTANCE

SQL instance of Archive Shuttle Directory database

USE_HTTPS

USE_HTTPS=1 to enable HTTPS instead of HTTP

DONT_CHECK_WEBSERVICE

Set DONT_CHECK_WEBSERVICE=1 if it is not required for the installer to check that the modules can communicate with the Archive Shuttle Core.

SKIP_TRY_START_SERVICES

If specified it will prevent the installer from trying to start the services at the end of the installation

Examples of unattended installation

The following are provided as examples of how to perform an unattended installation:

Install the AD Collector Module

msiexec /i ArchiveShuttleModulesInstall-7.x.xxxxx.y /quiet /l*v C:\Temp\ADColl.log ADDLOCAL=ASAdminModuleFeature,ADCollectorModuleFeature APPLICATIONFOLDER=”D:\Modules” SERVICEACCOUNT=EV\VaultAdmin SERVICEPASSWORD=xyz123 ASWEBSERVER=SRV001.EV.LOCAL LOGFOLDER=”D:\Logs”

Install EV Export Module

msiexec /i ArchiveShuttleModulesInstall-7.x.xxxxx.y /quiet /l*v C:\Temp\ADColl.log ADDLOCAL=ASAdminModuleFeature,EVExportModuleFeature EVEXPORTMODULEFOLDER=\\file001\exportimport APPLICATIONFOLDER=”D:\Modules” SERVICEACCOUNT=EV\VaultAdmin SERVICEPASSWORD=xyz123 ASWEBSERVER=SRV001.EV.LOCAL LOGFOLDER=”D:\Logs”

Changing Archive Shuttle Module Deployment

From time to time it may be necessary to add additional modules to servers that have already had some Archive Shuttle modules deployed. To do this, perform the following steps:

1.From Windows Control Panel, select Programs.

2.Select Uninstall a program.

3.From the list of programs, select Quadrotech Archive Shuttle Modules.

4.Right click the entry and choose Change.

5.Follow the onscreen prompts to add/remove the required components.

Upgrading Archive Shuttle

Introduction

This section describes how to upgrade an Archive Shuttle migration environment from Archive Shuttle 10.x.

 

We strongly advise you read through this section in its entirety before performing any kind of production environment upgrade.

 

There are three components that will be upgraded:

·Archive Shuttle Core: An MSI will be run to perform this upgrade.

·Archive Shuttle Modules: An MSI will be run to perform this upgrade.

·Archive Shuttle databases: Archive Shuttle Core will upgrade the Archive Shuttle Directory Database, and each Item Database when the Windows services start, following the upgrade.

 

info

NOTE: The global administrator account needs to be able to authenticate using basic authentication.

info

NOTE: See the Quadrotech Archive Shuttle Compatibility Guide to determine what version of .Net is required for the Archive Shuttle Core server.

Support Upgrade Paths

Upgrade to Archive Shuttle 10.3 is supported from Archive Shuttle 10.2 or Archive Shuttle 10.1. The specific build that is running will not affect the upgrade.

info

NOTE: Administration of Archive Shuttle using Internet Explorer 8 is no longer supported.

info

NOTE: It’s NOT possible to upgrade Archive Shuttle to version 10.1 when existing JournalTransformation mappings are present in the database, as Archive Shuttle 10.1 contains breaking database changes. Please remove the appropriate mappings prior to your update, or finish your Journal Transformation migration in version 9.9.

If you are not sure which mapping you need to remove, run a SQL query to get a list of created Journal Transformation ContainerMappingIds.

SELECT cm.ContainerMappingId FROM dbo.ContainerMapping cm

INNER JOIN dbo.Container c ON c.ContainerId = cm.TargetContainerId

WHERE c.ContainerTypeId IN (19,20,21)

 

How to Monitor DB Upgrade Status

Archive Shuttle should handle upgrade with databases' larger than 100GBs without the need for manual intervention.

Getting Ready

We recommend that, whenever possible, you perform the upgrade in a lab environment first. This gives you some familiarity of the upgrade process and allows you to fine-tune the upgrade steps to suit the particular customer, environment, policies, and procedures.

 

Having access to a lab environment also enables the exploration of the new features that are delivered in the newer version of Archive Shuttle. More information relating to the new features is available in the Release Notes and the Revision Notes.

 

Before starting the upgrade, it is essential to have the following:

·New Archive Shuttle 10.1 Core MSI

·New Archive Shuttle 10.1 Modules MSI

·Access to the username/passwords used during the installation for the Archive Shuttle Core and Modules

 

info

NOTE: Any username used during the original installation is remembered. However, the password must be re-entered.

In order for the upgrade to succeed, we recommend that there is sufficient free space on the SQL server locations for both the database and log files. The space available should be as follows:

Database/Log

Space

Archive Shuttle Directory

2x current size of database

Archive Shuttle Directory Logs

1x current size of log file

Archive Shuttle Item Database

2x current size of database

Archive Shuttle Item Database Logs

1x current size of log file

Sufficient time should also be allocated to the upgrade. Upgrading a large Archive Shuttle Item Database can take several hours. We recommend you monitor the Core log files after deployment to verify the process has completed when working with large deployments.

If a problem is encountered when upgrading the Archive Shuttle database, there are manual steps that can be performed to resume the upgrade. These are available from Quest Support.

Performing the upgrade

We advise you to perform the upgrade on the Archive Shuttle environment when migration activity is not actively running. Prior to performing the steps below, we recommend that you disable the Archive Shuttle modules that have been deployed and then allow some time to pass for the modules to complete their queued work before proceeding.

We also advise you to review the Archive Shuttle Dashboard. If the needles on the activity gauges are showing 0, then exports and imports are not currently running. Other background activity might still be in progress, so it is advised to perform the step of disabling the modules and reviewing the module log files to ensure work has stopped.

The following steps should be performed in order to upgrade the environment:

1.Stop the Archive Shuttle Modules on all servers.

2.Stop the Archive Shuttle Core service on the Archive Shuttle Core Server.

3.Perform a full SQL database backup of:

·Archive Shuttle Directory Database, and

·Every Archive Shuttle Item Database

4.Run the new Archive Shuttle 10.1 Core MSI on the Archive Shuttle Core Server.

5.Verify that the installation/upgrade completes without errors. When the installation has been completed, open the Archive Shuttle Admin Interface and navigate to some of the pages.

6.Run the Archive Shuttle 10.1 Module MSI on each server which have modules installed.

info

NOTEs:

1.If the migration target is Exchange or Office 365 and the server running the ingestion module is Windows 2008 R2, there is an additional Microsoft component to install.

2.If the Office 365 Leavers functionality is to be used within Archive Shuttle, then there are additional requirements described in this link.

3.For the Office 365 module to process licensing for Leavers, the PowerShell execution policy needs to be set to RemoteSigned or Unrestricted. Verify that the installation/upgrade completes without errors. After the installation the Archive Shuttle modules page in the Admin Interface should show all modules without a red background. This indicates that they are properly communicating with the Archive Shuttle Core.

4.If any changes have been made with regards to the logging levels for the Archive Shuttle Core or Modules, those changes will need to be implemented again once the upgrade has completed.

When the upgrade has been completed, perform the following post upgrade checks and ensure the step relating to Environment Sync is performed.

Post upgrade checks

Following the installation and upgrade of the migration environment, verify the upgrade by performing the followings tasks:

1.Open the Archive Shuttle administration page, and verify that the page opens without errors.

2.Verify the build number in the lower left hand corner of the administration page. It should be: 10.1.0.NNNNN (NNNNN will be five digits indicating the exact build number)

3.Go to the EV Environment page, and perform a Sync All EV Environments operation. This will take a few minutes to run, and is an essential post-upgrade step.

4.Open the Modules page from the Archive Shuttle administration page, and verify that all of the modules are accessible (none should show red, indicating that the Archive Shuttle Core has had issues contacting the module).

5.Verify that all the Archive Shuttle services are started using the Windows Service Control Manager on each server in the environment.

6.In each of the Archive Shuttle databases (Directory Database, and each Item Database) there is a table called SchemaVersion. The versions reported should be as follows:

·Archive Shuttle Directory Database: 10.2.0.0

·Archive Shuttle Item Database: 10.2.0.0

info

NOTE: If the SchemaVersion tables do not show these versions, contact Quest Support. We also recommend that you perform another full database backup prior to using Archive Shuttle for further archive migrations.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択