[Networker] Questions on backup renamed directories attribute?

Hi,

Three questions on the 'Backup renamed directories' attribute:

1. If you turn on the 'Backup renamed directories' attribute for aclient then under what circumstances *might* 'save -i' (backup commandattribute) not work as expected?

Is it because NW first walks through the save set (save set path or filesystem) to generate a list of what it needs to back up, including pathnames to .nsr files that will be ignored (when using save -i), but thenonce it's done and it then starts its backups, maybe someone mightrename a directory containing a .nsr file, but NW doesn't have that pathto that .nsr file in its list so it doesn't ignore it but insteadcarries out the instructions in that .nsr file, effectively negating the'-i' option for the save, at least in that situation? Something likethat, maybe?

What would be a better way to handle this, if you wanted to ingore all.nsr files under the save set but still have 'Backup renameddirectories' turned on? Just create a server side directive, like:


<< /saveset >>
ignore

as opposed to using 'save i' in the 'backup command' field?

2. Why does enabling this attribute cause the save program to perform alookup in the CFI in order to determine if a directory have been renamed?

Normally, NW is looking at the ctimes of the files and comparing theseagainst the value stored in the media database for the affected save setfor the previous backup. I would think the CFI would only be read whendoing recovers, so if a directory is renamed, then its ctime willchange, and if NW knows that the ctime has changed then why not justback up everything under there without having to check the client fileindex?

3. What happens if you have this attribute turned on, but you're writingyour data to a non-indexed pool?

Would this just be equivalent to not having it turned on and stillwriting it to a non-indexed pool?


Thanks.

George

--
George Sinclair
Voice: (301) 713-3284 x210
- The preceding message is personal and does not reflect any official or 
unofficial position of the United States Department of Commerce -
- Any opinions expressed in this message are NOT those of the US Govt. -