PoINT Storage Manager

Version 5.2 with Service Pack 3

Build 380

README

General Information

Supported Storage Systems in Archive Tier

System Requirements

Contact Information

License Information & Disclaimer

General Information

Contents

Install PoINT Storage Manager

Before installing PoINT Storage Manager make sure the system requirements are fulfilled. Then log on as a user which is a member of the local Administrators group and start SETUP.EXE from the distribution package.

Please note that PoINT Storage Manager requires a License Key which enables the licensed functionality. PoINT Storage Manager cannot be used without a valid License Key. The License Key can be entered during installation or at any later time.

During the installation process you can choose the components to be installed:

If you want to perform a client installation to administer PoINT Storage Manager from a client computer, you can uncheck the "Server Components" to install only the components required for the remote administration. Also, if you do not plan to use Storage Vaults using PoINT TAFS or PoINT VFS as Data Source, you can uncheck the appropriate agents. Note that components can be added or removed later by means of the Add/Remove Software Control Panel applet or by starting SETUP.EXE again.

The component "SUN ACSLS Support" should only be installed if you plan to connect to a tape library using a SUN StorageTek ™ ACSLS Server. In this case, the SUN LibAttach Services must be installed prior to installing PoINT Storage Manager.

The component "Web Client" is an optional component which allows users to retrieve or archive files using a standard web browser. Additional requirements for PoINT Storage Manager - Web Client are documented in the section System Requirements and the user documentation for the Web Client can be found in the ReadMe for Web Client

The component "PoINT Storage Manager SDK Runtime" must be selected if a 3rd party application uses the services of the PoINT Storage Manager SDK. This component is mandatory if "Web Client" is selected.

During the installation you will be prompted to enter a Configuration Key. This key is handed to you together with the software package. PoINT Storage Manager cannot be installed without a valid Configuration Key.

After the installation of PoINT Storage Manager the Administration GUI will appear and a wizard will guide you through some required settings.

User Rights

If you plan to administer PoINT Storage Manager using an account which is not a member of the Administrators group, you should add this account to the list of users which are allowed to administer PoINT Storage Manager using:

Setup PoINT Storage Manager > General > Manage User Accounts

After adding this account you can log in using the mentioned account and continue using PoINT Storage Manager.

Windows Server 2008 and later
When installing on an operating system with User Account Control you need to start the Administration GUI one time with administrative privileges and explicitly add your user account to the list of users in the user management. This is necessary because by default only Administrators are allowed to connect, but administrative privileges are not active by default.

PoINT Storage Agent Service Account

During the PoINT Storage Manager configuration you will be prompted to enter an user account which will be used as account for the PoINT Storage Agent Service. The specified account must have access to the files you intend to archive and it must be able to log-on to remote computers if source data are located there. Also, it must be a member of the local Administrators group.

Recommended Directory Settings

During configuration of PoINT Storage Manager you will be prompted to specify directories for caching and for temporary images. The following configuration is recommended:

Database and PoINT VFS Write Buffer

This directory should be located on a different hard disk partition than the operating system. This can be the physical hard disk where the operating system is installed on, unless that disk is in heavy use by other applications.

Temporary Image Volumes and Volume Cache

It is recommended to locate this directory on a dedicated fast hard disk.

Please note that all working directories shall be excluded from On Access Virus Scanner software.

Compatibility with other PoINT Software

Under the following conditions PoINT Storage Manager can be installed together with other PoINT products on the same systems:

PoINT Jukebox Manager

PoINT Jukebox Mananger version 5.0 SP4 or later can be installed on the same system. If you plan to migrate archive data to a jukebox managed by PoINT Jukebox Manager, please refer to section PoINT Jukebox Manager Connector for specific requirements.

PoINT Publisher NG

PoINT Publisher NG version 3.0 or later can be installed on the same system. If you plan to migrate archive data to an optical autoloader managed by PoINT Publisher NG, please refer to section PoINT Publisher NG Connector for specific requirements.

PoINT Archiver

PoINT Storage Manager cannot be installed on a system where PoINT Archiver is installed. Please contact support for information about possible upgrade scenarios.

Upgrading from a Previous Version

The following information do not apply when installing a service pack or hotfix which does not change the version number of PoINT Storage Manager.

Before upgrading your installation make sure that all Archive Volumes have been migrated to Archive Devices. Then deactivate all Storage Vaults and export the database and the System Key. The upgrade will replace your current version by the new version. The new version requires a new License Key. After upgrading from a previous version, the Service Account for the PoINT Storage Agent Service must be specified again. All other settings will be preserved.

Storage Vaults will not be automatically activated after the upgrade. You need to activate them manually after installing the upgrade. Also note that client installations must also be upgraded after upgrading the PoINT Storage Manager server installation.

PoINT NetApp FAS Agent

The PoINT NetApp FAS Agent allows using a NetApp FAS as Data Source for a Storage Vault. This way it is possible to transparently archive files from a NetApp FAS volume to Archive Devices managed by PoINT Storage Manager. Besides the manual and the online documentation please also refer to the separate document "PoINT NetApp FAS Agent" which describes the functionality in detail. This document can be opened through the Start Menu entry of PoINT Storage Manager.

PoINT EMC FileMover Agent

The PoINT EMC FileMover Agent allows configuring an EMC Storage System (Celerra or VNX) as Performance Tier and to archive and migrate files from EMC Storage Systems to upported Archive Devices. Besides the manual and the online documentation please also refer to the separate document "PoINT EMC FileMover Agent" which describes the functionality in detail. This document can be opened through the Start Menu entry of PoINT Storage Manager. The PoINT EMC FileMover Agent will be installed as a part of the PoINT Storage Manager Server Components. It is not possible to install it separately.

PoINT TAFS Client

Installation

The PoINT TAFS Client can be installed on client computers in the LAN if you want to locate the PoINT TAFS Data Source of Storage Vaults on these computers. The PoINT TAFS Client installation comprises the following components which will be installed on the client computer:

The TAFS Client installer can be found on the installation package or in the PoINT Storage Manager installation directory in the subdirectory "TAFS Client Setup". To install the PoINT TAFS Client, copy the installation package to the client computer and start the executable with administrative privileges. After installation of the TAFS Client modules, you will be guided through the configuration of the TAFS Client installation.

Required System Settings

After installation, the PoINT TAFS Agent Configuration Tool will be started. This tool allows configuring how the communication between PoINT Storage Manager and the PoINT TAFS Agent will be performed. If Storage Vaults have already been configured for this PoINT TAFS Client, it is necessary to deactivate all Storage Vaults and activate them again, after changing the communication settings.

SMB Pipes:
To allow communication between the PoINT TAFS Agent on the client computer and the PoINT Storage Manager Service through SMB Pipes, it is necessary to adjust the following system settings on the computer running the PoINT Storage Manager Service and on the computer where PoINT TAFS Client installation has been performed:

