Author: Mark Rinfret <mrinfret AT MARKRINFRET DOT COM>
Date: Sat, 5 Jun 1999 10:10:25 -0400
I'm in the process of configuring and testing ADSM and a 3590 tape drive with autochanger on an RS/6000 S7A system. The tape drive is connected to a SCSI F/W adapter. The server and client are both o
Author: Terence Louis <terence.louis AT USAA DOT COM>
Date: Mon, 7 Jun 1999 11:01:03 -0500
Mark, The throughput you are getting seems too low. We are seeing 4 MB/Sec to 7 MB/sec backing up AIX clients across an ATM network to a ADSM v3.1.2.20 server running on a RS/6000-S7A with 3590 tape
Now we buffer all our data to diskpools first, then I see about 28 GB/hr bleeding the diskpool to tapepool. just a FYI... later, Dwight Mark, The throughput you are getting seems too low. We are seei
Try checking the blocksize on your tape drive. I've had problems where an interrupted mksysb backup has left a drive with a blocksize of 512 and this caused similar symptoms on a 3575 library. Change
Is the bottleneck something else? We initially got poor performance on migration, but the problem was the updates to the ADSM database. We put the ADSM database behind a cached SSA adapter and our mi
ADSM sets tape drive attributes to be appropriate to its needs. Verify this in AIX by doing 'lsattr -E -l rmt_'. If you "steal" the drive from ADSM to do something in between ADSM uses, you may subv
Hi all, Any suggestion on the disk placement of the ADSM log? One of my server is a sliver node and I have the 3GB ADSM log on a SCSI internal disk and mirrored on the system disk where the system pa
Author: Kenneth Sparks <ken_x_sparks AT AMOCO DOT COM>
Date: Wed, 9 Jun 1999 08:44:30 -0500
If possible keep it on disks other than the database. Just to be safe keep it out of rootvg and then worry about internal vs external, but not too much. Hi all, Any suggestion on the disk placement o
Author: Richard Wagner at FOOTACTIONPO1 <IMCEACCMAIL-Richard+20Wagner+20at+20FOOTACTIONPO1 AT FOOTACTION DOT COM>
Date: Wed, 9 Jun 1999 08:56:00 -0500
It has been my experience that you should keep the log and database volumes on different drives froom each other. The reason being, the log file is actually a backup to the database, so it makes sens