Correct - the cumulative incremental uses the "full" effectively as an exclude 
list for your backup; a diff inc would use the full + any intervening 
incrementals as an exclude list. The point being it's only required at the time 
of backup.

What it does mean is that, if your original full expires, you can only restore 
the files captured by the still active incremental.

Synthetics are entirely different; they still only require the full and 
subsequent incrementals at "backup time" - they combine these previous backups 
to build a file list and then generate the new backup pulling the data from the 
old full and incrementals as required to complete the new image. Once completed 
the old fulls/incrementals are no longer needed.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Lightner, Jeff
Sent: 16 October 2012 21:44
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 78, Issue 7

I don't think so.   I believe the relevance of incremental to full is only at 
backup time and the catalogs would have no reason to keep track of them after 
that.

Each backup is a separate image so while the incremental needs to know what was 
on the full to determine WHAT TO BACKUP it does not need to know that to 
determine WHAT TO RESTORE - it simply restores whatever is in the incremental 
image (or any subset of information you tell it to restore from the image).   
As I noted earlier the INTENT is to do such restores AFTER a full restore but 
there is no requirement.   You can select any image to restore from at any 
time.   (You can restore a full without restoring the incremental and 
vice-versa.)   There could be occasions where the restore you want IS only the 
incremental (e.g. someone deleted a file created AFTER the most recent full 
that was backed up in an incremental - no reason to restore the full because it 
doesn't have the file anyway - just restore from that incremental.)

It might be different if you were doing synthetic backups though.    Such 
backups would of course have to keep track of all the underlying images.   I 
haven't played with those.

From: 
veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu]<mailto:[mailto:veritas-bu-boun...@mailman.eng.auburn.edu]>
 On Behalf Of Steve Quan
Sent: Tuesday, October 16, 2012 4:26 PM
To: veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
Subject: Re: [Veritas-bu] Veritas-bu Digest, Vol 78, Issue 7

I would have expected NBU to *keep* the info about the full backup until the 
subsequent differentials/incrementals have expired, however, I believe that NBU 
would determine that the "cleaned out" files from it's DB (expired) have not 
been backed up, and include them in a subsequent incremental, or whatever is 
based on that full (fun to track :)

