- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- OpenVMS Backup and SAN best practices
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2008 09:01 AM
тАО09-08-2008 09:01 AM
Does HP recommend specifically throttling OpenVMS Backup to a DIOLM of 8 when performing backup to a Fibre Channel SAN device? I know there was talk of patching the Backup image to only do 8 IO at a time to allow SAN arrays like the EVA to better handle the concurrent requests.
I am not able to find a reference to it in a recent patch, however.
My understanding of the correct best practice is that heavy concurrent IO applications should be throttled to avoid FC port queues, but again, I am not able to find a place where this is documented specifically.
I would also be very interested in reading anything that HP has for best practices regarding EVA Continuous Access and OpenVMS backup on the same SAN.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2008 11:03 PM
тАО09-08-2008 11:03 PM
SolutionWith the SAN Cache, high DIOLM causes memory thrashing. HP recommends to reducing DIOLM to 32.
Wim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2008 02:42 AM
тАО09-09-2008 02:42 AM
Re: OpenVMS Backup and SAN best practices
and I believe there were backports.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2008 08:16 AM
тАО09-09-2008 08:16 AM
Re: OpenVMS Backup and SAN best practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2008 08:17 AM
тАО09-09-2008 08:17 AM
Re: OpenVMS Backup and SAN best practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 09:56 AM
тАО09-10-2008 09:56 AM
Re: OpenVMS Backup and SAN best practices
$set term/wid=132
$ana/sys
SDA> fc stdt/all !
if this test is correct we only see 6 instances in 50 to 100 days of operation (and backups)
As for setting the DIOLM low sometimes this is a lot of work as for example, DECwindows might decide on boot to run autogen and reboot again because it doesn't like DIOLM set to 32. In OpenVMS 8.3 and 7.3-2 with patches HP created another solution:
Using the wtid limits available in vms732_fibre_scsi-v0400 to set
up a maximum number of io credits to the port. The suggested values for
different FC controllers are:
HSG80 240/(number of hosts + 2)
EMA12000 "
EMA16000 "
ESA10000 "
ESA12000 "
MSA1000 512/(num hosts+2)
MSA1500 "
EVA GL (3000 and 5000) 80
EVA XL (4K, 6K, & 8K) at least 80
XP128/512/1024 16
XP12000/10000 16
To set a cap on OpenVMS v7.3-2 with vms732_fibre_scsi-v0400 (or
later) installed use the following:
$ana/sys
SDA> fc show wtid ! to get the wwid
! use the host address to set for all ports on a controller
SDA> fc set wtid/wwid=
SDA>exit
The SDA set wtid commands should be added to a command procedure and executed in systartup_vms.com so they are activated for every boot.
I would contact the storage group to see if they agree with this solution still because we simply haven't needed to use (and test) it.
Clark Powell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2008 03:15 PM
тАО09-10-2008 03:15 PM
Re: OpenVMS Backup and SAN best practices
You would set DIOLM on the backup accounts, not systemwide.