Title: | NetWorker |
Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
Moderator: | DECWET::RANDALL .com::lenox |
Created: | Thu Oct 10 1996 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 750 |
Total number of notes: | 3361 |
Hi Does NetWorker server have a maximum number of: o savesets per server o savesets per client If so, what are these numbers? Thanks! tl
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
682.1 | if there is, it's way too complex to figure out | DECWET::EVANS | NSR Engineering | Thu May 15 1997 11:52 | 9 |
Terry -- it's usually memory/swap driven, so it could be almost anything - NetWorker uses "worklists" (linked lists in memory), so when there is a lot of "stuff" to worklist, one could run shy of either memory and/or swap. Naturally, the entries in the worklist can vary based upon the kind of operation you are trying to accomplish: saveset, file info, index entry, etc /bwe | |||||
682.2 | SANITY::LEMONS | And we thank you for your support. | Thu May 15 1997 13:51 | 7 | |
Hi Bruce So, my answer, I believe, is that there isn't a hardcoded limit, but system resources will eventually be exhausted. Thanks! tl |