So how are people using (planning to use) large
disk pools (either random or FILE - with or
without Sanergy)?

Migration's one process per node seems to limit
the usefulness of the large disk pool to
implement disk to disk backup.

A large disk pool appears useful for:
1)      Large number of nodes with small to
        medium size backups (small, medium,
        large and huge are dependent on your
        hardware) and you migrate to tape.
2)      Disk pool is large enough to contain
        all primary backup data and you do
        no migration to tape.

A large disk pool does not appear useful for:
1)      Small number of nodes with large to
        huge size backups. TDP nodes would be
        a good example of this (our case).

Is there some work-around for this migration issue?

Fred
-----Original Message-----
From: rbs AT BU DOT EDU [mailto:rbs AT BU DOT EDU]
Sent: Friday, June 06, 2003 8:48 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: anyone using ATA disk systems
Importance: Low


>We have also been looking at using a large diskpool.
>It appears migration only uses one tape drive per node.
>So, if you use TDP to back up 500GB to disk and then
>run migration, it will only use one tape drive to
>migrate that 500GB.
>
>Is this true?

Migration has historically run as one process per node's data,
so what you are seeing seems to say that this remains true today.

  Richard Sims, BU