5 Posts

February 10th, 2012 15:00

Well sometimes the dirs are know/fixed. But that sorta my question. How do you deal with the unknows.....

If the 'good' data was always located in a known sub dir that would work well. THe problem is the files are loose in the 'backups' dir along with other files. These all large makesysb files as to why I'm being selective vs just grabbing them all...

That said... I solved my own problem....   I'm not stating that this is a good solution for all as there may be some gotchas in some cases, in my case this will work fine..

I'm still not really happy that there doesn't seem to be a simple way to do this but here is what i did:

<< /backups >>

    mtimeasm: *keyword*.*

    +skip: .?* *

The Modified Time ASM looks at the MTIME vs INODE time, so it essentially has to 'look' at what ever mask is provicded. In my case I could care less about INODE or symlink updates.

I verified that this works exactly as I wanted it to..  It grabed 8 out of 100 large files.  

57 Posts

February 9th, 2012 23:00

Is there any fixed name for the directories that come and go. If so then you can skip all of them using wild characters in global directives.

Other wise if there are only certain directores which you want to backup, you can use the always keyword in directive to backup those and skip the rest of the data.

Please refer to the NetWorker administration guide for more details on directives.

No Events found!

Top