- Home
- Hardware
- Software
- Business Continuity
- Business Continuity Manager
- CCI
- Copy-on-Write Snapshot
- Hitachi Backup Services Manager
- Hitachi Data Protection Suite
- Hitachi Data Retention Utility
- Hitachi Dynamic Link Manager
- Hitachi Protection Manager
- Hitachi Replication Manager
- Hitachi ShadowImage In-System Replication
- Hitachi TrueCopy Remote Replication
- Hitachi Universal Replicator
- Hitachi Virtual Tape Library
- IBM Flashcopy replication
- PAV/HPAV
- XRC Replication
- Storage Management
- Basic Operating System
- Basic Operating System V
- Hitachi Device Manager
- Hitachi Tuning Manager
- Hitachi Replication Manager
- Hitachi Global Link Manager
- Hitachi Dynamic Provisioning
- Hitachi Tiered Storage Manager
- Performance Monitor
- Resource Monitor
- Server Priority Manager
- Storage Capacity Reporter
- Hitachi Command Director
- Storage Navigator Modular 2
- Storage Services Manager
- Universal Volume Manager
- Virtual Partition Manager
- Operating Systems
- Business Continuity
- Solutions
- Education
- Forums
Linking with Tuning manager
Hitachi Tiered Storage Manager can use Tuning Manager for collecting performance data and use this as a query so you can check which volumes are busy on which raidgroups. This allows you to more effectively manager the USP(V|VM) or NSC55 based on real performance figures. This is a very useful part of HTSM because it allows you query the most busiest applications/volumes and can prevent you from having performance problems. You have to have enough free space in your array to be able to move volumes around but that is quite obvious.
Tiered Storage manager relies on configuration data from Device manager and performance data from Tuning Manager. Therefor you first have to install and configure both these products if you want to use this feature.
Make sure on the HTNM server the HiCommand Suite Tuning Service is started because HTSM relies on it for collecting the performance metrics.
If you verified everything is working correctly link HTSM to HTNM by modifing the "tuningmanager.properties" file.
The content of the file looks like this:
# Tiered Storage Manager configuration file for Tuning Manager cooperation.
# the period when the Tiered Storage Manager acquires information
# ("week" and "month" can be specified.)
htnm.infoAcquirePeriod=week
# the period when the Tiered Storage Manager caches subsystem information
# that the agent manages (in minute)
htnm.infoCachePeriodInMinute=60
# the number of cooperating Tuning Manager servers
htnm.servers=1
# the information(host name and port number) on the cooperating Tuning Manager server
htnm.server.0.host=10.10.10.10
htnm.server.0.port=23015
#htnm.server.1.host=
#htnm.server.1.port=
#htnm.server.2.host=
#htnm.server.2.port=
As you can see it allows you to define more HTNM servers when you want additional arrays managed by HTSM but have different performance sources. (HTNM servers)
htsm link with htnm
Hello Hitachi users,
Has anyone actually been able to successfully link htsm with htnm? Can you use port 23015 (as suggested in this tip) for the apps to use? I have these products installed in a Windows envirnoment and I've had this to do on my list for some time.
Thanks,
reversec
reversec, Yes this actually
reversec,
Yes this actually works. Even better, you can create migration rules based on performance metrics in HTNM. This is the idea behind connecting HTSM to HTNM.
Regards,
Erwin