Salta al contenuto principale

Non-stop Backup and Large Database Files

Thread needs solution

I am thinking of reorganising my system to use NSB. I have some very large database files. If I add a new record, then the mofication date of the file will change - but not the size of the file or its creation date. What will NSB do in this case? Does it ignore the change in modification date? Does it create a new backup copy of the (very large) file? Does it create copies of the modified sectors of the file?

This also applies to some smaller files such as iTunes Library, Adobe Lightroom Library, etc... all files which do not change fundamentally, but their contents do change.

0 Users found this helpful

ATI bases the need to backup based on a sector being changed, not file date or size. If a sector has been touched, then it will backup the associated file. This is why, if you make a backup, don't change any files but defrag a disk, ati will then find lots to backup again.

Well, that was pretty clear-cut. So if I have a 75GB data file and change one record, then it will back up not just that sector(s) which has changed, but the entire 75GB. I suppose it would be asking a bit much of non-enterprise software to do otherwise.

I am looking at NSB to avoid having these incredibly long backups of the 1TB++ disks, but it would clearly fill up the available NSB Storage quite quickly.

I might have misspoke. The changed sector would get backed up and so would the relevant file meta data sectors since the sectors containing the metadata would also be changed (file date, for one example).