discuss a requirement with me: remote storage pool I/O agents
1997-07-26 05:43:00
Hi ADSM- ers.
With V3 IBM adresses some of my important requirements.
But there still are some important ones I would like to
officially post to IBM later.
Before I do so, I would like to discuss this requirements on this forum.
This might improve the quality of the requirement,
add voting voices ,
or just on the contrary prevent me from raising
unnecessary requirements.
Tell me what you think about my requirement.
Tell me also if you like or dislike the idea (of discussing requirements
here) itself.
The first of the requirements is not a modest one:
*************************************
remote storage pool I/O agents
*************************************
* Problems / Task to be supported:
=============================
A)
In scenarios where nodes
- are spread over different network segments
- have large percentage of changed data daily
the network bandwith may become limiting factor
making it necessary to install a group of ADSM servers
instead one server only. Or even one evades to
local backup solutions at all.
Both of these solutions cause more administration
expenditure than necessary.
B)
On installations with large number of nodes the
I/O throughoutput of ADSM server may become critical.
C)
offsite backups require tapes to be physically moved
away / brought back from/to ADSM Server
and add some administrative overhead.
Wanted:
=======
- Reduction of data amount over network segment with ADSM Server
where applicable (A)
- ability to improve throughoutput of ADSM Server by adding second
server
to the existing one - instead of replacing the existing one
- ability to generate offsite DB backups and backup storage pools
over network, without need to transport media back and forth.
Possible solution
==============
! p l e a s e u s e f i x e d f o n t for reading !
! Legend for those with another character sets: !
<---- this is left arrow
----> this is right arrow
* Currently
Only ADSM Server performs I/O´s against storage pools:
AC <--backup AS <--backup
DL data --> DE data --> Storage Pool
SI SR
ME <--control MV <--control
N data--> E data--> Database
T R
* Wanted
ADSM Client exchanges control data with ADSM Server,
and backup data (user files) with ADSM I/O agent.
The ADSM I/O agent may, but does not have to
reside on the same computer as ADSM server.
ADSM Server only copes locally with it´s database,
and exchanges control data with clients
and with I/O agents.
special case: backup DB.
AS
AC <--control--> DE <--control
DL data SR data--> Database
SI MV
ME E <--control
N R data--> AA
T <--backup DG
data------------------> SE <--backup
MN data--> Storage
T Pool
For 1) this enables to move most data inside of one
network segment - assuming one ADSM I/O agent in
segment,
or even to use localy attached robots on clients
for ADSM - good for file servers.
For 2) this enables to move tape I/O s away from
ADSM Server, thus freeing bus&memory bandwith
ressources on the computer with ADSM Server.
For 3) this enables offsitel tapes
have inserted in a robot attached over network
to ADSM server, eliminating
the need for transportation and
special administration of external tapes.
Bye,
Juraj SALAK
KEBA
Linz
Austria
sal AT keba.co DOT at
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- discuss a requirement with me: remote storage pool I/O agents,
Sal Salak Juraj <=
|
|
|