Or, incremental vs. differential - the former being a backup of changed files since the last full OR partial, and the latter being a backup of changed files since the last full.

Gilles Schipper 
Sent via mobile
416-702-7900

> On Apr 3, 2017, at 5:16 PM, Johnson, Tracy <[log in to unmask]> wrote:
> 
> I think what Donna refers to are the terms "incremental" versus "partial".  The terms somewhat specific to the backup software of your choice.
> 
> (Also not sure which is which anymore, since I use neither ability.)
> 
> Tracy Johnson
> +00 1 757 766-4318 tel
> +00 1 757 755-6470 mobile
> Hampton, Virginia, U.S.
> [log in to unmask]
> 
>> -----Original Message-----
>> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
>> Of Donna Hofmeister
>> Sent: Monday, April 03, 2017 4:59 PM
>> To: [log in to unmask]
>> Subject: Re: [HP3000-L] partial backups
>> 
>>> On Sat, Apr 1, 2017 at 10:53 AM, Jim Ryan <[log in to unmask]> wrote:
>>> 
>>> we do full backups every night and i wanted to change to partials
>>> during the week and a full on Sunday. what is the option for this? thank
>> you.
>>> 
>> 
>> Since everyone seems to be running in circles on answering this question....
>> 
>> First, you need to decide what kind of partial you want to do.  On Tuesday,
>> do you want to backup all files changed since Sunday's full backup or do you
>> want to backup all files changed since Monday's backup?  (and so on....)
>> 
>> There are some things to think about here.
>> 
>> If your "line in the sand" is always Sunday -- then you have to deal with
>> knowing that by Friday/Saturday your "partial" backup is likely going to be
>> sizeable and will take longer to run.  Otoh, if you ever have to do a *big*
>> restore, your restore plan is plan is pretty simple -- you'll need your last
>> partial and your last full backup.
>> 
>> If your "line in the sand" is always "yesterday" -- then your "partial"
>> backups will be relatively small and quick but the flip-side is your *big*
>> restore could be very complicated since you'll need every partial back
>> through Monday plus your full backup.
>> 
>> Fwiw, I think most people set the backup date as "Sunday" and do partials
>> from there.
>> 
>> The technical bit that you're really asking about is:
>> 
>>          restore ....;date>=!my_lastfull
>> 
>> "!my_lastfull" is (hopefully obviously) a CI variable that contains a date
>> in "mm/dd/[yy]yy" format.  This is a value that your *full backup job* needs
>> to establish.  So your full backup job should do something like:
>> 
>>          file lastfull,old
>>          echo !hpmonth/!hpday/!hpyear>*lastful
>> 
>> Your partial job will need to do something like this:
>> 
>>          file lastfull,old
>>          input my_lastfull < *lastfull
>> 
>> There's plenty of logic that needs to be added to the above examples.
>> (You'll note that there is NO error checking/what-if handling, etc.)  This
>> should be enough to get you started.
>> 
>> Btw, the following is the link for the latest store manual:
>> 
>> http://www.teamnaconsulting.com/compresources/pdfs/B5151-90003.pdf
>> 
>>      - donna
>> 
>> --
>> Donna Hofmeister
>> Allegro Consultants, Inc.
>> 408-252-2330
>> Visit us on Linkedin
>> <https://www.linkedin.com/company/allegro-consultants-inc->
>> Like us on Facebook <http://www.facebook.com/allegroconsultantsinc>
>> 
>> * To join/leave the list, search archives, change list settings, *
>> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *