ADSM-L

Re: lanfree / storage agent idea or whateva :-)

2006-12-14 04:26:55
Subject: Re: lanfree / storage agent idea or whateva :-)
From: "Hooft, Jeroen" <Jeroen.Hooft AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 14 Dec 2006 10:24:13 +0100
On the TSM-server you define the paths of system A, the storage-agent
system.
System B will then make will send the backup-data via the LAN to the
storage-agent on system A. (as specified with "LANFREETCPServeraddress")
>From system A the data will be sent over the SAN to a tapedrive.

This mechanism with a remote storage-agent is nice when you have a fast
internal/virtual network, like in the IBM's P570's. You only need 1
system with an HBA to tape while the other lpars in the system use the
internal network to sent the data to the system with the HBA. 
I played with it and got a reasonable performance on a P570, when using
a virtual internal network with an high MTU size. 

Jeroen



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
goc
Sent: Wednesday, December 13, 2006 2:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] lanfree / storage agent idea or whateva :-)

hi all, i've been thinking ...
is one storage agent enough to serve all lanfree clients we wish to back
up ?

for example:
on server A which is STA i have running dsmsta with following
configuration

root@hptdb02:/opt/tivoli/tsm/StorageAgent/bin # more dev* set staname
STA_2 set stapassword password set stahladdress sta_2.domain.hr set
stalladdress 1511 define server MAIN_TSM serverpassword=password
hladdress=main_tsm.domain..hr lladdress=1500

&

root@hptdb02:/opt/tivoli/tsm/StorageAgent/bin # more dsmsta.opt
SERVERNAME MAIN_TSM DEVCONFIG devconfig.out COMMmethod TCPIP TCPPort
1511

this server A sees the LTO drives as local drives /dev/rmt*, hard linked
as per manual


on client (server B) in dsm.sys i have

...
ENABLELANFREE       yes
COMMmethod         TCPip
LANFREETCPPort 1511
LANFREECOMMMETHOD TCPip
LANFREETCPServeraddress sta_2.domain.hr
TCPPort            1500
TCPServeraddress   main_tsm.domain.hr
...

now my question is : when i define /dev/rmt drives i must do it on STA
server (A) which sees the drives phisicaly and hardlinked to /dev
directory exactly as seen by the MAIN_TSM server

OR

can i place dummy /dev/rmt* on client server since it's using
information from STA server which sees the drives (rmt's) for real ?

how do you manage it ?  i got a feeling after some implementation that
STA must be installed and configured on every server which has BA client
ready to backup/archove on it ... (this is maybe even true)

it would be nice that 1 STA i enough and lanfree BA clients can use him
...
i think i need a vacation, i talk too much

thanks.

my new record :-)
-------------------------------------------------------
Total number of objects inspected:      253
Total number of objects backed up:      253
Total number of objects updated:          0
Total number of objects rebound:          0
Total number of objects deleted:          0
Total number of objects expired:          0
Total number of objects failed:           0
Total number of bytes transferred:     2.96 TB
LanFree data bytes:                    2.96 TB
Data transfer time:                3,948.46 sec
Network data transfer rate:        805,348.31 KB/sec
Aggregate data transfer rate:      110,039.74 KB/sec
Objects compressed by:                    0%
Elapsed processing time:           08:01:37




TSM 5.3.4
AIX 5.2
LTO3
bla bla ...



Attachment: disclaimer.txt
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>