- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- valid /etc/ddr.dbase entry for v5.1x (A and B-1)
Operating System - Tru64 Unix
1753546
Members
5638
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-13-2004 01:11 PM
тАО05-13-2004 01:11 PM
valid /etc/ddr.dbase entry for v5.1x (A and B-1)
The problem is slow to very slow backup performance using vdumps and
brbackup (SAP Br Tool) in the order of 1.5MB/s to 6.6MB/s as recorded by
collect.
What I need is a valid /etc/ddr.dbase entry for v5.1x (A and B-1).
Machine types affected: ES40, ES45, GS140, GS60, DS20.
Tape Library: MSL6060 (4x LTO 2)
HP Documentation states that the LTO 2 tape library is supported on Tru64,
but this is not the case as the current ddr entry states only Ultrium (LTO
1):
SAPXXX#> more /etc/ddr.dbase | grep Ultrium
# Matches "Ultrium"
Name = "HP" "Ultrium"
# Ultrium mode select parameters for rewind after reset behavior
The hwmgr listing states the device as "Ultrium 2-SCSI"
HWMGR Listing:
130:
path_port_id_6 = 6
path_target_id_6 = 2
path_lun_id_6 = 2
path_dev_i/o_cnt_6 = 0
path_state_6 = 1
path_new_state_6 = 0
path_xfer_6 = 0
path_wds_6 = 0
path_avserv_6 = 0
path_pxfer_6 = 0
path_avwait_6 = 0
registration_time = Wed Apr 28 16:17:03 2004
user_name = (null) (settable)
location = (null) (settable)
software_module = (null)
state = available
state_previous = unknown
state_change_time = none
event_count = 38
last_event_time = Thu May 13 14:51:20 2004
access_state = online
access_state_change_time = none
capabilities = 0
indicted = 0
indicted_probability = (null)
indicted_urgency = (null)
disabled = 0
name = SCSI-WWID:02000008:5006-0b00-001f-a734
category = tape
architecture = SCSI
phys_location = bus-6-targ-2-lun-2
dev_base_name = tape8
model = Ultrium 2-SCSI
firmware_rev = F43W
read_ops = 693920
write_ops = 10344046
read_bytes = 42634489856
write_bytes = 674650130432
current_density = 66
block_size = 0
records = 1
filemarks = 0
rewind_timo = 3600
space_timo = 3600
load_timo = 3600
space_eod_timo = 3600
resid = 0
sense_info = 0
sense_key = 6
soft_err = 0
hard_err = 0
active_paths = 1
standby_paths = 0
failed_paths = 0
donot_use_paths = 0
selected_bus = 6
selected_target = 2
selected_lun = 2
path_fail_limit = 1
subsys_dev_handle = 9
manufacturer = HP
consistent_name = 1
ccmn_specific_addr = 18446739676786513152
cluster_dev_directions = 0 (settable)
drvr_max_xfer = 16777215
SAPXXX #>
brbackup (SAP Br Tool) in the order of 1.5MB/s to 6.6MB/s as recorded by
collect.
What I need is a valid /etc/ddr.dbase entry for v5.1x (A and B-1).
Machine types affected: ES40, ES45, GS140, GS60, DS20.
Tape Library: MSL6060 (4x LTO 2)
HP Documentation states that the LTO 2 tape library is supported on Tru64,
but this is not the case as the current ddr entry states only Ultrium (LTO
1):
SAPXXX#> more /etc/ddr.dbase | grep Ultrium
# Matches "Ultrium"
Name = "HP" "Ultrium"
# Ultrium mode select parameters for rewind after reset behavior
The hwmgr listing states the device as "Ultrium 2-SCSI"
HWMGR Listing:
130:
path_port_id_6 = 6
path_target_id_6 = 2
path_lun_id_6 = 2
path_dev_i/o_cnt_6 = 0
path_state_6 = 1
path_new_state_6 = 0
path_xfer_6 = 0
path_wds_6 = 0
path_avserv_6 = 0
path_pxfer_6 = 0
path_avwait_6 = 0
registration_time = Wed Apr 28 16:17:03 2004
user_name = (null) (settable)
location = (null) (settable)
software_module = (null)
state = available
state_previous = unknown
state_change_time = none
event_count = 38
last_event_time = Thu May 13 14:51:20 2004
access_state = online
access_state_change_time = none
capabilities = 0
indicted = 0
indicted_probability = (null)
indicted_urgency = (null)
disabled = 0
name = SCSI-WWID:02000008:5006-0b00-001f-a734
category = tape
architecture = SCSI
phys_location = bus-6-targ-2-lun-2
dev_base_name = tape8
model = Ultrium 2-SCSI
firmware_rev = F43W
read_ops = 693920
write_ops = 10344046
read_bytes = 42634489856
write_bytes = 674650130432
current_density = 66
block_size = 0
records = 1
filemarks = 0
rewind_timo = 3600
space_timo = 3600
load_timo = 3600
space_eod_timo = 3600
resid = 0
sense_info = 0
sense_key = 6
soft_err = 0
hard_err = 0
active_paths = 1
standby_paths = 0
failed_paths = 0
donot_use_paths = 0
selected_bus = 6
selected_target = 2
selected_lun = 2
path_fail_limit = 1
subsys_dev_handle = 9
manufacturer = HP
consistent_name = 1
ccmn_specific_addr = 18446739676786513152
cluster_dev_directions = 0 (settable)
drvr_max_xfer = 16777215
SAPXXX #>
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 06:51 PM
тАО05-13-2004 06:51 PM
Re: valid /etc/ddr.dbase entry for v5.1x (A and B-1)
From your grep output on the ddr.dbase, I must conclude that the "DENSITY" sections are missing in your ddr.db /
I attached a complete LTO ddr.dbase section to this reply.
Remember to run the "ddr_config -c" after you inserted the missing pieces into ddr.dbase /
Rgds,
Johan.
_JB_
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-13-2004 08:02 PM
тАО05-13-2004 08:02 PM
Re: valid /etc/ddr.dbase entry for v5.1x (A and B-1)
Have a look inside the documentation of your backup software (install section for Tru64).
The thread "tape on 5.1" 4-5 entries before contains a pointer to the documentation of netbackup explain in detail the necessary ddr entries.
The thread "tape on 5.1" 4-5 entries before contains a pointer to the documentation of netbackup explain in detail the necessary ddr entries.
Help() { FirstReadManual(urgently); Go_to_it;; }
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP