| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 555.1 | max index info for NT, different for Digital UNIX | DECWET::LENOX | The quiet before the storm | Fri Apr 04 1997 10:01 | 8 |
|
With NSR on NT V4.3, limits are 2GB (for each index).
With NSR on NT V4.4, limits should be 4GB for client indexes,
assume that media index will also be this, but that would need
checking.
With NSR on NT after V4.4, should handle much larger indexes.
|
| 555.2 | | KAHLUA::LEMONS | And we thank you for your support. | Fri Apr 04 1997 10:20 | 5 |
| Thanks very much. I'm sorry for not asking for this in my original
request, but what about NetWorker Server for Digital UNIX V4.2B?
Thanks!
tl
|
| 555.3 | 8Gb each index file | DECWET::EVANS | NSR Engineering | Fri Apr 04 1997 13:17 | 0 |
| 555.4 | | KAHLUA::LEMONS | And we thank you for your support. | Fri Apr 04 1997 13:25 | 2 |
| Thanks!
tl
|
| 555.5 | uh oh | SANITY::LEMONS | And we thank you for your support. | Wed Apr 16 1997 06:37 | 28 |
| Hi
Here's a df on my /nsr 'disk', which is a 6 member RAID-5 array of 4 GB
drives:
# df -k /nsr
Filesystem 1024-blocks Used Available Capacity Mounted on
nw_domain#nw 20945920 4381962 16552192 21% /nw
#
So, if each index file can be 8 Gbytes in size, then the file index in
/nsr/index could be 8 Gbytes, and the media index in /nsr/mm could be
up to 8 Gbytes as well. Right?
In practice, I know that the media index will be a fraction of the
size of file index.
I'm planning to keep our site backups in our TL822 (soon, TL893) for
one year. I believe we have, or will add, TL8nn capacity to achieve
this. But I'm concerned that I might exceed the maximum file index
size.
Is that 8 Gbytes a hard-and-fast limit? If so, please increase it as
soon as possible (I'm beta-testing NetWorker Server for Digital UNIX
V4.3, if you'd like to slip the change in there :) ).
Thanks!
tl
|
| 555.6 | Gulp | SANITY::LEMONS | And we thank you for your support. | Wed Apr 16 1997 06:49 | 17 |
| Gulp. A little more data:
du -k /nsr/index
.
.
.
4335968 /nsr/index
# du -k /nsr/mm
18545 /nsr/mm
So I read this that my file index is already 4.3 Gbytes, while my media
index is 18.5 Mbytes. Am I seeing this correctly? What will happen
when the file index exceeds 8 Gbytes?
Thanks!
tl
|
| 555.7 | Big index news and caveats... | DECWET::FARLEE | Insufficient Virtual um...er.... | Wed Apr 16 1997 09:58 | 21 |
| Terry,
Do you only have one client?
The 4.3GB of index files is split among ALL of your clients.
The 8GB limit is for any ONE client's index file
(/nsr/index/foo.bar.dec.com/db)
Note that as your indexes grow, they will get slower...
NetWorker's database implementation is lightweight, but is not
optimal for huge indexes.
In a future relase (without a schedule affixed as of yet, but sometime
after the fall), I believe that the indexes will be broken into 2GB chunks
with essentially unlimited expansion.
That doesn't mean they will be fast enough to satisfy you, just that it
will work.
Kevin
|
| 555.8 | | SANITY::LEMONS | And we thank you for your support. | Wed Apr 16 1997 10:31 | 12 |
| Kevin
Oh! Whew! 8 Gbytes for ONE client's index file is no problem. We
have 130 clients, and I don't see any one client's index file growing
to be 8 GB. You mentioned that:
"The 4.3GB of index files is split among ALL of your clients."
Do you mean the media index, or the file index, in that sentence?
Thanks!
tl
|
| 555.9 | | DECWET::FARLEE | Insufficient Virtual um...er.... | Wed Apr 16 1997 11:51 | 4 |
| I mean that the 4.3GB you measured in the /nsr/index tree
represents the SUM of all your clients' file indexes.
Kevin
|
| 555.10 | | SANITY::LEMONS | And we thank you for your support. | Wed Apr 16 1997 18:04 | 7 |
| Kevin
Gotcha. Yep, 4.3 Gbytes IS the sum of all of my client's file
indicies.
Thanks
tl
|