TCP:
To allow TCP connections it is necessary to create firewall exceptions for the process PntFtrSvc.exe on the computer running the PoINT TAFS Agent and for jbxArch.exe on the computer where PoINT Storage Manager has been installed. By default the TCP connection will be created using TCP port 8237, so that you may also unblock this port on both systems rather than creating exceptions for the processes.

PoINT VFS Drive Letter

If the PoINT VFS Agent has been installed as a software component, it will create the virtual drive letter which can be used to access Storage Vaults which are configured for the PoINT VFS Data Source. If you do not plan to use this functionality you can avoid creation of the drive letter by either not installing the PoINT VFS Agent component or disabling the PoINT VFS Agent Service using the Windows Control Panel.

Uninstall PoINT Storage Manager

Restore Data in PoINT TAFS Data Sources

Data in the PoINT TAFS Data Source of a Storage Vault will not be accessible after uninstalling PoINT Storage Manager or PoINT TAFS Client, unless purged files have been restored and the PoINT TAFS Reparse Tags have been removed.

This can be achieved using the PoINT TAFS Explorer Shell Extension, by means of the command "Remove TAFS Tags" in the context menu of the PoINT TAFS Data Source in the Windows Explorer. Note that the related Storage Vault must be active and purged data must be present in the configured Capacity or Archive Tier devices.

The command line tool "TagRemover" mentioned in the section Command Line Tools below, can also be used to remove the PoINT TAFS Reparse Tags. However, this tool does not retrieve purged files.

Remove the Software

Before starting the uninstallation of PoINT Storage Manager you should stop and deactivate all Storage Vaults.

Now open the Add/Remove Software Control Panel applet, find the entry for PoINT Storage Manager and click Change/Remove. In the following dialog select Remove All to uninstall PoINT Storage Manager from your system.

During the software removal you will be prompted to confirm remove of some directories. You can confirm this, if these directories have been solely used by PoINT Storage Manager.

Logging and Log Rotation

PoINT Storage Manager logs error, warning and informational messages to different log files which are by default located in the directory "Logs" within the installation directory. This directory can be changed by means of the setup dialog of PoINT Storage Manager. Usually it is not necessary to open the log files directly from that directory because the Administration Tool provides several ways to access all relevant log files.

In order to limit the disk space used by log files, PoINT Storage Manager provides a simple mechanism for log rotation and for archiving old log files. These settings can be changed by means of the setup dialog of PoINT Storage Manager under Advanced Settings.

There you can specify a maximal log file size and age. If either criteria has been reached, the log file will be renamed to "<log file name><time stamp>.archived.log" and a new empty log file will be created. These criteria will be checked when writing to a log file. Therefore log rotation will not be performed for logs which will not be written to anymore.

It is also possible to enable compression of the old log files and to specify a location to move the (compressed) log files to. Additionally, you may select after which period these archived log files shall be deleted. If both, move and delete, is enabled, the files will be moved to the specified directory and deleted after the specified period. The local system account needs read and write permission to the specified directory. If the directory is a network location, you must specify an UNC path and grant access to the computer account where PoINT Storage Manager is running on (e.g. DOMAIN\COMPUTER$).

The compression, moving and deletion of the archived logs files will be performed as a delayed operation - usually at 1:00 AM, after starting the PoINT Storage Manager service or after changing one of these options. If multiple log files are outstanding for compression at this time, they will be packed into one compressed file named "Logs <log file name><time stamp>.zip" Otherwise the compressed file will get the name of the log file plus a time stamp.

Logging on PoINT TAFS Client installations

The PoINT TAFS Agent on PoINT TAFS Client installations writes its log messages to a log file in the directory "Logs" in the installation directory. This directory cannot be changed. The log file can be opened using the command "PoINT TAFS Agent Log File" which is available in the Start Menu.

Log rotation settings for PoINT TAFS Client installations must be changed using the PoINT TAFS Client configuration tool. The functionality is similar to the description above, except that the log archive directory requires read and write permission for the computer where the PoINT TAFS Client has been installed. The compression option cannot be changed for PoINT TAFS Client installations. Old log files will always be compressed.

Default Log Rotation Settings

By default, log files will be split and compressed if they become larger than 512 MByte.

Software Limitations

Maximal Number of Storage Vaults

PoINT Storage Manager supports up to 64 Storage Vaults.

Maximal Number of Archive Devices

PoINT Storage Manager supports up to 20 archive devices (CD/DVD/BD Autoloaders, Optical/Tape Drives or Libraries, HD/NAS Devices or Object Stores).

Maximal Number of Files and Directories in the Archive Database

The PoINT Storage Manager database can store about 1.000.000.000 directories, each containing up to 100.000 files.
When using Storage Vaults with a PoINT VFS or Standard File System data source or Storage Vaults which have been created with PoINT Storage Manager versions before 4.0, the number of directories decreases for each file version which supersedes an older version of the same file. Such configurations support at least 1.000.000.000 different file versions.

Archival/Migration Restrictions

File Attributes and Time Stamps

When copying files between the storage tiers PoINT Storage Manager keeps the following attributes along with the file data:

If one of those attributes has been changed after archiving or copying the file, theses changes will only be copied to Archive or Capacity Tier if also the Creation or Modification Time Stamps have been changed.

Maximal Length of File and Path Names

The Capacity Tier has no additional limitations for file and path name lengths compared to those of the Windows operating system. Windows supports path names of about 32000 characters and path components (file or directory names) of up to 255 characters. Please note that other system components, e.g. storage devices, may have other limitations.

The Archive Tier supports path names of up to 1017 characters, relative to the root of the Storage Vault. A path component (file or directory name) can be up to 255 characters long.

NTFS File Permissions

File permissions will not be archived or copied to Capacity Tier. During retrieval the default Windows permissions for the corresponding parent directory are applied.

NTFS Alternate Data Streams

Alternate data streams will not be archived or copied to Capacity Tier.

Extended Attributes

When using the PoINT TAFS Data Source, files with Extended Attributes cannot be archived or copied to the Capacity Tier. If such files are present, a message will be logged to the job log file and the files will be skipped. With other Data Sources, the files will be archived without the Extended Attribute data.

File/Directory Moves or Renames

File and Directory Deletion

Backup Data of PoINT TAFS Data Sources

It is recommended to perform a regular backup of all data in PoINT TAFS Data Sources. The backup application should be configured so that it does not backup file data of files which have been purged (i.e. are off-line), but that it stores the reparse points. In case of a failure of the hard disk, the backup can be restored to a new hard disk and the Storage Vault can be configured to use the new hard disk (see Restore PoINT TAFS Data Source to a Different Hard Disk).

If no backup of the PoINT TAFS Data Source is present, the data can also be restored from the Storage Vault. But in this case it is necessary to create a new Storage Vault after restoring the data. All data will then be archived again to the new Storage Vault.

