Hi Douglas,
In Solaris you can get better performance if you use
raw devices for DB, LOG and diskpools.


> My organization recently migrated a 45GB TSM 5.1.5
> database from an old AIX platform to a Sun V880
> running Solaris 8. The migration of the database was
> done by using "dsmserv restore db" as the export
> failed on varios errors. A db audit was never
> performed because of the downtime involved - days,
> weeks, who knows?
> The server has 4*900MHz Sparcs, 8GB RAM, one
> functional Gb ethernet card, and 6*73 internal FC
> disks. Externally, a JBOD was used, Sun's D2,
> 12*36GB
> SCSI-3 disks. It was all configured with Disksuite
> in
> this way. /, /usr, /opt were mirrored using two of
> the
> internal disks. The other disks were configued as
> RAID
> and had filesystems that contained primary db and
> log
> volumes as well as a storage pool for Domino. The
> external array was also configured as RAID 5 and had
> filesystems that would contain the db and log copies
> as well as other storage pools -Backuppool, etc.
> When the system came up, performance was incredibly
> poor and it became apparent that the bottleneck was
> the D2 array which had problems migrating and
> backing
> up simultaneously.
> At that point or shortly thereafter, stgpool volumes
> were spread between the internal disk and external
> disk and the the db/log copies were deleted.
> The current situation is that, after inspecting the
> output from "q sessions", the client make contact
> with
> the server and then sits in queue for a very long
> time. Once the actual backup/restore starts, it runs
> like greased lightning, however. Incidentally, there
> are over 1000 desktop clients runiing 95, 98 and XP.
>
> Any ideas, suggestions? Thank you...
>
>
>
>
>
______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca

___________________________________________________
Yahoo! Msviles
Personaliza tu msvil con tu logo y melodma favorito
en http://moviles.yahoo.es