[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::networker

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

722.0. "hsm indexes" by BRSADV::BUGGENHOUT () Thu May 29 1997 09:12

Hi

for a customer I have setup a small nsr/hsm config and played around with
it. The customer site has a lot of small files so they are very much concerned
about the indexsize and the use of it.
Because of all there questions I noticed that I miss a few answers too which
can be useful for others so 

- as far as I could see NSR creates 1 indexfile per client, if this is a backup
   AND a HSM client will this be 1 indexfile or can it be split ?
- when exactly for HSM is an indexentry created and used : pre-migration or
  migration ?
- when a file is modified between pre-migration and migration then no migration 
   will be done. What happens at the next pre-migration time : a new copy
  needs to be made : is the previous one replaced ? Is the new copy part of
  a new saveset so the old one stays and it is just the indexentry that is 
   updated to the new copy in the new saveset ?
- Indexentries are normally deleted when volumes are recycled, no ? If a stub is
  deleted then after 60 days the file is deleted too : how ? Just removing the
  entry out the index I suppose ?

Thanks for the input

Regina

T.R	Title	User	Personal Name	Date	Lines
722.1		DECWET::SDY	Support Novice...seeking enlightenment	`Thu May 29 1997 12:50`	29
	>- as far as I could see NSR creates 1 indexfile per client, if this is a backup > AND a HSM client will this be 1 indexfile or can it be split ? it should be 1 index file for each, HSM looks like a separate client (ala archive) >- when exactly for HSM is an indexentry created and used : pre-migration or > migration ? the Migration saveset is created during the pre-migration stage, which is when the index entry will be created. >- when a file is modified between pre-migration and migration then no migration > will be done. What happens at the next pre-migration time : a new copy > needs to be made : is the previous one replaced ? Is the new copy part of > a new saveset so the old one stays and it is just the indexentry that is > updated to the new copy in the new saveset ? the new one is part of a new saveset, and the old saveset stays around for the files that haven't changed. >- Indexentries are normally deleted when volumes are recycled, no ? If a stub > is deleted then after 60 days the file is deleted too : how ? Just removing > the entry out the index I suppose ? yes, I believe so. steve.
722.2	whoops..	DECWET::SDY	Support Novice...seeking enlightenment	`Fri May 30 1997 14:11`	21
	re: -.1 It has been brought to my attention that I may have worded poorly a portion of the last answer. I think I answered the wrong (unasked) question. There is only 1 index db file per client, If a client is a backup client AND an HSM client for the same filesystem, there might be 2 index entries for some files (one for the backup pool and one for the migration pool) in the index db. Regarding the "splitting" issue, since the db's reside on the server, the only kinds of splitting I could see would be to have a single client, point at one server for backup services, and point at another server for HSM services. This would then generate separate index db's on each server. Yes, I do believe you should be able to do this. sorry if I caused any confusion. steve.
722.3	confused no but I had hoped ...	BRSADV::BUGGENHOUT		`Mon Jun 02 1997 08:47`	16
	Steve, The separate indexes for HSM and backup are an important issue for us as the customer has quit some data. The data is on the server itself and therefore the hsm/backup client is the server. The data are a thousand of small files so the index will be big. Splitting for hsm and backup could be easy to put them on seperate filesystems, or loosing backup index would not directly impact hsm ... This customer story will show up in your mailbox as we (Jurge Klezedjenski and I) had same extra details/technical issues on the index sizes regina