Highlighted
Toddman214
2 Iron

Merging a client index back together

Jump to solution

Networker 8.2.3.8

Windows 2012r2

Hi all,

I encountered an issue in which a particular client index has reached a very large size.....665gb (yes, gigabytes) over the past couple years. The reason is that this backup points to Isilon, and backs up all of the NFS and CIF shares on there. I believe I saw where there are 200,000,000+ files in there, and retention on them is anywhere from 5 weeks to 13 years, so that I can browse for them whenever needed. Because of the nature of what we do, there's never any telling what Im going to be asked for or when. So, I have a ton of files that must be searchable for a very long time, so Im aware of why this index is so big. My main two options are continuing to grow the volumes on the Networker server (which someday, just wont work anymore), or running my Index entry backups to tape to retain them for that long retention, but then having to recall both the index backup tapes AND the data tapes as well for older restores, which is also an option Im not really happy with.

Because that index started getting so big, I was running out or room on that volume. I stood up another volume, and redirected the index path to the new volume, and backups of this client have been pointing there. I was able to get my original volume expanded enough so that it can now hold both parts of the client index, and I now want to merge them back together. I always get a lot of requests for restores, and I have to stop the backups, point the index path back to its original location before i can perform a restore, if the data is needed from before I separated the index.

So, in short, how can i merge the secondary part of the index back into the original index? Inside of the client index folder, i can see the backup subfolders created daily, but I dont want to simply copy those over to the original index and assume all would be well. That would probably work, but might break something at the same time.

Thanks all!

Todd

0 Kudos
1 Solution

Accepted Solutions
muetzd
1 Nickel

Re: Merging a client index back together

Jump to solution

Toddman214,

There is no issue with copying in the index folders.

Ensure there are no backups or recovers in progress for the client you are working on.

"Accept new sessions" can be toggeled to No to ensure something does not kick in accidentally.

nsrls <client_name> to get a bench mark.

ensure you know where the latest client file index backup is.

mminfo -avoRt -q name=index:<client_name> | more


Copy in the index folders.

Rerun the nsrls <client_name> is there an appreciable difference?

nsrck -L6 <client_name>

This will ensure the new entries are picked up from the new location.

nsrinfo -t <date> <client_name> | more

where <date> is converted to decimal from hex of a file name in a db6 sub-subfolder.

David.

2 Replies
muetzd
1 Nickel

Re: Merging a client index back together

Jump to solution

Toddman214,

There is no issue with copying in the index folders.

Ensure there are no backups or recovers in progress for the client you are working on.

"Accept new sessions" can be toggeled to No to ensure something does not kick in accidentally.

nsrls <client_name> to get a bench mark.

ensure you know where the latest client file index backup is.

mminfo -avoRt -q name=index:<client_name> | more


Copy in the index folders.

Rerun the nsrls <client_name> is there an appreciable difference?

nsrck -L6 <client_name>

This will ensure the new entries are picked up from the new location.

nsrinfo -t <date> <client_name> | more

where <date> is converted to decimal from hex of a file name in a db6 sub-subfolder.

David.

Toddman214
2 Iron

Re: Merging a client index back together

Jump to solution

Thank you, David. I have now merged the index, and it seems to be working fine.

0 Kudos