Note: Please also read the section Compatibility Issues later in this document.

Restore PoINT TAFS Data Source to a Different Hard Disk

If a hard disk containing a PoINT TAFS Data Source has been replaced, PoINT Storage Manager cannot activate the related Storage Vault anymore. Therefore it is necessary to change the configuration of the Storage Vault accordingly. In case the Storage Vault has been created with PoINT Storage Manager 3.0, PoINT Archiver 5.0 or a later version, the Storage Vault data source path can be changed using the properties dialog of the Storage Vault: Remove the configured path and then add the path with the location of the restored data.

If the Storage Vault has been created by an earlier version of PoINT Storage Manager or PoINT Archiver, the option to remove the data source path is not available. In this case, follow the steps below. Before proceeding with these steps, make sure the data of the PoINT TAFS Data Source has been restored from a recent backup to a directory with the same path name on the new hard disk.

Command Line Tools

No PoINT Storage Manager license is required to use the command line tools mentioned below.

TagRemover

This command line program is provided for Storage Vaults with data source PoINT TAFS and data source NetApp FAS.

Before using this program, please first check the data source specific requirements mentioned below. Then open a command line with administrative privileges and change to the directory where PoINT Storage Manager is installed. Now enter "TagRemover" and the switch "remove". Additionally specify the path to the directory as parameter. Note, that the path has to be enclosed by double quotes in case it contains spaces. Then specify the log file, if no log file is specified messages are displayed on screen.

The program automatically detects if the specified folder path belongs to a Storage Vault for PoINT TAFS or for NetApp FAS. Optionally, the program generates a log file in case a log file is specified as command line parameter.

This program does not retrieve files which have been purged. However, if you plan to delete all files, you can use the command line switch "force" to also remove tags from files which are off-line, i.e. have been purged. The files will then be accessible again, but do not contain any data (they are sparse).

Examples calling the TagRemover program:

TagRemover remove "D:\TAFS Data Source" D:\logFiles\tagRemoverLogFile.txt force
TagRemover remove "\\NetApp_FAS\Data Source" D:\logFiles\tagRemoverLogFile.txt force

Storage Vaults for data source PoINT TAFS

The program removes PoINT TAFS Reparse Tags which have been assigned to files by the PoINT TAFS Filter Driver. Note that the recommended method to remove PoINT TAFS Tags is to use the PoINT TAFS Explorer Shell Extension. Because using this program requires stopping the PoINT TAFS Filter Driver, you must ensure that no users or applications can access data in other PoINT TAFS Storage Vaults on this system. Also refer to section Uninstall PoINT Storage Manager for details.

Before starting the program make sure the PoINT Storage Manager Service has been stopped and the PoINT TAFS Filter Driver is not running. To stop the PoINT TAFS Filter Driver perform the following command on a command line and confirm if you will be prompted to also stop dependent services:

net stop pntvolflt

Storage Vaults for data source NetApp FAS

The program removes Alternate Data Streams (ADS) from NetApp FAS which have been assigned to files by the PoINT Storage Manager.

Before starting the program make sure the PoINT Storage Manager Service has been stopped.

psmcmd

This command line program can be used to trigger Migration or Archive Job Cycles. The tool is part of a PoINT Storage Manager client or server installation and of the PoINT TAFS Client installer. It can only be used by users which are allowed to administer PoINT Storage Manager using the PoINT Storage Manager Administration GUI. Refer to section User Management in the online help or manual for more information.
The following command line syntax must be used:

psmcmd [server=<computer_name>] <command> <parameters>

All commands return 0 if the operation succeeded or a value other than 0 if the command failed. The server option need not be specified if the PoINT Storage Manager Server is running on the computer where psmcmd will be executed.

Show available commands or get help for a specific command
psmcmd help [command]

List all configured Storage Vaults
psmcmd query storagevaults

Retrieve purged files on the Performance Tier
psmcmd recall storagevault=<storage_vault_uid> path=<relative_file_or_dir_name> [simulate]

This command can be used to recall (retrieve) purged files on the Performance Tier. The command is supported for all Data Source types which support purging of files. Please note that this command internally executes a migration job cycle and waits until it completed. If another migration job cycle is currently active, the command waits until the other cycle has finished and then starts the new cycle. If an archiving job cycles is currently active, the command fails with an error message.
The specified path must be relative to the root of the configured Storage Vault. For example if the Storage Vault data source is \\SERVER\SHARE\Vault and the content of the directory \\SERVER\SHARE\Vault\Users\User1 shall be recalled, the value for path must be set to Users\User1.

By specifying the optional parameter "simulate" it is possible to simulate the job execution. After successful execution, the log file indicates which files would have been recalled.

Progress and error messages for the job will be logged to the "Migration job log" of the Storage Vault.

Archive and purge files
psmcmd archive storagevault=<storage_vault_uid> path=<relative_file_or_dir_name> [simulate]

This command can be used to archive files which have not been archived yet and to purge them if this is supported by the Performance Tier and if they are larger than 4 KByte. Please note that this command internally executes an archiving job cycle and waits until it completed. If a migration job cycle is currently active, the command waits until that cycle has finished and then starts the new cycle. If another archiving job cycle is currently active, the command fails with an error message.
The specified path must be relative to the root of the configured Storage Vault. For example if the Storage Vault data source is \\SERVER\SHARE\Vault and the content of the directory \\SERVER\SHARE\Vault\Users\User1 shall be archived, the value for path must be set to Users\User1.

By specifying the optional parameter "simulate" it is possible to simulate the job execution. After successful execution, the log file indicates which files would have been archived and purged.

Progress and error messages for the job will be logged to the "Archive job log file" of the Storage Vault.

Trigger an Archiving or Migration Job Cycle
psmcmd trigger type=[archive|migration] storagevault=<storage_vault_uid> [policies=<policy_list>] [wait] [simulate]

Specify "type=archive" to execute Archiving Policies or "type=migration" to execute a Migration Job Cycle.

If the optional parameter "wait" has been specified the command will wait until the job has been executed and the return code indicates whether the job succeeded (0) or failed. If "wait" has not been specified the return code indicates whether the job has been queued (0) or could not be queued.

By specifying the optional parameter "simulate" it is possible to simulate the policy execution to test the configured policies. If this option has been specified, all conditions will be evaluated, but actions will not be performed. The job summary statistics will then indicate how many files would have been affected by the configured policies.

If the parameter "policies" is not specified, the policies which have been specified as migration policies for the Storage Vault will be used. If policies have been specified, they will be executed in the specified order. The policy list must be a semicolon separated list of policy names and a post fix which determines whether the policy is to be selected from the list of policies which are assigned to the Storage Vault or from the global list of policy templates. The post fix "@sv" selects a policy from the Storage Vault and "@tp" can be used to select a policy from the global template list:
<policy_list>=[<policy_name>@sv|<policy_name>@tp][|;<policy_list>]

Examples:
psmcmd trigger type=migration storagevault=0123456789ABCDEF policies=P1@sv;P2@sv;P1@tp wait

Because key words can be abbreviated as long as they remain unique, the following command line works too:
psmcmd t ty=migration st=0123456789ABCDEF p=P1@sv;P2@sv;P1@tp w

If a policy name contains spaces use this syntax:
psmcmd t ty=migration st=0123456789ABCDEF "p=P1@sv;P2@sv;Copy to Capacity Tier@tp"

T2Copy

This command line program is provided for Storage Vaults with a Capacity Tier using the object based file structure. Starting with PoINT Storage Manager 5.1 this is the default setting. This program does not work for Capacity Tiers using the legacy file structure. T2Copy can be used to copy the content of the Capacity Tier to another path and thereby renaming the files to their original file names.

To copy data from a Capacity Tier, open a command line and change to the directory where PoINT Storage Manager is installed. Now enter "T2Copy" and the following command line parameters: The path to Capacity Tier, the Target Path the File System Structure has to be copied to and the absolute path to a log file. Optionally, specify the command line parameter "versions" to copy all file versions to the target path. Otherwise only the last version will be copied. The command line parameter "verbose" enables detailed log output.
Note that paths have to be enclosed by double quotes in case they contain spaces.

Before starting the program make sure the related Storage Vault has been deactivated.

Examples:

T2Copy "D:\PSM Capacity Tier Devices\Vault 2013" "E:\Target Path for Vault 2013" "E:\logFiles\T2Copy Logfile for Vault 2013.log" versions verbose

T2Copy "\\FileServer\PSM Capacity Tier Devices\Vault 2014" "E:\Target Path for Vault 2014" "E:\logFiles\T2Copy Logfile for Vault 2014.txt"

StoreMigrator

The Object Store Migration Tool (StoreMigrator.exe) allows copying of Archive Volumes stored on one Archive Device to another Archive Device. Additionally, this tool can be used to create a list of the volumes which must be copied to the new device or which are already present on both devices. The current version of Store Migrator supports Archive Devices of type "Object Storage" (cloud based), only.

Please refer to the separate document StoreMigrator.pdf for detailed information about this tool.

Known Problems

Known Hardware Problems

Primera autoloaders may fail to load the last disc

After moving the last disc from the input bin to the drive, the autoloader keeps the drive tray open and stops. The 'Server Messages' dialog appears and indicates that the device has been stopped after a failure. A log file message indicates that multiple discs have been loaded.

Recovery:
Make sure only one disc has been loaded into the drive. If two discs have been loaded put one disc back into the bin.
Press the 'go' button in the device view to restart the autoloader.

Compatibility Issues

Some backup applications do not correctly restore PoINT TAFS file stubs of files which are 512 bytes small or smaller

While restoring such files, some backup applications create files containing zeros instead of restoring the original file stub. Therefore it is strongly recommended to avoid purging of small files by specifying an appropriate size condition (e.g. files size > 4096) in the corresponding purging policy. Additionally, you may forcedly prevent PoINT TAFS Agent from purging such files by adding the following registry key on the computer where PoINT TAFS Agent is running:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PntVolFlt
Value Name: MinPurgeFileSize
Value Type: DWORD
Content: <Size in byte> (Default is 0)

If this registry value is present, PoINT TAFS Agent ensures that files which are smaller than the specified value, will not be purged. Please note that PoINT TAFS Agent ignores commands to purge such files and returns a success return code. Therefore if a job tries to purge such small files, the job reports that the file has been purged, eventhough the command has not been executed by the PoINT TAFS Agent.

Note: It is necessary to reboot the computer after changing this value. If PoINT TAFS Agent is running on a Failover Cluster, the registry value must be set on all nodes.

LTFS tape format compatibility

PoINT Storage Manager formats tapes using the LTFS 2.0 format. This format can be read by other compliant LTFS implementations. However, PoINT Storage Manager does not write to tapes which have been modified by other LTFS software. Such tapes will be treated as "closed" so that they can still be read but no new data will be stored on such tapes.

Compatibility with Virus Scanner Software

To avoid compatibility and performance problems it is strongly recommended to exclude all working directories of PoINT Storage Manager from On Access Virus Scanners.

Supported Storage Systems in Archive Tier

Contents

Supported Storage Systems in Archive Tier

This version of PoINT Storage Manager supports the following storage systems as Archive Devices. If your device is not in the list, refer to the information provided at www.point.de or contact PoINT Software & Systems (support@point.de).

Object Stores

PoINT Storage Manager supports different types of Object Stores as archive devices. Such devices do not use a file system like interface but store objects and provide an object id to access these objects. Support for a specific Object Store device type requires a Connector for PoINT Storage Manager. The following Connectors are currently available:

This version of PoINT Storage Manager is prepared for the PoINT Connector for Microsoft Azure Blob Storage. Please contact PoINT for availability of this connector.

If your device is not in the list please contact PoINT for an updated list of available Object Store Connectors. Please also contact PoINT to obtain additional documentation and information about system requirements for the Object Store Connectors.

Optical Jukeboxes (PoINT Jukebox Manager Connector)

Optical jukeboxes are not directly supported by PoINT Storage Manager. However, optical jukeboxes controlled by PoINT Jukebox Manager can be used as archive devices by means of the PoINT Jukebox Manager Connector.

The PoINT Jukebox Manager Connector allows using Volume Sets as Archive Devices. Before configuring such an Archive Device make sure your License Key enables the PoINT Jukebox Manager Connector and that a supported version of PoINT Jukebox Manager has been installed and licensed.

Requirements

The PoINT Jukebox Manager Connector requires PoINT Jukebox Manager version 8.0 SP2 or higher. In addition to the device license, the License Key must enable the PoINT Jukebox Manager SDK.

PoINT Jukebox Manager can either be installed on the same system as the PoINT Storage Manager server or on another computer which is accessible via a CIFS network share using an account which is valid on both systems. If PoINT Jukebox Manager is installed on another system, it is necessary to install its client components on the PoINT Storage Manager system. This can be performed by selecting "Remote Administration" while running the PoINT Jukebox Manager installation. Please note that it is necessary to also update these client components after installing updates for PoINT Jukebox Manager.

Settings in PoINT Jukebox Manager

PoINT Storage Manager can write to Volume Sets which consist of either rewritable or write once media. For best performance it is recommended to use Dynamic Image Recording, Mirroring or configure caching on hard disk for the Volume Set. Additionally, the following options must be specified in the properties of the Volume Set:

- Enable the option "Notify if total free space is less than..." and set the value to at least 2 times of the Archive Volume capacity specified in PoINT Storage Manager.
- Enable the option "Automatically add new media."

The same Volume Set must not be used by different PoINT Storage Manager Archive Devices and it must not be used by other applications or users. If PoINT Jukebox Manager is installed on another system, it is recommended to create separate network shares for Volume Sets used by PoINT Storage Manager and to restrict the permissions to a specific user account. This share and the user account must be specified when configuring the device in PoINT Storage Manager. This account also must be allowed to connect to the PoINT Jukebox Manager service. To achieve this, open "User Management" in PoINT Jukebox Manager and make sure the account is present and has the right to record media.

If PoINT Jukebox Manager and PoINT Storage Manager are running on the same computer, PoINT Storage Manager uses the account "SYSTEM" to connect to PoINT Jukebox Manager. In this case, make sure the option "Always allow local administrators to connect" is checked in the "User Management" in PoINT Jukebox Manager.

Caching on Hard Disk

PoINT Storage Manager does not depend on a specific write cache configuration, because the PoINT Jukebox Manager Connector controls the flushing of the write cache. In order to use the write cache, just select one of the write cache configurations for the Volume Set. The option "Migrate files when read only." can be enabled to ensure that migrated archive volumes cannot be overwritten.
The size of the write cache must be large enough to store multiple Archive Volumes of the size specified for your Storage Vaults. If more than one Volume Set is configured to use the write cache, the cache size must be increased accordingly. In this case it is also recommended to limit the cache size used by PoINT Storage Manager in the settings dialog of the configured Archive Devices. Note that the specified value must be larger than the Archive Volume size of your Storage Vaults. For best performance, the write cache and the limit specified in PoINT Storage Manager should be as large as possible.

Dynamic Image Recording or Mirroring

When using Dynamic Image Recording it is recommended to enable the option "Synchronize Dynamic Images if no data has been written for..." and set the timeout to about 2 minutes.
If caching on hard disk is also used, the value for "Maximum number of Dynamic Images" should be set to a value which can hold as many data as fit into the configured write cache. For example, if the write cache is set to 100 GByte and the Volume Set consists of 25 GB media, the number of Dynamic Images should be set to at least 4. Please note that you need sufficient hard disk space for both, the write cache and the specified number of Dynamic Images.

Settings in PoINT Storage Manager

To configure a PoINT Jukebox Manager Volume Set as Archive Device in PoINT Storage Manager, create a new HD/NAS Device and select "PoINT Jukebox Manager Volume Set" as device type.

During configuration enter the path to the Volume Set. If PoINT Jukebox Manager is running on another computer you must specify an UNC path, otherwise specify the drive letter path. If an UNC path has been specified, you will also be prompted for an user account. This account requires read/write permissions for the network share and it must be allowed to connect to the PoINT Jukebox Manager service as described above.

The capacity and type of the Archive Volumes need not be related to the media type used in PoINT Jukebox Manager. For example you can configure a Storage Vault which creates 4 GByte volumes and write these volumes to a Volume Set consisting of BD-R media.

The network timeout on the computer running PoINT Storage Manager should be set to at least 600 seconds:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
Value Name: SessTimeout
Value Type: DWORD
Content: <timeout in seconds>

This value must be created if it does not exist. After changing the value, it is necessary to restart the computer.

Multiple Volume Sets per PoINT Storage Manager Archive Device

It is possible to specify more than one path for a HD/NAS Device of type PoINT Jukebox Manager Volume Set. In this case the PoINT Jukebox Manager Connector will use one of these paths for writing and the others will be used for reading only. This way it is possible to finalize a Volume Set and to add a new Volume Set for writing. If the second Volume Set is on another PoINT Jukebox Manager installation, you will need an additional license for the PoINT Jukebox Manager Connector.

Off-line Management

Media belonging to the Volume Set can be deactivated and removed from the jukebox after they have been finalized. In this case, make sure that the Volume Set itself stays active. If PoINT Storage Manager requires media which are currently off-line, it reports the name and the location of the media. Additionally it is possible to query the name and location of the media which hold a specific file by selecting the file in the Archive Browser and clicking on the button "Volume Locations".

Media created by previous versions of PoINT Storage Manager

If the jukebox contains media which have been created using the integrated optical jukebox support of a previous version of PoINT Storage Manager, the Archive Volumes on these media can be read if the following conditions apply:
Media which have been formatted to a specific volume size can be imported and scanned in PoINT Jukebox Manager. Then open the File System View in PoINT Jukebox Manager, select the media and from the context menu select "Set Base Path..." and enter a unique string as path, e.g. "Old Archive Media". The media are now grouped in this directory in the file system. This directory can be added to the path list of a configured PoINT Storage Manager Archive Device of type PoINT Jukebox Manager Volume Set.
Please note that PoINT Storage Manager will not write to these media. To write more data to the jukebox, configure a Volume Set as described above.

PoINT Jukebox Manager Connector does not support media, which have been recorded in "disc-at-once" mode. In this case please contact PoINT Software & Systems GmbH.

Error Recovery

The PoINT Jukebox Manager Connector does not automatically perform recovery after recording or hardware failures while writing to the Volume Set. If the Volume Set becomes write protected after such a failure, it is necessary to fix the problem using the PoINT Jukebox Manager Administration Tool and to rescan the Volume Set. If PoINT Storage Manager is currently reading from the Volume Set you may also need to deactivate the Storage Vaults and the related PoINT Storage Manager Archive Device.

CD/DVD/BD and UDO Single Drives

UDO Drives

- PLASMON UDO30E, UDO30I (FW A027, A028 have been tested)
- PLASMON UDO60E, UDO60I (FW T480 have been tested)

BD Drives

- LG BE06
- Matsushita BD SW-5582 (FW BZE6 has been tested)
- Matsushita BD SW-5583 (FW 1009)
- Optiarc BD-RW BD-M100A
- Pioneer BD-RW BDR-101A
- Pioneer BD-RW BDR-101A
- Pioneer BD-RW BDR-203
- Pioneer BD-RW BDR-206
- Pioneer BD-RW BDR-206M
- Pioneer BD-RW BDR-207M (FW 1.20 has been tested)
- Pioneer BD-RW BDR-208M (FW 1.10 has been tested)
- Pioneer BD-RW BDR-209M
- Pioneer BD-RW BDR-PR1
- Plextor BD-R PX-B900A
- Plextor BD-R PX-B920SA

CD/DVD-R Drives

