I got the same situation.
In our case I (aix) evoke parallel incremental backup sessions, one per
filesystem.

Udo Schoepgens, IT-OP, o.tel.o




Stephan Rittmann <srittmann AT FIDUCIA DOT DE> am 12.03.99 13:59:12

Bitte antworten an "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

An:    ADSM-L AT VM.MARIST DOT EDU
Kopie:  (Blindkopie: Udo Schöpgens/Intern/USR/o-tel-o/de)
Thema: ADSM and big file-servers





Hi all,
I want to start a discussion about ADSM and backing up big file servers. In
our
environment we have 16 Mbit token-ring networks and we are using ADSM to
back
up all of the critical data.
The biggest file servers that we use at the moment has a 18 GB data
partition.
Backing up these servers with incremental backup is no problem. It works
for a
long time, everybody is satisfied about the short backup times. But what
will
happen  in the case of a disk failure. If the server was very full, you
have to
restore up to 18 GB. With our kind of netwotk this would take about 20
houres
or more.
What I want to say is; The disks in the servers  become bigger and bigger,
the
backup time is still the same because of the incremental technique from
ADSM.
I'm sure that most of the useres from ADSM don't think about the long
restore
times in case of a disk failure.
The difference between the network speed and the size of the data disks
becomes
bigger and I see a problem in this fact.
What are you think about these? And how could we solve these problem?
Stephan Rittmann
FIDUCIA AG, Karlsruhe
Germany