Bug 195988 - System Hang during back up used Veirtas NetBackup
Summary: System Hang during back up used Veirtas NetBackup
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: iscsi-initiator-utils
Version: 4.0
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Mike Christie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-06-20 07:00 UTC by Jung Chul Woo
Modified: 2012-06-20 16:04 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2012-06-20 16:04:36 UTC


Attachments (Terms of Use)

Description Jung Chul Woo 2006-06-20 07:00:46 UTC
Description of problem:
This server serves as Remote connection gateway. The users control the each 
server through this system. This system uses MySQL DB and remote connection 
gateway application developed by programmer. User's traces connected this 
system recorded in the form of "Logs". Formerly logs compress "xxxx.tar.gz" and 
move another directory. The application and log files of this system backed up 
by Veritas NetBackup. The capacity is 130G, nearly 80,000~100,000 files. When 
backed up through Veritas NetBackup, this system hang. Backup speed was nearly 
50~60MB/s. How can I find this issue? Please answer or mail me.

Version-Release number of selected component (if applicable):
RedHat Enterprise AS 4 (Kernel 2.6.9-11)
Xeon 3.0Ghz 10EA
10GB Memory
MySQL DB

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jiri Pallich 2012-06-20 16:04:36 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.