- LG GMA-4020B
- LG GMA-4120B
- Matsushita BD SW-5582 (FW BZE6 has been tested)
- Matsushita BD SW-5583 (FW 1009)
- Matsushita DVD-RAM LF-D310
- Matsushita DVD-RAM LF-D521
- Matsushita DVD-RAM SW-9571
- Matsushita DVD-RAM SW-9572
- Matsushita DVD-RAM SW-9573
- Matsushita DVD-RAM SW-9575
- Matsushita DVD-RAM SW-9581
- Matsushita DVD-RAM SW-9582
- Matsushita DVD-RAM SW-9583
- Matsushita DVD-RAM SW-9585
- Matsushita DVD-RAM SW-9590
- _NEC DVD_RW ND-1300A
- Optorite DVD RW DD0201
- Philips DVDRW228
- Pioneer DVD-R DVD-R7322
- Pioneer DVD-R DVD-R7783
- Pioneer DVD-RW DVR-103
- Pioneer DVD-RW DVR-104
- Pioneer DVD-RW DVR-105
- Pioneer DVD-RW DVR-106
- Pioneer DVD-RW DVR-107
- Pioneer DVD-RW DVR-108
- Pioneer DVD-RW DVR-109
- Pioneer DVD-RW DVR-110D
- Pioneer DVD-RW DVR-110
- Pioneer DVD-RW DVR-111D
- Pioneer DVD-RW DVR-112
- Pioneer DVD-RW DVR-K11
- Pioneer DVD-RW DVR-K12
- Plextor BD-R PX-B900A
- Plextor BD-R PX-B920SA
- Plextor DVDR PX-504A
- Plextor DVDR PX-708A
- Plextor DVDR PX-712A
- Plextor DVDR PX-716A
- Plextor DVDR PX-740A
- Plextor DVDR PX-750A
- Plextor DVDR PX-755A
- Plextor DVDR PX-800A
- Plextor DVDR PX-810A
- Sony DVD RW DRU-500A
- Sony DVD RW DRU-510A
- Sony DVD RW DRU-530A
- Sony DVD RW DRU-700A
- Sony DVD RW DW-D22A
- Sony DVD RW DW-Q30A
- Sony DVD RW DW-U10A
- Teac DV-W50E
- Teac DV-W58D
- Teac DV-W5000E/S (FW 1.0A)
- Teac DV-W516E / GDM (FW M452)

Standard NAS, SAN and Hard Disk Devices

The following devices have been tested:
- NetApp E-Series
- Promise VessRAID 1840i
- Promise VTrack E610f
- STEC ZeusIOPS

Appliances as Archive Devices

Crossroads StrongBox

CIFS network shares to a Crossroads StrongBox can be configured as Archive Device. The following models are supported:
- Crossroads StrongBox T1, T3
- Crossroads StrongBox T10, T20, T30

The appliance has been tested with software version 2.1.2.7.0

Notes:
If users or applications try to read purged files which have been archived to the StrongBox, they may receive read errors or network timeouts if the data must be read from tape. In this case the user or application must retry the access later. Therefore it is strongly recommended to configure an appropriate File Cache Size on the StrongBox device so that read data will stay in the cache for a reasonable time.

EMC Data Domain

EMC Data Domain can be configured as Archive Device in PoINT Storage Manager if this option is enabled in your License Key. It has been tested with EMC Data Domain OS 5.5.0.4.

PoINT Storage Manager supports the retention functionality. To use this functionality, make sure retention is enabled for the MTree containing the CIFS share to use and then specify the desired retention values when configuring the new Storage Vault. Retention will be applied for all volumes of this Storage Vault using the specified settings. The retention values specified in PoINT Storage Manager must be within the minimum and maximum values configured for the MTree.

PoINT Storage Manager requires access to the storage systems using a CIFS share. During configuration of the device you will be prompted to enter an user account which has access to the share. Make sure this account is known on the storage system and that it has read and write permissions to the CIFS share.

FAST LTA Silent Cube

A volume on a FAST LTA device can be configured as Archive Device in PoINT Storage Manager if this option is enabled in your License Key.

The volume on the FAST LTA device must be configured as "WORM with retention (RWRO triggered)" or "WORM with retention and versioning (RWRO triggered)". Additionally, the creation of the so-called "Safe files" must be enabled for the volume. They must be configured to use the extension "safe" and either the text or xml file format.
You may set a retention time in PoINT Storage Manager when configuring the Storage Vault. If no retention time has been set in PoINT Storage Manager, the default retention time, which has been configured on the FAST LTA volume, will be used.

Fujitsu Storage ETERNUS CS Data Protection Appliances

Shares on ETERNUS CS Data Protection Appliances can be configured as Archive Devices in PoINT Storage Manager if this option is enabled in your License Key.

PoINT Storage Manager supports retention on these devices if the "protectable" option is enabled for the file system. You may set a retention time in PoINT Storage Manager when configuring the Storage Vault. If no retention time has been set in PoINT Storage Manager, a default retention time will be used, if configured for the file system.

NetApp AltaVault

The NetApp AltaVault Storage Appliance can be configured as Archive Device in PoINT Storage Manager using the Standard HD/NAS connector. It can also be configured as Capacity Tier for Storage Vaults if the PoINT Storage Agent Service Account has permission to access the provided CIFS network share.

The appliance has been tested with software version 4.2P1

NetApp FAS (SnapLock)

A NetApp FAS volume can be configured as Archive Device in PoINT Storage Manager if this option is enabled in your License Key.

PoINT Storage Manager supports the SnapLock functionality. To use this functionality, specify the desired retention time stamp when creating a new Storage Vault. SnapLock will then be enabled for all volumes of this Storage Vault using the specified retention time stamp.

The NetApp FAS volume must be shared using the CIFS file system. For further information about configuration of NetApp FAS please refer to the NetApp documentation.

Plasmon Archive Appliance

Volumes managed by the Plasmon Archive Appliance can be used as Archive Device for archival or replication. For usage of the Plasmon Archive Appliance as NAS Device the PoINT Storage Manager License Key must enable the Plasmon Archive Appliance as supported device.

For information on how to configure the Plasmon Archive Appliance please refer to the corresponding Plasmon documentation.

PoINT Storage Manager supports the write once as well as the rewriteable mode of the Plasmon Archive Appliance. The mode can be specified in the "Archive" tab in the Plasmon Archive Appliance administration GUI under the option "Allow File Changes".

It is recommended to specifiy the "Migration Policy" for immediate migration from write cache to media. PoINT Storage Manager waits for completed migration to media before a Job Cycle is finished.

Tape Devices

Tape Libraries and Autoloader

- actidata actiLib Library 2U
- BDT FlexStor II
- Cristie GigaStream T-Series (T8, T24, T48, T560)
- Dell PowerVault (TL2000, TL4000)
- HP MSL G3 Series (MSL2024, MSL4048, MSL8096)
- HP MSL 6000 Series
- HP StorageWorks 1/8 G2
- HPE StoreEver MSL6480
- IBM Tape Library (TS3100, TS3200)
- pivotstor AP Series Tape Library (TL2000, TL4000, TL8000)
- Overland Neo Series
- Qualstar TLS-8211/8222/8433/8466/88132/88264
- Qualstar RLS-8202/8204/8404/8236
- Qualstar RLS-8204/8244/8444
- Qualstar RLS-8560
- Qualstar RLS-85120
- Qualstar XLS-810160/810240/820500/832700/816110
- Quantum Scalar Series
- Spectra Logic T-Series
- SUN StorageTek SL24/48
- SUN StorageTek ML500
- Tandberg Storage Loader 2U LTO
- Tandberg StorageLibrary T24

