Hey guys,
I've got an interesting scenario I've been working on and I need some additional input.
We have a server (Windows 2003, NBU 5.1 MP5) with a large number of small files that rarely change. Differential backups don't work on the server because it takes too long looking for the next file to backup. Currently we run a Full backup bi-weekly and have a client side script that runs nightly and does a user-initiated backup on the last 3 days of files. The files are arranged by calendar date primarily.
Our Windows Admins would like to try something different, involving 'junction points' in NTFS. Apparently this will effectively store the files elsewhere and all we will need to do is backup the 'junctions'.
My initial testing resulted in NBU backing up the junction and the files behind it (not surprised as the client relies on the OS to get its files from). However, we were unable to restore from those backups; the restore would re-create the junction/folder but couldn't restore anything past that. Not really a problem though, as the actual files are elsewhere anyway and will be backed up from there. The problem is that the backup actually got the files though.
So, the present spin on the scenario is: they want me to only backup the 'junctions' (they appear to be directories to the OS). My first thought was to use Exclude/Include lists. Not much luck so far, unfortunately.
The file structure is thus:
G:\SourceDir\DateDirs\Data
The 'junction' is going to be the 'DateDir' level directories; there are tons of these (one for each day).
How would you setup an Exclude/Include combination to backup only those directories?
I've tried some testing but have only succeeded in getting a first level directory.
Ie: Exclude G:\ and Include G:\Temp = backup of G:\Temp directory (and nothing inside it).
Testing an include of: G:\Temp\Test1 results in 0 files backed up.
Same thing with wildcards and various combinations of '\' adding.
Any ideas out there?
DP