/Steve
> From: 
> veritas-bu-requ...@mailman.eng.auburn.edu<mailto:veritas-bu-requ...@mailman.eng.auburn.edu>
> Subject: Veritas-bu Digest, Vol 78, Issue 7
> To: 
> veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
> Date: Tue, 16 Oct 2012 12:00:09 -0500
>
> Send Veritas-bu mailing list submissions to
> veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> or, via email, send a message with subject or body 'help' to
> veritas-bu-requ...@mailman.eng.auburn.edu<mailto:veritas-bu-requ...@mailman.eng.auburn.edu>
>
> You can reach the person managing the list at
> veritas-bu-ow...@mailman.eng.auburn.edu<mailto:veritas-bu-ow...@mailman.eng.auburn.edu>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Veritas-bu digest..."
>
>
> Today's Topics:
>
> 1. Incremental backup question (Whelan, Patrick)
> 2. Re: Incremental backup question (Lightner, Jeff)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 16 Oct 2012 13:57:19 +0000
> From: "Whelan, Patrick" 
> <patrick.whe...@baml.com<mailto:patrick.whe...@baml.com>>
> Subject: [Veritas-bu] Incremental backup question
> To: 
> "veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>"
> <veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>>
> Message-ID:
> <D463AE619BD5C34C83282CD821B8760D0FF772@smtp_mail.bankofamerica.com<mailto:D463AE619BD5C34C83282CD821B8760D0FF772@smtp_mail.bankofamerica.com>>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
> I suppose the answer is obvious, but I'm having trouble getting my head 
> around it.
> What happens to an incremental backup whose dependent full has expired.
> For example
> A full backup is run and expires in 90 days. 89 Days later an cumulative 
> incremental is run and expires in 30 days. Two days later the Full expires. 
> Is the incremental still useful? If so, to what extent.
>
> Regards,
>
> Patrick Whelan
> Senior NetBackup Specialist
> +44 (0)207 995 9715
>
> ----------------------------------------------------------------------
> This message w/attachments (message) is intended solely for the use of the 
> intended recipient(s) and may contain information that is privileged, 
> confidential or proprietary. If you are not an intended recipient, please 
> notify the sender, and then please delete and destroy all copies and 
> attachments, and be advised that any review or dissemination of, or the 
> taking of any action in reliance on, the information contained in or attached 
> to this message is prohibited.
> Unless specifically indicated, this message is not an offer to sell or a 
> solicitation of any investment products or other financial product or 
> service, an official confirmation of any transaction, or an official 
> statement of Sender. Subject to applicable law, Sender may intercept, 
> monitor, review and retain e-communications (EC) traveling through its 
> networks/systems and may produce any such EC to regulators, law enforcement, 
> in litigation and as required by law.
> The laws of the country of each sender/recipient may impact the handling of 
> EC, and EC may be archived, supervised and produced in countries other than 
> the country in which you are located. This message cannot be guaranteed to be 
> secure or free of errors or viruses.
>
> References to "Sender" are references to any subsidiary of Bank of America 
> Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
> Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
> Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
> Government Agency. Attachments that are part of this EC may have additional 
> important disclosures and disclaimers, which you should read. This message is 
> subject to terms available at the following link:
> http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
> consent to the foregoing.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20121016/18226d86/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Tue, 16 Oct 2012 15:27:29 +0000
> From: "Lightner, Jeff" <jlight...@water.com<mailto:jlight...@water.com>>
> Subject: Re: [Veritas-bu] Incremental backup question
> To: 
> "veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>"
> <veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>>
> Message-ID: 
> <040b89c8b1e1d945ae2700c511a039e9230...@atmexdb03.dsw.net<mailto:040b89c8b1e1d945ae2700c511a039e9230...@atmexdb03.dsw.net>>
> Content-Type: text/plain; charset="utf-8"
>
> The incremental will have any files it backed up still on it and those can be 
> restored. However unless most of your files change on a daily basis you?re 
> not likely to have most of the files in the incremental.
>
> That is to say that a full OR an incremental CAN be restored without respect 
> to the other backups but the INTENT is that the full be restored first then 
> the subsequent incrementals (or a single cumulativeincremental) since that 
> full should be restored on top of it to get the changes since the full.
>
> If the full expired but the media it was written on has not been reused you 
> can re-import the full and then restore it. The re-import will change the 
> expiration date relative to the date of import rather than the date of backup.
>
>
>
>
>
> From: 
> veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
>  
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu]<mailto:[mailto:veritas-bu-boun...@mailman.eng.auburn.edu]>
>  On Behalf Of Whelan, Patrick
> Sent: Tuesday, October 16, 2012 9:57 AM
> To: 
> veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
> Subject: [Veritas-bu] Incremental backup question
>
> Hi All,
>
> I suppose the answer is obvious, but I?m having trouble getting my head 
> around it.
> What happens to an incremental backup whose dependent full has expired.
> For example
> A full backup is run and expires in 90 days. 89 Days later an cumulative 
> incremental is run and expires in 30 days. Two days later the Full expires. 
> Is the incremental still useful? If so, to what extent.
>
> Regards,
>
> Patrick Whelan
> Senior NetBackup Specialist
> +44 (0)207 995 9715
>
> ________________________________
> This message w/attachments (message) is intended solely for the use of the 
> intended recipient(s) and may contain information that is privileged, 
> confidential or proprietary. If you are not an intended recipient, please 
> notify the sender, and then please delete and destroy all copies and 
> attachments, and be advised that any review or dissemination of, or the 
> taking of any action in reliance on, the information contained in or attached 
> to this message is prohibited.
> Unless specifically indicated, this message is not an offer to sell or a 
> solicitation of any investment products or other financial product or 
> service, an official confirmation of any transaction, or an official 
> statement of Sender. Subject to applicable law, Sender may intercept, 
> monitor, review and retain e-communications (EC) traveling through its 
> networks/systems and may produce any such EC to regulators, law enforcement, 
> in litigation and as required by law.
> The laws of the country of each sender/recipient may impact the handling of 
> EC, and EC may be archived, supervised and produced in countries other than 
> the country in which you are located. This message cannot be guaranteed to be 
> secure or free of errors or viruses.
>
> References to "Sender" are references to any subsidiary of Bank of America 
> Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
> Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
> Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
> Government Agency. Attachments that are part of this EC may have additional 
> important disclosures and disclaimers, which you should read. This message is 
> subject to terms available at the following link:
> http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
> consent to the foregoing.
>
>
>
>
>
> Athena?, Created for the Cause?
>
> Making a Difference in the Fight Against Breast Cancer
>
>
>
>
>
> How and Why I Should Support Bottled Water!
> Do not relinquish your right to choose bottled water as a healthy alternative 
> to beverages that contain sugar, calories, etc. Your support of bottled water 
> will make a difference! Your signatures count! Go to 
> http://www.bottledwatermatters.org/luv-bottledwater-iframe/dswaters and sign 
> a petition to support your right to always choose bottled water. Help fight 
> federal and state issues, such as bottle deposits (or taxes) and 
> organizations that want to ban the sale of bottled water. Support community 
> curbside recycling programs. Support bottled water as a healthy way to 
> maintain proper hydration. Our goal is 50,000 signatures. Share this petition 
> with your friends and family today!
>
>
>
> ---------------------------------
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
> information and is for the sole use of the intended recipient(s). If you are 
> not the intended recipient, any disclosure, copying, distribution, or use of 
> the contents of this information is prohibited and may be unlawful. If you 
> have received this electronic transmission in error, please reply immediately 
> to the sender that you have received the message in error, and delete it. 
> Thank you.
> ----------------------------------
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20121016/a677c424/attachment-0001.htm
>
> ------------------------------
>
> _______________________________________________
> Veritas-bu maillist - 
> Veritas-bu@mailman.eng.auburn.edu<mailto:Veritas-bu@mailman.eng.auburn.edu>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
> End of Veritas-bu Digest, Vol 78, Issue 7
> *****************************************
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to