Re: [Veritas-bu] Question about synthetic backups
On Thu, Feb 21, 2008 at 11:10:21PM -0800, dbergen wrote: > > If all you are looking for is another copy of the full backup you have, > > then just run > > > > bpduplicate -dp -backupid > > > > Yes, I can do that easily enough but how do I automatically schedule such an > action (without a Vault license)? I would do it outside of NBU (cron). It would probably be wrapped in something that would have enough smarts to "do the right thing" if the correct full backup hadn't actually been created due to failure or something. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area < This line left intentionally blank to confuse you. > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
I too want to thank all for the feedback as it has made the manual much clearer to me. I also apologize for apparently muddying the waters that I did not intentionally mean to do and deter from Mr. Bergen's original question. Regards -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dbergen Sent: Friday, February 22, 2008 12:10 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question about synthetic backups Thanks for all the feedback, see some more replies below. > We disagree on what a true synthetic backup is and how it is implemented. No, we don't disagree at all, I wasn't stating opinion, I was just saying how Netbackup handles a synthetic. > If all you are looking for is another copy of the full backup you have, then just run > > bpduplicate -dp -backupid > > Yes, I can do that easily enough but how do I automatically schedule such an action (without a Vault license)? > As to TOP's question, have you tried running a full, then a series of > incrementals, THEN a syn full or cumulative incremental? That's what > it's designed for. Why would you make a syn full from a full? The > results would be the same a duplication of that same backup, with a lot > more work. The use of it without any fulls is pointless enough that the > program is probably just barfing and saying "what are you doing? You > don't have any incrementals to merge into a full! All you have is a > full! Why don't you just copy it?" > I understand what you are saying here, my question is about the logic of WHY it worked that way. The way it is is how I already understood it to work. What I am trying to say (obviously poorly) is that if I: 1. Make a FULL synth to the onsite tape pool. 2. Want another FULL from the same time written to the offsite tape pool at a later date but BEFORE another incremental has taken place, I can't seem to do it, other than with Vault. What I was trying to get an answer to is... Shouldn't Netbackup be smart enough to say "he is requesting another FULL, I just did one, BUT I see this one is to a different media pool so I will copy the most current full to the media pool as requested" > In order to create a Synthetic Full/Cumulative backup, NBU wants to have > on tape all of the files in the condition they currently exist on the > client being backed up. In order to do that, it must perform an > incremental. Otherwise you'd be creating a full backup based on files > that were backed up at some previous point in time, so your synthetic > backup would look like it was taken yesterday or before. Therefore, NBU > requires you to take an incremental just before. > Hmm... maybe things have changed in 6.5.1 as it doesn't require an incremental backup just before at all. You are free to make the synthetic at any time after the incremental, just with the understanding that your synth full will only be as current as you most recent incremental. > He's incorrectly (I believe) assuming that the Synthetic backup picks up > differential information from the client, in the process of creating the > Synthetic Full. > No, I understand how the synthetic works. > And RTFM is what the > original poster could have done rather than complain that NetBackup > doesn't work like TSM. > Huh? I never said anything of the sort and I HAVE read the manual, quite a bit of it actually. > Or whenever; there is no need for immediacy other than the synthetic > full (or synthetic cumulative) is only as current as the latest > incremental it uses. That's obvious, but I need to remind myself > periocially that I can schedule the synthetic when resources are > available rather than right after the last incremental component. Exactly, unlike what Chris said above this is one of the big pluses to Synthetics for me, I can generate the weekly full anytime over the next 3-4 days. Thanks everyone for the feedback, I will be changing one datacentre to almost totally synthetic backups next month and this is more great info. thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
> What I was trying to get an answer to is... Shouldn't Netbackup be smart > enough to say "he is requesting another FULL, I just did one, BUT I see > this one is to a different media pool so I will copy the most current full > to the media pool as requested" Maybe, but apparently not. ;) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Question about synthetic backups
Thanks for all the feedback, see some more replies below. > We disagree on what a true synthetic backup is and how it is implemented. No, we don't disagree at all, I wasn't stating opinion, I was just saying how Netbackup handles a synthetic. > If all you are looking for is another copy of the full backup you have, then > just run > > bpduplicate -dp -backupid > > Yes, I can do that easily enough but how do I automatically schedule such an action (without a Vault license)? > As to TOP's question, have you tried running a full, then a series of > incrementals, THEN a syn full or cumulative incremental? That's what > it's designed for. Why would you make a syn full from a full? The > results would be the same a duplication of that same backup, with a lot > more work. The use of it without any fulls is pointless enough that the > program is probably just barfing and saying "what are you doing? You > don't have any incrementals to merge into a full! All you have is a > full! Why don't you just copy it?" > I understand what you are saying here, my question is about the logic of WHY it worked that way. The way it is is how I already understood it to work. What I am trying to say (obviously poorly) is that if I: 1. Make a FULL synth to the onsite tape pool. 2. Want another FULL from the same time written to the offsite tape pool at a later date but BEFORE another incremental has taken place, I can't seem to do it, other than with Vault. What I was trying to get an answer to is... Shouldn't Netbackup be smart enough to say "he is requesting another FULL, I just did one, BUT I see this one is to a different media pool so I will copy the most current full to the media pool as requested" > In order to create a Synthetic Full/Cumulative backup, NBU wants to have > on tape all of the files in the condition they currently exist on the > client being backed up. In order to do that, it must perform an > incremental. Otherwise you'd be creating a full backup based on files > that were backed up at some previous point in time, so your synthetic > backup would look like it was taken yesterday or before. Therefore, NBU > requires you to take an incremental just before. > Hmm... maybe things have changed in 6.5.1 as it doesn't require an incremental backup just before at all. You are free to make the synthetic at any time after the incremental, just with the understanding that your synth full will only be as current as you most recent incremental. > He's incorrectly (I believe) assuming that the Synthetic backup picks up > differential information from the client, in the process of creating the > Synthetic Full. > No, I understand how the synthetic works. > And RTFM is what the > original poster could have done rather than complain that NetBackup > doesn't work like TSM. > Huh? I never said anything of the sort and I HAVE read the manual, quite a bit of it actually. > Or whenever; there is no need for immediacy other than the synthetic > full (or synthetic cumulative) is only as current as the latest > incremental it uses. That's obvious, but I need to remind myself > periocially that I can schedule the synthetic when resources are > available rather than right after the last incremental component. Exactly, unlike what Chris said above this is one of the big pluses to Synthetics for me, I can generate the weekly full anytime over the next 3-4 days. Thanks everyone for the feedback, I will be changing one datacentre to almost totally synthetic backups next month and this is more great info. thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
> You need to run a differential Or a synthetic cumulative, a cumulative or any combination that makes sense, cumulatives obviating the need for any earlier cumulatives or differentials. It's all in the Veritas NetBackup System Administrator's Guide | Policies | More about synthetic backups. And RTFM is what the original poster could have done rather than complain that NetBackup doesn't work like TSM. > and then a synthetic full immediately following. Or whenever; there is no need for immediacy other than the synthetic full (or synthetic cumulative) is only as current as the latest incremental it uses. That's obvious, but I need to remind myself periocially that I can schedule the synthetic when resources are available rather than right after the last incremental component. > [...] The "Synthetic Full" is a normal full image backup > according to Netbackup and gets used in the next Synthetic > Backup. I think there are issues with this related to > deleted files (differential backups don't realize that > something got deleted so the new full will have all the > deleted files) No, that's what TIR is for. You can't configure a synthetic without TIR+move in the policy. > so I would recommend "refreshing" the > synthetic with an actual full every so often. Any reason for that other than just getting used to trusting the computer with one more new task? Accurately determining synthetic content is something a human can do with pencil, paper and time; there is no magic or guesswork. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
He's incorrectly (I believe) assuming that the Synthetic backup picks up differential information from the client, in the process of creating the Synthetic Full. Paul -- > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Curtis Preston > Sent: February 20, 2008 4:04 PM > To: Haskins, Steve; VERITAS-BU@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Question about synthetic backups > > > As to TOP's question, have you tried running a full, then a series of > incrementals, THEN a syn full or cumulative incremental? That's what > it's designed for. Why would you make a syn full from a full? The > results would be the same a duplication of that same backup, > with a lot > more work. The use of it without any fulls is pointless > enough that the > program is probably just barfing and saying "what are you doing? You > don't have any incrementals to merge into a full! All you have is a > full! Why don't you just copy it?" La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
As to TOP's question, have you tried running a full, then a series of incrementals, THEN a syn full or cumulative incremental? That's what it's designed for. Why would you make a syn full from a full? The results would be the same a duplication of that same backup, with a lot more work. The use of it without any fulls is pointless enough that the program is probably just barfing and saying "what are you doing? You don't have any incrementals to merge into a full! All you have is a full! Why don't you just copy it?" To the question of what synthetic backups are for... The purpose of NetBackup's Synthetic Backups is to allow you create a full or cumulative incremental backup without having to transfer the files across the network. The definite benefits are reduction in load on the client and network, and that you can create the full/cumulative backup any time of the day -- you can't do that with regular fulls. It may or may NOT take shorter than a traditional full or cumulative incremental backup. IMHO, Symantec oversold the "quicker" aspects in the early days of Synthetics, and created a lot of unhappy people because in some circumstances they take longer. They're still BETTER (no load on the client or network, and run them at any time.) In order to create a Synthetic Full/Cumulative backup, NBU wants to have on tape all of the files in the condition they currently exist on the client being backed up. In order to do that, it must perform an incremental. Otherwise you'd be creating a full backup based on files that were backed up at some previous point in time, so your synthetic backup would look like it was taken yesterday or before. Therefore, NBU requires you to take an incremental just before. Bringing TSM into this comparison muddies the waters, IMHO. First, they have a completely different architecture that doesn't require fulls for filesystem backups. You have to do other things that NBU doesn't need to do, like reclamation, but you don't need to do fulls. The closest thing TSM has to a Synthetic Full Backup is a "Backup Set," also referred to as an "instant archive." A Backup Set is a self contained tape that can be read and restored from without the TSM database, and consequently, its contents are not stored in the TSM database. So a Backup Set cannot be used for regular operational restores inside TSM -- it is designed to be used outside TSM. When you compare a Backup Set to a Synthetic Backup, they are very similar. Perform a recent incremental, then create your Backup Set. Although TSM doesn't require it, it would be silly to do otherwise, unless you were trying to create an archive from several days ago. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies > -Original Message- > From: [EMAIL PROTECTED] [mailto:veritas-bu- > [EMAIL PROTECTED] On Behalf Of Haskins, Steve > Sent: Tuesday, February 19, 2008 7:02 PM > To: VERITAS-BU@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Question about synthetic backups > > CBergen, > > You're not the only one that would like some enlightenment...I mean, > on synthetics backups. I don't understand why incrementals have to be > continuously run at all. As I understand it, that is the point of > synthetic backups as to have a full and just backup the changes from > that point forward with synthetics? That is the way TSM's synthetic > backups work with the option of how many 'versions' to retain. I'm on > 5.1 (getting ready to upgrade to 6.5.1) so maybe synthetics are > different in 6.x? What is exactly done between the required incrementals > and the synthetics? Does each synthetic combine the previous two > incrementals and how; as a differential and then expire the two tapes > that were used for the incrementals (just an example if two were used)or > delete the incrementals images on the tapes OR disk? > > Regards, > Steve > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of dbergen > Sent: Tuesday, February 19, 2008 12:20 PM > To: VERITAS-BU@mailman.eng.auburn.edu > Subject: [Veritas-bu] Question about synthetic backups > > > When I attempt a synthetic backup and the most recent backup of the > client is a full backup nothing happens. > > Nothing happens because Netbackup says there was no incremental backup > to analyze. My question is: So What? > > I want another full backup, to a completely different volume pool, > shouldn't Netbackup realize that the volume pool is different and run > the synthetic backup again? > > Hopefully someone can tell me what I am doing wrong here. > > Thanks, > dbergen > > +-
Re: [Veritas-bu] Question about synthetic backups
It is set to 9 days, and I can't remember what the initial default was. I run the synthetic fulls each week, so 9 days gives me the overlap I want in case something happens and the synthetic doesn't run right on schedule. I keep two weeks of incrementals, and three fulls on this system. -Jon > Did you have to change your "Keep TIR Information" to longer than 1 day > in your Master server properties to get this to work? > > -Jonathan > > -Original Message- > From: Jon Bousselot [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 20, 2008 1:21 PM > To: Martin, Jonathan > Cc: VERITAS-BU@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Question about synthetic backups > > The synthetic full keeps track of moved and deleted files that occur > between incrementals. When the incrementals are assembled, the changes > are reflected in the new synthetic full. I just tested this to see for > myself. (ver 6.5) > > I believe this feature is enabled (and required) in the policy under the > label "collect true image restore information" and "with move > detection". > > I moved a subdirectory to a new directory level, and the incremental > backed up the entire contents of that moved data. It isn't smart enough > to see that the files were same just moved to a new home. Maybe > de-duplication will handle this in future versions. > > -Jon > > >> > You need to run a differential and then a synthetic full immediately >> > following. The synthetic basically takes your last full and applies >> > all the differentials to it to create a new "full" image. >> > >> > Full + Diff + Diff + Diff = Synthetic Full Synthetic Full + Diff + >> > Diff + Diff = Synthetic Full Synthetic Full + Diff + Diff + Diff = >> > Synthetic Full etc... >> > >> > The "Synthetic Full" is a normal full image backup according to >> > Netbackup and gets used in the next Synthetic Backup. I think there >> > are issues with this related to deleted files (differential backups >> > don't realize that something got deleted so the new full will have all >> > > >> > the deleted files) so I would recommend "refreshing" the synthetic >> > with an actual full every so often. >> > >> > >> > -Jonathan >> > >> > -Original Message- >> > From: [EMAIL PROTECTED] >> > [mailto:[EMAIL PROTECTED] On Behalf Of >> > dbergen >> > Sent: Tuesday, February 19, 2008 2:20 PM >> > To: VERITAS-BU@mailman.eng.auburn.edu >> > Subject: [Veritas-bu] Question about synthetic backups >> > >> > >> > When I attempt a synthetic backup and the most recent backup of the >> > client is a full backup nothing happens. >> > >> > Nothing happens because Netbackup says there was no incremental backup >> > > >> > to analyze. My question is: So What? >> > >> > I want another full backup, to a completely different volume pool, >> > shouldn't Netbackup realize that the volume pool is different and run >> > the synthetic backup again? >> > >> > Hopefully someone can tell me what I am doing wrong here. >> > >> > Thanks, >> > dbergen >> > >> > +- >> > +- >> > |This was sent by [EMAIL PROTECTED] via Backup Central. >> > |Forward SPAM to [EMAIL PROTECTED] >> > +- >> > +- >> > >> > >> > ___ >> > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu >> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> > >> > ___ >> > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu >> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >> > >> > >> > > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
Did you have to change your "Keep TIR Information" to longer than 1 day in your Master server properties to get this to work? -Jonathan -Original Message- From: Jon Bousselot [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 20, 2008 1:21 PM To: Martin, Jonathan Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question about synthetic backups The synthetic full keeps track of moved and deleted files that occur between incrementals. When the incrementals are assembled, the changes are reflected in the new synthetic full. I just tested this to see for myself. (ver 6.5) I believe this feature is enabled (and required) in the policy under the label "collect true image restore information" and "with move detection". I moved a subdirectory to a new directory level, and the incremental backed up the entire contents of that moved data. It isn't smart enough to see that the files were same just moved to a new home. Maybe de-duplication will handle this in future versions. -Jon > You need to run a differential and then a synthetic full immediately > following. The synthetic basically takes your last full and applies > all the differentials to it to create a new "full" image. > > Full + Diff + Diff + Diff = Synthetic Full Synthetic Full + Diff + > Diff + Diff = Synthetic Full Synthetic Full + Diff + Diff + Diff = > Synthetic Full etc... > > The "Synthetic Full" is a normal full image backup according to > Netbackup and gets used in the next Synthetic Backup. I think there > are issues with this related to deleted files (differential backups > don't realize that something got deleted so the new full will have all > the deleted files) so I would recommend "refreshing" the synthetic > with an actual full every so often. > > > -Jonathan > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > dbergen > Sent: Tuesday, February 19, 2008 2:20 PM > To: VERITAS-BU@mailman.eng.auburn.edu > Subject: [Veritas-bu] Question about synthetic backups > > > When I attempt a synthetic backup and the most recent backup of the > client is a full backup nothing happens. > > Nothing happens because Netbackup says there was no incremental backup > to analyze. My question is: So What? > > I want another full backup, to a completely different volume pool, > shouldn't Netbackup realize that the volume pool is different and run > the synthetic backup again? > > Hopefully someone can tell me what I am doing wrong here. > > Thanks, > dbergen > > +- > +- > |This was sent by [EMAIL PROTECTED] via Backup Central. > |Forward SPAM to [EMAIL PROTECTED] > +- > +- > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
The synthetic full keeps track of moved and deleted files that occur between incrementals. When the incrementals are assembled, the changes are reflected in the new synthetic full. I just tested this to see for myself. (ver 6.5) I believe this feature is enabled (and required) in the policy under the label "collect true image restore information" and "with move detection". I moved a subdirectory to a new directory level, and the incremental backed up the entire contents of that moved data. It isn't smart enough to see that the files were same just moved to a new home. Maybe de-duplication will handle this in future versions. -Jon > You need to run a differential and then a synthetic full immediately > following. The synthetic basically takes your last full and applies all > the differentials to it to create a new "full" image. > > Full + Diff + Diff + Diff = Synthetic Full > Synthetic Full + Diff + Diff + Diff = Synthetic Full > Synthetic Full + Diff + Diff + Diff = Synthetic Full > etc... > > The "Synthetic Full" is a normal full image backup according to > Netbackup and gets used in the next Synthetic Backup. I think there are > issues with this related to deleted files (differential backups don't > realize that something got deleted so the new full will have all the > deleted files) so I would recommend "refreshing" the synthetic with an > actual full every so often. > > > -Jonathan > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of dbergen > Sent: Tuesday, February 19, 2008 2:20 PM > To: VERITAS-BU@mailman.eng.auburn.edu > Subject: [Veritas-bu] Question about synthetic backups > > > When I attempt a synthetic backup and the most recent backup of the > client is a full backup nothing happens. > > Nothing happens because Netbackup says there was no incremental backup > to analyze. My question is: So What? > > I want another full backup, to a completely different volume pool, > shouldn't Netbackup realize that the volume pool is different and run > the synthetic backup again? > > Hopefully someone can tell me what I am doing wrong here. > > Thanks, > dbergen > > +-- > |This was sent by [EMAIL PROTECTED] via Backup Central. > |Forward SPAM to [EMAIL PROTECTED] > +-- > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
If all you are looking for is another copy of the full backup you have, then just run bpduplicate -dp -backupid Steve On Tue, Feb 19, 2008 at 3:20 PM, dbergen <[EMAIL PROTECTED]> wrote: > > When I attempt a synthetic backup and the most recent backup of the client > is a full backup nothing happens. > > Nothing happens because Netbackup says there was no incremental backup to > analyze. My question is: So What? > > I want another full backup, to a completely different volume pool, > shouldn't Netbackup realize that the volume pool is different and run the > synthetic backup again? > > Hopefully someone can tell me what I am doing wrong here. > > Thanks, > dbergen > > +-- > |This was sent by [EMAIL PROTECTED] via Backup Central. > |Forward SPAM to [EMAIL PROTECTED] > +-- > > > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
You need to run a differential and then a synthetic full immediately following. The synthetic basically takes your last full and applies all the differentials to it to create a new "full" image. Full + Diff + Diff + Diff = Synthetic Full Synthetic Full + Diff + Diff + Diff = Synthetic Full Synthetic Full + Diff + Diff + Diff = Synthetic Full etc... The "Synthetic Full" is a normal full image backup according to Netbackup and gets used in the next Synthetic Backup. I think there are issues with this related to deleted files (differential backups don't realize that something got deleted so the new full will have all the deleted files) so I would recommend "refreshing" the synthetic with an actual full every so often. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dbergen Sent: Tuesday, February 19, 2008 2:20 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question about synthetic backups When I attempt a synthetic backup and the most recent backup of the client is a full backup nothing happens. Nothing happens because Netbackup says there was no incremental backup to analyze. My question is: So What? I want another full backup, to a completely different volume pool, shouldn't Netbackup realize that the volume pool is different and run the synthetic backup again? Hopefully someone can tell me what I am doing wrong here. Thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
>From what I understand about synthetics, you have to have one "real" full backup, so there has to be a schedule with that type. Just run another non-synthetic full backup if all you want is a full Jared M. Seaton Recovery Administrator Mylan Inc. 304-554-5926 304-685-1389 (Cell) "dbergen" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 02/19/2008 09:52 PM Please respond to VERITAS-BU@mailman.eng.auburn.edu To VERITAS-BU@mailman.eng.auburn.edu cc Subject [Veritas-bu] Question about synthetic backups When I attempt a synthetic backup and the most recent backup of the client is a full backup nothing happens. Nothing happens because Netbackup says there was no incremental backup to analyze. My question is: So What? I want another full backup, to a completely different volume pool, shouldn't Netbackup realize that the volume pool is different and run the synthetic backup again? Hopefully someone can tell me what I am doing wrong here. Thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu == CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. == ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
I concur that the underlying reason and thus the point of synthetic backups is to shorten the backup window and reduce downtime and network bandwidth utilization (at least after the first full is completed). We disagree on what a true synthetic backup is and how it is implemented. Regards -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dbergen Sent: Tuesday, February 19, 2008 10:27 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question about synthetic backups I might be able to enlighten you some. I'm not sure the differences between synthetics in 5.1 and 6.5 as I am only using them in 6.5. You're close but not quite on the mark about synthetics. The point of the synthetic is to reduce server down time, shorten the backup window and reduce network utilization by creating NEW backups by combining the most recent FULL with ALL Differential backups newer than that FULL. The FULL and Diffs aren't altered in any way, you don't want them to be, you want to still be able to go back to them if you need to. The only thing that is synthetic about the synthetic backup is the fact that it didn't get the data directly from the server rather it got it from two or more previous backups. None of this helps my original question of course... +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Question about synthetic backups
I might be able to enlighten you some. I'm not sure the differences between synthetics in 5.1 and 6.5 as I am only using them in 6.5. You're close but not quite on the mark about synthetics. The point of the synthetic is to reduce server down time, shorten the backup window and reduce network utilization by creating NEW backups by combining the most recent FULL with ALL Differential backups newer than that FULL. The FULL and Diffs aren't altered in any way, you don't want them to be, you want to still be able to go back to them if you need to. The only thing that is synthetic about the synthetic backup is the fact that it didn't get the data directly from the server rather it got it from two or more previous backups. None of this helps my original question of course... +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question about synthetic backups
CBergen, You're not the only one that would like some enlightenment...I mean, on synthetics backups. I don't understand why incrementals have to be continuously run at all. As I understand it, that is the point of synthetic backups as to have a full and just backup the changes from that point forward with synthetics? That is the way TSM's synthetic backups work with the option of how many 'versions' to retain. I'm on 5.1 (getting ready to upgrade to 6.5.1) so maybe synthetics are different in 6.x? What is exactly done between the required incrementals and the synthetics? Does each synthetic combine the previous two incrementals and how; as a differential and then expire the two tapes that were used for the incrementals (just an example if two were used)or delete the incrementals images on the tapes OR disk? Regards, Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dbergen Sent: Tuesday, February 19, 2008 12:20 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question about synthetic backups When I attempt a synthetic backup and the most recent backup of the client is a full backup nothing happens. Nothing happens because Netbackup says there was no incremental backup to analyze. My question is: So What? I want another full backup, to a completely different volume pool, shouldn't Netbackup realize that the volume pool is different and run the synthetic backup again? Hopefully someone can tell me what I am doing wrong here. Thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Question about synthetic backups
When I attempt a synthetic backup and the most recent backup of the client is a full backup nothing happens. Nothing happens because Netbackup says there was no incremental backup to analyze. My question is: So What? I want another full backup, to a completely different volume pool, shouldn't Netbackup realize that the volume pool is different and run the synthetic backup again? Hopefully someone can tell me what I am doing wrong here. Thanks, dbergen +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu