We have about six sun servers with about 700+ filesystem. We have a
daily incremental backup for all. Yes, we managed to backup all FS with
the backup window of about 10 hours. Here is how it works:
1- We used the adsm command sch to invoke our unix script which will in
turns use adsm command dsmc inc.
2- Four process will be used for each node or sun server in this script.
You can use more or less it depends on your system's power.
For more information, please let me know, so I can detail our method.
We are very happy, since we can backup all of this data in our backup
window. However, there are disadvantages, such as the retry option
which will be missing. We are in the process of automating this
function to simulate the retry function.
I hope this help. This is the least I could do for this useful list.
Regards
Fawzi Al-Matar
Saudi Arabia
>
> I wonder if anybody has experience configuring a single Unix box
> as multiple ADSM client nodes. I'm pretty sure I've read on this
> list of people doing something similar with Netware machines, but
> I haven't seen anything in regard to a Unix client.
>
> We have a very large file server that is turning over more data
> than we can handle in a given night--due in large part to ADSM's
> single-threaded nature. We're considering defining this single
> file server as thirteen separate ADSM clients (one for each file
> system).
>
> I've been told that a single ADSM node can not participate in
> more than one schedule at a time, so I'm left with this idea of
> making the one machine multiple ADSM nodes. I'm not sure,
> however, how I would go about setting up the proper dsm.sys and
> dsm.opt files.
>
> I would like to hear from anyone who may have experience in this
> area.
>
> Thanks. -- Tom
>
> "If I could dot the 'i' in a Michigan Thomas A. La Porte
> game and the good lord came to take me Archivist, Feature Animation
> the next day ... at least I could DreamWorks SKG
> die happy." - Beano Cook, ESPN <tlaporte AT anim.dreamworks DOT
> com>
|
