Long, long, long backup sessions

2001-08-24 Thread Zoltan Forray/AC/VCU
Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3 with 2GB RAM. TSM client is 4.1.2.0) is becoming unacceptable and unworkable. Currently, backup sessions are sometimes taking more than 16-hours (as I send

Re: Long, long, long backup sessions

2001-08-24 Thread Thierry ITTY
as a kind of comparison you can see here the same snippet for our GIS server, hp9000/j6000 1GB/20GB tsm client 4.1, much smaller but... tsm server is a rs6k/f50 2x332 MHz 640 MB, network is ATM/155 Mbps Total number of objects inspected: 333 895 Total number of objects backed up:1 349 Total

Re: Long, long, long backup sessions

2001-08-24 Thread Martin, Jon R.
: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 11:25 AM To: [EMAIL PROTECTED] Subject: Long, long, long backup sessions Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3

Re: Long, long, long backup sessions

2001-08-24 Thread Andrew Raibeck
] cc: Subject:Long, long, long backup sessions Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3 with 2GB RAM. TSM client is 4.1.2.0) is becoming unacceptable and unworkable. Currently

Re: Long, long, long backup sessions

2001-08-24 Thread Lindsay Morris
To: [EMAIL PROTECTED] Subject: Re: Long, long, long backup sessions Consider using the 4.2 client's journal backup feature, which is intended to eliminate the need to scan the file system for changed files. The elapsed time represents the total time from the beginning of the operation to the end

Re: Long, long, long backup sessions

2001-08-24 Thread Lindsay Morris
: Long, long, long backup sessions Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3 with 2GB RAM. TSM client is 4.1.2.0) is becoming unacceptable and unworkable. Currently, backup sessions are sometimes

Re: Long, long, long backup sessions

2001-08-24 Thread Richard Sims
The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3 with 2GB RAM. TSM client is 4.1.2.0) is becoming unacceptable and unworkable. ... Yes, I understand the LARGE amount of OBJECTS INSPECTED is an issue. But, the current data tells me it took over 8-hours from the start

Re: Long, long, long backup sessions

2001-08-24 Thread PINNI, BALANAND (SBCSI)
: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 10:25 AM To: [EMAIL PROTECTED] Subject: Long, long, long backup sessions Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3 with 2GB

Re: Long, long, long backup sessions

2001-08-24 Thread Zoltan Forray/AC/VCU
: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Long, long, long backup sessions Consider using the 4.2 client's journal backup feature, which is intended to eliminate the need to scan the file system for changed files. The elapsed time represents

Re: Long, long, long backup sessions

2001-08-24 Thread Andrew Raibeck
to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Long, long, long backup sessions Consider using the 4.2 client's journal backup feature, which is intended to eliminate the need to scan the file system for changed files. The elapsed time

Re: Long, long, long backup sessions

2001-08-24 Thread Gerald Wichmann
- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Friday, August 24, 2001 8:25 AM To: [EMAIL PROTECTED] Subject: Long, long, long backup sessions Looking for some guidance to improve backup session times. The time it takes to backup our e-mail servers (4-way processor H70 AIX 4.3.3

Re: Long, long, long backup sessions

2001-08-24 Thread Gerald Wichmann
Sorry my math was off by a factor of 100.. :-) 283000/522000 = 5421 seconds = 90.35 minutes = 1.5 hours.. So perhaps it's not that big a network issue afterall.. but still I'd look into the network throughput performance. Gerald Wichmann System Engineer StorageLink 408-844-8893 (v)

Re: Long, long, long backup sessions

2001-08-24 Thread Zoltan Forray/AC/VCU
First, I want to thank everyone for their feedback. Since I am not an AIX person, I passed these responses to my AIX guru. Here are *HIS* reponses (noted with ###: I would suggest the problem is nothing but the amount of files that need to be processed. I have one client with 3 million +

Re: Long, long, long backup sessions

2001-08-24 Thread Lindsay Morris
Zoltan, these stats you sent: Session Duration: 7:06:49 Object Inserted: 78,979 Size of Objects: 2,480,911 Idle Wait Time:1:03:27 Comm Wait Time:3:39:06 say that number-of-files is the biggest issue. Network speed isn't greate, but I see a

Re: Long, long, long backup sessions

2001-08-24 Thread William Boyer
PROTECTED] Subject: Re: Long, long, long backup sessions First, I want to thank everyone for their feedback. Since I am not an AIX person, I passed these responses to my AIX guru. Here are *HIS* reponses (noted with ###: I would suggest the problem is nothing but the amount of files that need

Re: Long, long, long backup sessions

2001-08-24 Thread Thomas Denier
Quoting Zoltan Forray/AC/VCU [EMAIL PROTECTED]: The Elapsed processing time is confusing. Is it trying to tell me it only took 3-minutes to actually transfer the 2.83GB ?? The elapsed times reported by 4.1.2.0 clients are simply wrong. This is a known bug in that client level. The bug itself

Re: Long, long, long backup sessions

2001-08-24 Thread Richard Sims
...We recently upgraded from 2-CPU to 4. It did not improve the backup times, though. ... Compression should not be an issue since it can use 4-fast CPU's. If you are running single-threaded, you'll be using one CPU. Richard Sims, BU

Re: Long, long, long backup sessions

2001-08-24 Thread PINNI, BALANAND (SBCSI)
## Will consider addressing network speed issue. Can't do much. It is a 100 switch. Compression should not be an issue since it can use 4-fast CPU's. Even if ur switch is at 100mbs.And ur network I/F is at auto-negotiation(default) then also ur xfer speed will be at low level.Thats the