Tape Single Drives

- DELL PowerVault LTO5-140
- HP StorageWorks Ultrium LTO-3/4/5/6
- Tandberg LTO-6 HH (Tested with firmware revision 3249)

SUN StorageTek™ ACSLS

PoINT Storage Manager supports StorageTek™ ACSLS (Automated Cartridge System Library Software). The SUN® LibAttach software version 1.4.2 has to be installed and configured on the Windows system. PoINT Storage Manager automatically uses the ACSLS server which is configured as default server in LibAttach. To enable support for StorageTek™ ACSLS make sure the appropriate support modules have been selected during installation of PoINT Storage Manager.

Supported tape technologies are LTO 2 through 7.

CD/DVD/BD Autoloader Devices (PoINT Publisher NG Connector)

The PoINT Storage Manager Connector for PoINT Publisher NG ("PPNG Connector") allows using an optical autoloader, which will be controlled by PoINT Publisher NG, as archive device. Data which has been selected for archiving by PoINT Storage Manager will be recorded to one or more optical media. Optionally, a provided print label will be printed on the media which contains information to identify the media.

The intention of this function is to backup (copy) or archive (move) data to optical media. PPNG Connector does not provide functionality to restore archived data. Archived data can be accessed if another archive device has been configured in PoINT Storage Manager or by inserting the optical disc into an optical drive and accessing the data through the drive letter.

Because PPNG Connector does not support access to archived files it is recommended to create a Storage Vault using the "Standard File System" as data source. This type does not support purging of files and thus cannot cause inaccessible data.

Note:
PoINT Storage Manager directly supports optical autoloaders on 32 bit operating systems. If your optical autoloader is supported by your version of PoINT Storage Manager, it is not necessary to configure and use the PoINT Publisher NG Connector. In this case refer to section CD/DVD/BD Autoloader Devices (Direct Attached). If you still want to use "PPNG Connector", you must not configure and activate the optical autoloader in PoINT Storage Manager.

Configuration in PoINT Publisher NG

PPNG Connector requires PoINT Publisher NG version 4.0.243 or later. It can be installed on the same system as PoINT Storage Manager or on a system which is accessible by a CIFS share. After installation and configuration of the optical autoloader it is necessary to configure an ECR folder for images using the desired media type and to enable printing if required. If PoINT Storage Manager is installed on another system it is necessary to create a CIFS share for the parent directory of the configured ECR folder and to grant read/write permission to an account which is also valid on the PoINT Storage Manager system.

Configuration in PoINT Storage Manager

In PoINT Storage Manager first configure a new archive device of type "Hard Disk / NAS > PoINT Publisher NG - ECR". During configuration you will be asked for the path to the configured ECR folder. If this is a network path, you will also be asked for the account which has permission to access the network share. Note that it is necessary to specify the path to the ECR folder, even if the parent directory has been shared.

Now create a Storage Vault which shall use the PPNG Connector. During configuration of the Storage Vault make sure to select the newly configured archive device and to select the volume type and capacity which matches the configured media type of the ECR folder. In the settings for the archive tier it is also possible to select a PoINT Label Editor print file (*.plf) as described in the section below.

When configuring scheduled job execution, it is possible to specify a data threshold so that archiving jobs will only be started if enough data are ready for archiving to an optical disc.

Note:
Multiple Storage Vaults can be configured to use the same "PPNG Connector" as archive device if their volume capacity is compatible to the media of the ECR folder. It is also possible to configure multiple PPNG Connector devices which use different ECR folders and eventually different media types. However, PPNG Connector devices must only be assigned to a Storage Vault if the media type of the ECR folder matches the volume type and capacity of the Storage Vault.

Label Printing

PPNG Connector supports label printing using PoINT Label Editor print files (*.plf). The label file must be created or modified using the PoINT Label Editor version which has been installed with PoINT Publisher NG. After creating the label file open the archive tier settings in PoINT Storage Manager and enable the option "Enable Label Printing". Then click on "Change" to select the print label file. The selected label file will be copied to the Storage Vault configuration. Therefore it is necessary to add the label again after changing it using PoINT Label Editor.

Together with the print label PPNG Connector generates a print data file for each recorded disc. This data file contains the following information:

The print file assigned to the Storage Vault may contain variable fields which reference one or more of the provided data fields. Please refer to the documentation of PoINT Publisher NG for more information about variable data fields in print label files.

Error Recovery

If an error occurs during recording, that error will be reported by PoINT Publisher NG and it must be handled there. Once the image has been correctly recorded it will be removed from the ECR folder and PoINT Storage Manager marks the archive volume as successfully migrated.

CD/DVD/BD Autoloader Devices (Direct Attached)

The following devices are supported on 32 bit operating systems only:

- LSK Alpha
- LSK Delta 3
- LSK Delta 5
- LSK Delta 7
- LSK Gamma 2
- LSK Gamma 4
- LSK Omega Pro

- Primera Publisher II (tested with firmware: 1.25, 1.40)
- Primera Publisher Pro (tested with firmware: 1.16)
- Primera Publisher SE (tested with firmware: 1.23)
- Primera Publisher XR (tested with firmware: 2.07)
- Primera Publisher XR Blu (tested with firmware: 2.40)
- Primera Publisher XRP (tested with firmware: 4.05, 4.07)
- Primera Publisher Pro Xi (tested with firmware: 5.05)
- Primera Publisher Pro Xi2 (tested with firmware: 5.05)
- Primera Publisher 4100 Series and 4100 Xi

- TEAC Explorer 1 ("WP-55T") (up to 3 recorders, tested with firmware 1.46, 1.81)
- TEAC Polarstar ("WP-55B") with optional stacker WP-OP100 (1 recorder, tested with firmware 1.65)
- TEAC DiscSprinter ("WP-3150") (2 recorder, tested with firmware 0.83/MECOUNT, 0.84/UIF)

The following devices are supported on both, 32 and 64 bit, operating systems:

- Rimage 2000i (tested with printer 'Rimage 480i')
- Rimage Amigo II
- Rimage Autostar II
- Rimage 3400 (tested with printer 'Everest 400')
- Rimage 5100N (tested with printer 'Everest-III')
- Rimage 5400N (tested with printer 'Everest 400')
- Rimage DL 5200
- Rimage DLN 5200
- Rimage Producer 6100N
- Rimage Producer 7100 / 7100N (tested with printer 'Everest-II')
- Rimage Producer 8100 / 8100N
- Rimage Protégé II (tested with printer 'Prism')

