![]() Only when the backup method selected is FULL - Back Up Files -Īllows incrementals and differentials using modified time,ĭIFFERENTIAL - Using modified time or INCREMENTAL - Using This option can only be used with NTFS volumes and Journal to determine which files have been modified since the lastįull backup. "Select this option if you want to use Windows’ NTFS Change Now for what you want to do, I am wondering if you choose the option - Use the Windows Change Journal if available The DIFFERENTIAL - Using modified time - should say the same thing. Now what that should say is "since the last full backup or last incremental" Includes all files that haveĬhanged (based on the archive bit) since the last full backup, and does not affect any media rotation scheme because the archive bit is not reset. What I say this is - the manual for Differential using archive bit says:-ĭIFFERENTIAL - Changed Files. I would say this is a typo - or maybe Veritas thinks that what you are trying to do is overly complex? Possibly is? charles RE: Does "Differential/Modified time" works as advertised? justin2000 (MIS) 16 Oct 04 08:07 The manual clearly states this, but in my experiment it does not work as far as I can see. The key issue here that the weekend differential must backup all files since the last full, else there's not much point. This way I get a fairly good balance with backup times, the amount of data I have to retain, while at the same time get a reasonably low number of restores I have to do in case I lose an entire volume or server. Repeat for two more weeks until on the fourth weekend you do another full. My other angle on this is a backup scheme I use for NetWorker, and by reading the manual for Backup Exec I figured I could adapt it for use with Backup Exec, although slightly simpler.ĭo a modifired time differential next weekend. So my question is part academic, to find out if Backup Exec also can do this. Legato NetWorker, HP Data Protector and Veritas NetBackup come to mind. Many other backup packages have this feature. RE: Does "Differential/Modified time" works as advertised? justin2000 (MIS) 16 Oct 04 03:23 ![]() I backup to disk, but that shouldn't make any difference. I access the files through the default share, not through any user defined share. I use the same selection list for all three jobs (full, incr, diff). I'm at Backup Exec 9.1 sp1, I updated the RAWS on my target server as well. The point to my experiment was to make sure the new version of a differential backup would infact backup all modified files since last _full_, regardless of any incrementals inbetween. Had I used the older method, where an incremental resets the archive bit I would fully agree that a following differential backup would not backup anything, since it uses the archive but. I interpret this to mean that a "DIFFERENTIAL - Using modified time" backup should in my case now backup 30% of the files. According to the manual, this should backup all changed files since the last full backup. Now I did a "DIFFERENTIAL - Using modified time". I did this in total of three times, and each incremental backup generated 10%, as expected. I also repeated the "INCREMENTAL - Using modified time" backup. I repeated the touch process, but I made sure I touched a different 10% of the files. I then did a "INCREMENTAL - Using modified time" and as expected I backed up the same 10% of the files. I then used a small "touch" utility to update the last modify time on 10% of the files. I created a folder with 10.000 48k files and did a "FULL - Back Up Files - Allow incrementals and differentials using modified time". ![]() One thing I noticed is the feature of using Full, incremental and differential backups based on modified time instead of the old way of using the archive bit. I haven't used Backup Exec for quite a few years, but recently I've started to delve into what the latest version 9.1 brings to the table. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |