Incremental backups not working for drives mounted to directories.
Updated: 27 May 2010 | 2 comments
I have some directories under C:\mnt which do not change - they have a fixed created/modified date.
I then mount some volumes to these directories, turning them into NTFS junctions:
C:\>dir c:\mnt
Volume in drive C has no label.
Volume Serial Number is 29CD-179E
Directory of c:\mnt
27/11/2009 03:50 AM <DIR> .
27/11/2009 03:50 AM <DIR> ..
27/11/2009 03:28 AM <JUNCTION> SCO-FILE1-F [\??\Volume{85de6ca8-daa7-11de-93aa-0019bbc8e994}\]
27/11/2009 03:50 AM <JUNCTION> SCO-FILE1-G [\??\Volume{85de6ca9-daa7-11de-93aa-0019bbc8e994}\]
26/11/2009 07:02 PM <JUNCTION> SCO-SQL1-E [\??\Volume{85de6ca1-daa7-11de-93aa-0019bbc8e994}\]
0 File(s) 0 bytes
5 Dir(s) 20,186,116,096 bytes free
The problem is that both the Full Backup and the Incremental Backup wind up backing up all the files!
What I wanted was for the incrementals to just contain the changed data.
I am attempting to use Synthetic Backups for this, so I wonder whether the extra attributes it gathers might be affecting the outcome? See:
http://www.symantec.com/connect/forums/aofo-error-be-server-aofo-not-selected-iscsi-snapshots-mounted
Any idea how I might be able to solve this?
Thanks,
Simon.
discussion Filed Under:
Comments
What sort of Operating System
What sort of Operating System holds these mount points (slight concern based on the SCO name showing in the list) If it is a form of Unix/Linux mounted on Windows (over SAMBA or similar) then it is possible that Incremental backups will function as full backups.
sorry!
sorry - lol! SCO is short for a place name; all servers are Windows Server 2008 (x64).
The LUNs are mounted via software iSCSI.
Would you like to reply?
Login or Register to post your comment.