Log:
Assessments - 0, GPA: 0 ( )

Instruções de Operação HP, Modelo HP Integrity NonStop H-Series

Fabricante : HP
Arquivo Tamanho: 149.88 kb
Arquivo Nome :
Língua de Ensino: ende
Ir para baixar



por este dispositivo também tem outras instruções :

Facilidade de uso


Version H4.02 – December 2014
Summary of Changes
VTC is supported under MS-Windows 2012, in addition to MS-Windows 2008.
A new utility, “VTC Management Console” or VTCMC, has been added. It handles the
VTC internal configuration.
Add support of LTO6 emulation and media type, without Encryption.
SSL is available in the BackPak components, tunnelling is no longer required. On
NonStop, it is provided by the ComForte SecurLib/SSL library. On Windows, SSL is
provided by Microsoft framework and by OpenSSL. BackPak components are
distributed with SSL disabled.

On the NonStop, SSL is configured through the ComForte file SSLCFG, a few
parameters are configured through the BackBox TACL macro BB053_SSL.
On the VTC, SSL is configured through the VTCMC and in the BackPak UI.
“CPU affinity” has been added as a criterion in the tape drive selection. BackPak
prefers tape IOPs that run on the same CPU as the tape application (BACKUP,
TMFDR…). This can be disabled in the NonStop profile accessible via the NSK Nodes
tab in the BackPak UI.
The EMS Extractor is now configured through the NSK Nodes tab in the BackPak UI.
The file BBEXTCFG has been removed.
A new NonStop program (OBB055) has been added for cloning physical tapes to
virtual tapes without changing any of the associated DSM/TC information. When
replicating backup, BB055 is equivalent to BACKCOPY but nothing is change in the
copied volume, volume label and backup dates are identical. It can also be used to
clone a virtual media to physical one.
A new functionality is now available in the Windows Advanced Pool Management, the
Copy Pool Sync option. This new option copies a volume from the Storage Pool to
the Copy Pool of the same Data Store. The copy is done through the regular backup
script, automatically submitted after a backup, or executed on demand through the
UI for a single volume or an entire Data Store. Execution is reported in EMS as a
regular backup script, although it’s not configured as a script. Copies are done on
remote path only and it will be chosen among available path in the Copy Pool.
Ems Messages are now highlighted for all alert messages, and only for alert
messages. The replication in of alert message to message#3171 is now optional.
In configuration of data store scripts, the user has now the choice to:
- Either continues the usual manual configuration of user-defined scripts
(“Generic” scripts).
- Or Select pre-defined scripts to use “as is” (“TSM” and “Manual Restore”
scripts)


...


Escreva a sua própria avaliação do dispositivo



Mensagem
Seu nome :
Introduza os dois dígitos :
capcha





categorias