>Load-Balancing is a "would be nice" and not a must. Cross-location was meant
>in a way that we have 3 separate Amanda installations, each in a different
>locations. System A at location A will backup the clients on location B and
>the system on location B; system B on location B will backup clients at C and
>System A, and so on. Should be no problem for any software. I just mentioned
>that in fact it might matter that it is possible to split up the system into
>3 (or more) smaller chunks.
Load balancing could be achived by cutting your system into some
chunks that would each be backed-up by a specific system.
But cross back-up IS a STRONG issue. As it works today, amanda relies
on system specific features on each client to take care of incremental
back-up. Let suppose you have 2 different back-up servers that would
save files from a specific client one after the other:
- back-up server A runs a level 3, incremental dump
- back-up server B runs a level 0, full dump
- back-up server A runs a level 4, incremental dump
You would like that your server A level 4 dump refeers to the level 3
also done by server A. Most likely it will refeers to the ull dump
made on server B...
This problems comes from the dump(8) that Amanda runs on the client,
not from Amanda design itself (except the choice to run dump(8)
:). What would it be with Gnu tar?
>out of reality), as there is a budget to buy a software. And if you know what
>a licence for Networker (50 Clients, 2 Storange Nodes, ...) costs, you know
>what we could pay a programmer ;-)
Well, I mentionned that to a friend, also sys-admin, his immediate
answer was that you should buy something (he mentionned Veritas
actually). Whatever the fact a programmer could do it, consider that
it could take him 2 or 3 years to have something working...
And also consider that Amanda is designed to run on tape, the version
to run on disk is only a development thing...
Best regards,
Olivier
