Here, you can:
Once you have connected to the Storage Manager Explorer, call up this dialog using the context menu of the root node of your Storage Manager Explorer:
Fig.: Context menu of the root node
Select the Properties command.
Fig.: "Properties" dialog box
"General" tab |
|
Server |
Version specification of the SMX and server name of the PROXESS server. In the case of distributed systems, the name of the server on which the PROXESS Storage Manager is installed. |
DBIL connection |
DBIL stands for database interface layer. |
Database name |
Name of the SQL database which uses the Storage Manager for saving its settings. If the field remains empty, the default database provided by the system, SMDB, is used. |
DBIL server |
Name of the server on which the PROXESS Database Manager is installed. |
Protocol |
Network protocol between the Storage Manager and Database manager (e.g. TCP/IP). If both modules are on one computer, specify the "Local server" setting. |
Number of simultaneous connections |
Number of SQL connections or SQL queries between the Storage Manager and the SQL database of the Storage Manager (e.g. the SMDB). Recommendation: 10 for large systems with approx. 30 users, and five for smaller systems |
Hierarchical storage management |
|
Also split volumes by database (cannot be undone) |
With this setting, volumes are created separately according to PROXESS database. This setting may make sense if you are operating a personnel archive in addition to a general archive or are running multiple clients in a system and would also like to separate the associated archive files from one another. |
Permanently save volume image files in image cache |
With this option, you activate the HSM image cache process. This is required in order to create a virtual "image cache" as a new device in the next step. An image cache is reserved disk space on Blu-ray media, for example. |
License file |
Path to the valid PROXESS license file |
"Protocols" tab |
|
Selection between: - TCP/IP - Local server - Named Pipes |
A purely local installation works efficiently with the "Local server" or "Named Pipes" setting.
For a distributed installation of the PROXESS modules on the network, TCP/IP generally makes sense.
Only select those protocols supported by the underlying server. |