Driver Installation

Before you can use a device with PoINT Storage Manager you need to install the driver software which ships with the device. When installing the drivers make sure that you install only the required drivers (usually only the printer drivers), but not any support software which may conflict with PoINT Storage Manager operation. To do this you should connect the device and when the Windows New Device Wizard appears, insert the driver disk and let the Wizard automatically install the drivers.

Notes for LSK Autoloaders

These autoloaders are only supported on 32 bit operating systems.

Notes for Primera Autoloaders

These autoloaders are currently only supported on 32 bit operating systems.
If you plan to use multiple identical Primera autoloaders on one system, please contact the Primera support for information how to configure the system appropriately.

Notes for TEAC Autoloaders

These autoloaders are currently only supported on 32 bit operating systems.
The following printer models are supported:

For the proper functioning of the Maintenance Mode of the autoloader the following must be obeyed:

When PoINT Storage Manager is running, the front power key is watched. If it is pressed, the system is requested to shut down. You will see a corresponding message on the front panel display as soon as the autoloader's current activity will be completed and then PoINT Storage Manager terminates and the system shuts down.

Please note:
The restart function (i.e. shutdown + restart) of the operating system does not work properly. The hardware unconditionally powers off after 5 minutes.

Notes for Rimage Autoloaders

PoINT Storage Manager depends on the services of the Rimage Software Suite to control the autoloaders. This version of PoINT Storage Manager supports OfficeNET Software Suite 8.0 and 8.1. The following software builds have been tested:

The Rimage server software must be installed and configured on the system where the autoloader is connected to. It is not necessary that this is the system where PoINT Storage Manager is installed, however, both systems must be connected through the Windows network.

When using a Rimage autoloader the following procedures are slightly different than documented in the manual:

Configuring a Rimage Autoloader
Open Setup PoINT Storage Manager > Devices > Add/Remove Devices and click on Remote Autoloader...
Specify the server and port settings and click on Next. Then select the device from the list and click Add. Now close the dialog and configure the device as described in the manual.

Configuring Bins
Bin and media type settings must be changed using the Rimage software. After changing these settings it is necessary to deactivate and reactivate the device in PoINT Storage Manager.
Please note that the device must be configured to use the FIFO mode in the Rimage software.

Handling 'Bin Empty' Conditions
When a bin is empty the Rimage server sends a notification which will be displayed in the Server Notification dialog as "An alert from a remote server is pending". After inserting new media you need to acknowledge this message.

System Requirements

Contents

Hardware Requirements

Intel Pentium based system or a compatible processor with at least one quad core processor and at least 8 GByte RAM.

Configurations with an optical autoloader as archive device and without a Capactity Tier require a dual core processor and and at least 4 GByte RAM.

Operating System

Supported operating systems for PoINT Storage Manager Server and PoINT TAFS Client:

The .NET Framework 3.5 is required. This framework is an optional feature of all supported operating systems and it will automatically be enabled during installation of PoINT Storage Manager.

Additional Requirements for PoINT Storage Manager - Web Client

If you plan to install PoINT Storage Manager - Web Client, the following Operating System components must have been installed before installing PoINT Storage Manager:

Note:
When using ASP.NET 3.5 on Windows Server 2012 (R2), it is necessary to change the .NET Framework version of the Application Pool used by the Web Client to .NET 2.0. This change must be performed after installing PoINT Storage Manager Web Client. By default, Web Client uses the DefaultAppPool.

Hard Disk

The installation hard disk must be formatted with NTFS. Also, the hard disk used to store images and the database must not be encrypted or compressed.

Program Files
The program files require about 100 MByte of hard disk space on the system partition.

Archive Database
The database must be located on a NTFS formatted hard disk partition with sufficient space to store database entries for all files wich have been copied to the Archive Tier.
The following formula is an estimation for the required space for the database:

Database Size = 1024 Bytes * NumDirs
+ 256 Bytes * (NumDirs + NumFiles)
+ 36 Bytes * NumFiles

<NumDirs> and <NumFiles> are the total number of directories and files stored in the Archive Tier.

Examples:
- 1 million files and 10.000 directories will require about 315 MB hard disk space for the database.
- 10 million files and 100.000 directories will require about 3 GB of hard disk space for the database.

The database will automatically be increased in steps of 100 MByte, the initial size is 500 MByte.

Temporary Image Volumes and Volume Cache
Archived data are first stored in a temporary image volume on the hard disk before the volume is migrated to the Archive Devices. The temporary hard disk space will be released after successful migration of the volume. While a Storage Vault Job Cycle is running it requires space for at least two volumes per active Storage Vault.

Note: When archiving large files you must provide hard disk space for all volumes wich are required to store the two largest files.

The volume cache is used to cache data which have been read from tape or object store devices. It is located in a sub-directory of the directory for the temporary image volumes. The size of this cache is configurable using the Advanced Settings dialog of PoINT Storage Manager. After installation the size is set to 20 GByte.

Capacity Tier Metadata Cache
Storage Vaults with a Capacity Tier using the object based file structure create a cache to map file IDs to the file entry in the Capacity Tier. This cache is located in the directory which is specified as Configuration, Journal and Log Files directory in the PoINT Storage Manager setup dialog. It requires approximately 130 Byte per file in the Capacity Tier.

PoINT VFS Agent
If the PoINT VFS Agent has been selected as a component during installation, it will create an directory and read cache with the initial size of 1 GByte in the database directory. Also, the PoINT VFS write buffer will be located in the database directory. This buffer must be large enough to store all files which will be written to a PoINT VFS Data Source at a time or which will be migrated from an External File System. Please refer to the online help for more information about recommended directory settings.

Contact Information

Address:
PoINT Software & Systems GmbH
Eiserfelder Str. 316
57080 Siegen, Germany

E-Mail:
sales@point.de (sales and product related inquiries)
info@point.de (general inquiries)

WWW:
www.point.de

License Information
Possession, use, duplication or dissemination of this documentation as well as the software described in this documentation is authorised only pursuant to a valid written license from PoINT Software & Systems GmbH or an authorised sublicensor.

Disclaimer
PoINT Software & Systems GmbH believes the Information included in this publication is accurate as of the date of publication, it is subject to change without notice. PoINT Software & Systems GmbH is not responsible for any inadvertent errors. PoINT Software & Systems GmbH makes no representations that the use of its products in the manner described in this document will not infringe on existing or future patent rights, nor do the descriptions contained in this document imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.

A functioning storage workflow requires a well configured system environment with devices working free of faults and, if applicable, flawless storage media. Therefore it is of the essence that the user does backup all data by functions offered by PoINT software and/or (if required) by supplementary software products at adequate intervals (i.e. in accordance with the scope and frequency of changes), and thereby to facilitate the reinstatement of these data even in exceptional situations (i.e. in case of hardware malfunction).