qinghe46
2 Iron

question about nsrck and scanner

Jump to solution

I know:

If save set passes browse policy, we can use nsrck -L7 or scanner to retrive the its index entry.

And if save set passes retention policy, we can also use nsrck -L7 or scanner to retrive the its index and media database entry.

question:

Is it necessary to use nsrmm to change its browse and retention policy every time before using nsrck -L7 or scanner? If it is not necessary every time, then when is necessary to do that?

my concern is if we do not use nsrmm to change its browse and retention policy first, even if we retrived index and media database entry by using nsrck -L7 or scanner, it will soon become recoverable or recyclable again because its browse and retention policy remained in a previous date. Or will the browse and retention policy be changed automatically after using nsrck -L7 or scanner? If so, how can that be changed?

0 Kudos
1 Solution

Accepted Solutions
masonb
3 Zinc

Re: question about nsrck and scanner

Jump to solution

Ok lets break it down here: -

Scanner has two main functions - one to reintroduce a volume into the Media Database (MDB), if deleted accidentally or volume from another Datazone. The other is to rebuild client file index (CLI) entries from savesets which are present on a volume which is known but we either do not have an index backup anymore (therefore nsrck cannot be used to repopulate the index) or its quicker to use scanner than recall other volumes etc.

nsrck will recover an index backup (not the original saveset but the index entries for that client/s backup which belong to the NetWorker server not the client) which were present on a specific day.

mminfo can report the status of saveset backups and tell us if the details regarding the files/dirs are still available and if the original backup was successful or not. This is via the cE - which is complete and eligible for recycling volume can be reused at any time but MDB entries still exist for this backup, cr - not passed its retention time but passed browse period therefore CLI entries have been removed and cb - all entries in MDB and CLI are present therefore detailed recovery is possible.

nsrmm can be used to manage media contents. There are two main rules for the -e and -w flags: -

-e You cannot set a retention shorter than a browse period.

-w Once a saveset becomes recoverable the browse time cannot be changed.

for the -w this doesn't mean a saveset cannot transition from cr to cb - it means the nsrmm command cannot do this as this alone would not recreate the CLI entries required - this is why scanner/nsrck are used to perform this function.

You can change browse/ret periods if they are in cb status as all the entries required are in the CLI and will be retained for the new times you set.

The 23 hrs reference is made to the internal housekeeping job which NetWorker runs to maintain its CLI and MDB entries but this is a max time. The behaviour changed from 7.3.x of Networker and after this we seen when the retention/browse period is not changed then the entries are deleted almost immediately so detailed recovery was not possible after scanner/nsrck commands and is why this procedure was published.

Regards,

Bill Mason

View solution in original post

0 Kudos
8 Replies
ble1
7 Thorium

Re: question about nsrck and scanner

Jump to solution

You need to use nsrmm when retention period has passed. When only browse period has passed, it will be reseted by nsrck command.

qinghe46
2 Iron

Re: question about nsrck and scanner

Jump to solution

Thanks for the info. Do you know how it will be reseted by nsrck command? What's the rule? Another 1 month by default? Or according to the browse policy set in client resource?

0 Kudos
nmc2
3 Argentum

Re: question about nsrck and scanner

Jump to solution

Refer to this link. You may find it useful.

http://solutions.emc.com/EMCSolutionView.asp?id=esg98649&usertype=C

Regards,

Prajith

0 Kudos
qinghe46
2 Iron

Re: question about nsrck and scanner

Jump to solution

Thank you but I have already read this. The article does not mention how the original browse time will be changed after using nsrck or scanner to retrive index for save set in cE or cr status.

0 Kudos
masonb
3 Zinc

Re: question about nsrck and scanner

Jump to solution

The support solution details how nsrmm is used to reset the browse/retention period. nsrck and scanner do not do this. Scanner will repopulate the media database (if volume info is not there already) and or client file index entries as will recovery of the index information via nsrck.

The change for the browse/retention time is there to stop NetWorker removing the entries again as without this step the backup data (index or saveset) would be still considered as "not required" as it was passed the time we need to keep the details for.

In your example where the flags are cE this means that the retention period has also expired therefore this needs to be reset also. Once a saveset is marked as recoverable you cannot change the browse time directly with nsrmm -w, therefore you have to use nsrmm -e command to make the saveset browsable again.

Hope this helps.

Bill Mason

0 Kudos
qinghe46
2 Iron

Re: question about nsrck and scanner

Jump to solution

In your example where the flags are cE this means that the retention period has also expired therefore this needs to be reset also.  Once a saveset is marked as recoverable you cannot change the browse time directly with nsrmm -w, therefore you have to use nsrmm -e command to make the saveset browsable again.

Hope this helps.

Bill Mason

really? once a saveset is marked as recoverable, I cannot use nsrmm -w to change the browse time? nsrmm -e is to change retention time, how will it make the saveset browsable again?

0 Kudos
qinghe46
2 Iron

Re: question about nsrck and scanner

Jump to solution

Told by a networker engineer:

nsrck and scanner will not change browse and retention time, just change the sumflags from cE to cr or cr to cb.

nsrim will check the browse time and retention time every 23 hours. So if not using nsrmm to change browse time and retention time within 23 hours, since browse time/retention time remained in a previous date, it will find browse time/retention time passes again and reset sumflags from  cr to cE or cb to cr. So after using nsrck/scanner, either recover the data within 23 hours or use nsrmm to change browse time and retention time within 23 hours.

Not sure this is a correct explaination or not. This is not an easy topic.

0 Kudos
masonb
3 Zinc

Re: question about nsrck and scanner

Jump to solution

Ok lets break it down here: -

Scanner has two main functions - one to reintroduce a volume into the Media Database (MDB), if deleted accidentally or volume from another Datazone. The other is to rebuild client file index (CLI) entries from savesets which are present on a volume which is known but we either do not have an index backup anymore (therefore nsrck cannot be used to repopulate the index) or its quicker to use scanner than recall other volumes etc.

nsrck will recover an index backup (not the original saveset but the index entries for that client/s backup which belong to the NetWorker server not the client) which were present on a specific day.

mminfo can report the status of saveset backups and tell us if the details regarding the files/dirs are still available and if the original backup was successful or not. This is via the cE - which is complete and eligible for recycling volume can be reused at any time but MDB entries still exist for this backup, cr - not passed its retention time but passed browse period therefore CLI entries have been removed and cb - all entries in MDB and CLI are present therefore detailed recovery is possible.

nsrmm can be used to manage media contents. There are two main rules for the -e and -w flags: -

-e You cannot set a retention shorter than a browse period.

-w Once a saveset becomes recoverable the browse time cannot be changed.

for the -w this doesn't mean a saveset cannot transition from cr to cb - it means the nsrmm command cannot do this as this alone would not recreate the CLI entries required - this is why scanner/nsrck are used to perform this function.

You can change browse/ret periods if they are in cb status as all the entries required are in the CLI and will be retained for the new times you set.

The 23 hrs reference is made to the internal housekeeping job which NetWorker runs to maintain its CLI and MDB entries but this is a max time. The behaviour changed from 7.3.x of Networker and after this we seen when the retention/browse period is not changed then the entries are deleted almost immediately so detailed recovery was not possible after scanner/nsrck commands and is why this procedure was published.

Regards,

Bill Mason

View solution in original post

0 Kudos