Re: [Veritas-bu] Synthetic backups failing with 610

2013-06-05 Thread pranav batra
Hello
Yes we created new policy ,repeated the whole process. Taking manual full 
followed by incremental and then Synthetic.I have now verified the manual full 
images and media verify failed.
I can see the full backup as successful backup but media verify failed and thus 
synthetic backups are failing.
Now this is something new to troubleshoot.
PranavB

To: pranav_vent...@hotmail.com
Subject: RE: [Veritas-bu] Synthetic backups failing with 610
From: ken_zuf...@goodyear.com
Date: Wed, 5 Jun 2013 07:35:26 -0400

How often are you running the backups?
 If TIR information has dropped off for some reason, it can cause
a 610 as well.  They can also be generated if one of the backups has
expired (automatically or manually) before the next synthetic is scheduled.



Have you tried taking a new regular
full and starting the process again?



Ken Zufall

Operating Systems Administrator

D660C

The Goodyear Tire  Rubber Company

GTN 446.0592 or 330.796.0592









From:  
 pranav batra pranav_vent...@hotmail.com

To:  
 ken_zuf...@goodyear.com
ken_zuf...@goodyear.com, Veritas veritas-bu@mailman.eng.auburn.edu

Date:  
 06/05/2013 01:32 AM

Subject:
   RE: [Veritas-bu]
Synthetic backups failing with 610








We are only trying to synthesize full and
differential. We are not taking cumulative and still backup is failing
with 610.



Thanks,

PranavB




To: sm...@peppas.gr

CC: pranav_vent...@hotmail.com; veritas-bu@mailman.eng.auburn.edu

Subject: RE: [Veritas-bu] Synthetic backups failing with 610

From: ken_zuf...@goodyear.com

Date: Tue, 4 Jun 2013 10:45:50 -0400



No, that configuration doesn't work either.  You're limited to a single
synthetic schedule per policy. 



Ken Zufall

Operating Systems Administrator

D660C

The Goodyear Tire  Rubber Company

GTN 446.0592 or 330.796.0592









From:sm...@peppas.gr


To:ken_zuf...@goodyear.com,
pranav_vent...@hotmail.com 

Cc:veritas-bu@mailman.eng.auburn.edu


Date:06/04/2013
10:15 AM 

Subject:RE:
[Veritas-bu] Synthetic backups failing with 610









But , 

I think that you can run differential incrementals and synthesize a cumulative
 backup. 

Then you can use the full and the latest synthetic cumulative and create
a new synthetic full. 

As you do not mix incremental and cumulative backups you are ok


  

stefanos 

  

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu]
On Behalf Of ken_zuf...@goodyear.com

Sent: Tuesday, June 04, 2013 2:33 PM

To: pranav_vent...@hotmail.com

Cc: veritas-bu@mailman.eng.auburn.edu

Subject: Re: [Veritas-bu] Synthetic backups failing with 610


  

We had a similar problem last year, discovered that the problem--for us,
anyways--is that you can't have mixed incrementals when using synthetics.
 For example, you can run differential incrementals and synthetic
fulls; you can run cumulative incrementals and synthetic fulls; but you
cannot run cumulative and differential backups and get successful synthetics.
 They will work for a single cycle (seed full, mixed incrementals,
synthetic full), but the next time a synthetic is attempted it will fail
with a 610. 



Took us months to figure that one out and that was working with Symantec
support. 



Ken Zufall

Operating Systems Administrator

The Goodyear Tire  Rubber Company









From:pranav
batra pranav_vent...@hotmail.com


To:Veritas
veritas-bu@mailman.eng.auburn.edu


Date:06/04/2013
02:53 AM 

Subject:[Veritas-bu]
Synthetic backups failing with 610


Sent by:veritas-bu-boun...@mailman.eng.auburn.edu
















Hello Geeks, 



I am here facing issues with synthetic backup.  There are 7-8 windows
2008 clients that are giving me issues with synthetic backup.


The backup is failing with 610.




1: (610) end point terminated with an error 



Environment : Master windows 2008 R2 -7.5.0.5


Client 7.5.0.5 -2008R2 



We are taking their backups on Pure Disk pool ( We have created MSDP ).
All the backups are happening over the WAN and thus we are using synthetic
backups for the weekends. 





FUll backups runs fine ,incremental runs file ,synthetic also does runs
fine but fails after running/writing few Gigs with 610.




1: (610) end point terminated with an error 





Not able to get any clue even from Symantec till now.




Any help would be appreciated.


Anyone else faced similar issue before.




Thanks, 

PranavB 

___

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] Synthetic backups failing with 610

2013-06-04 Thread pranav batra
Hello Geeks,
I am here facing issues with synthetic backup.  There are 7-8 windows 2008 
clients that are giving me issues with synthetic backup.The backup is failing 
with 610.
1: (610) end point terminated with an error 
Environment : Master windows 2008 R2 -7.5.0.5Client 7.5.0.5 -2008R2
We are taking their backups on Pure Disk pool ( We have created MSDP ). All the 
backups are happening over the WAN and thus we are using synthetic backups for 
the weekends.

FUll backups runs fine ,incremental runs file ,synthetic also does runs fine 
but fails after running/writing few Gigs with 610.
1: (610) end point terminated with an error 

Not able to get any clue even from Symantec till now.
Any help would be appreciated.Anyone else faced similar issue before.
Thanks,PranavB 
  ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic backups failing with 610

2013-06-04 Thread ken_zufall
We had a similar problem last year, discovered that the problem--for us, 
anyways--is that you can't have mixed incrementals when using synthetics. 
For example, you can run differential incrementals and synthetic fulls; 
you can run cumulative incrementals and synthetic fulls; but you cannot 
run cumulative and differential backups and get successful synthetics. 
They will work for a single cycle (seed full, mixed incrementals, 
synthetic full), but the next time a synthetic is attempted it will fail 
with a 610.

Took us months to figure that one out and that was working with Symantec 
support.

Ken Zufall
Operating Systems Administrator
The Goodyear Tire  Rubber Company




From:   pranav batra pranav_vent...@hotmail.com
To: Veritas veritas-bu@mailman.eng.auburn.edu
Date:   06/04/2013 02:53 AM
Subject:[Veritas-bu] Synthetic backups failing with 610
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu



Hello Geeks,

I am here facing issues with synthetic backup.  There are 7-8 windows 2008 
clients that are giving me issues with synthetic backup.
The backup is failing with 610.

1: (610) end point terminated with an error 

Environment : Master windows 2008 R2 -7.5.0.5
Client 7.5.0.5 -2008R2

We are taking their backups on Pure Disk pool ( We have created MSDP ). 
All the backups are happening over the WAN and thus we are using synthetic 
backups for the weekends.


FUll backups runs fine ,incremental runs file ,synthetic also does runs 
fine but fails after running/writing few Gigs with 610.

1: (610) end point terminated with an error 


Not able to get any clue even from Symantec till now.

Any help would be appreciated.
Anyone else faced similar issue before.

Thanks,
PranavB 
___
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] Synthetic backups failing with 610

2013-06-04 Thread smpt1
But ,

I think that you can run differential incrementals and synthesize a
cumulative  backup.

Then you can use the full and the latest synthetic cumulative and create a
new synthetic full. 

As you do not mix incremental and cumulative backups you are ok

 

stefanos

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of
ken_zuf...@goodyear.com
Sent: Tuesday, June 04, 2013 2:33 PM
To: pranav_vent...@hotmail.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Synthetic backups failing with 610

 

We had a similar problem last year, discovered that the problem--for us,
anyways--is that you can't have mixed incrementals when using synthetics.
For example, you can run differential incrementals and synthetic fulls; you
can run cumulative incrementals and synthetic fulls; but you cannot run
cumulative and differential backups and get successful synthetics.  They
will work for a single cycle (seed full, mixed incrementals, synthetic
full), but the next time a synthetic is attempted it will fail with a 610. 

Took us months to figure that one out and that was working with Symantec
support. 

Ken Zufall
Operating Systems Administrator
The Goodyear Tire  Rubber Company




From:pranav batra pranav_vent...@hotmail.com 
To:Veritas veritas-bu@mailman.eng.auburn.edu 
Date:06/04/2013 02:53 AM 
Subject:[Veritas-bu] Synthetic backups failing with 610 
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu 

  _  




Hello Geeks, 

I am here facing issues with synthetic backup.  There are 7-8 windows 2008
clients that are giving me issues with synthetic backup. 
The backup is failing with 610. 

1: (610) end point terminated with an error 

Environment : Master windows 2008 R2 -7.5.0.5 
Client 7.5.0.5 -2008R2 

We are taking their backups on Pure Disk pool ( We have created MSDP ). All
the backups are happening over the WAN and thus we are using synthetic
backups for the weekends. 


FUll backups runs fine ,incremental runs file ,synthetic also does runs fine
but fails after running/writing few Gigs with 610. 

1: (610) end point terminated with an error 


Not able to get any clue even from Symantec till now. 

Any help would be appreciated. 
Anyone else faced similar issue before. 

Thanks, 
PranavB 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
 http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
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] Synthetic backups failing with 610

2013-06-04 Thread ken_zufall
No, that configuration doesn't work either.  You're limited to a single 
synthetic schedule per policy.

Ken Zufall
Operating Systems Administrator
D660C
The Goodyear Tire  Rubber Company
GTN 446.0592 or 330.796.0592




From:   sm...@peppas.gr
To: ken_zuf...@goodyear.com, pranav_vent...@hotmail.com
Cc: veritas-bu@mailman.eng.auburn.edu
Date:   06/04/2013 10:15 AM
Subject:RE: [Veritas-bu] Synthetic backups failing with 610



But ,
I think that you can run differential incrementals and synthesize a 
cumulative  backup.
Then you can use the full and the latest synthetic cumulative and create a 
new synthetic full. 
As you do not mix incremental and cumulative backups you are ok
 
stefanos
 
From: veritas-bu-boun...@mailman.eng.auburn.edu [
mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of 
ken_zuf...@goodyear.com
Sent: Tuesday, June 04, 2013 2:33 PM
To: pranav_vent...@hotmail.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Synthetic backups failing with 610
 
We had a similar problem last year, discovered that the problem--for us, 
anyways--is that you can't have mixed incrementals when using synthetics. 
For example, you can run differential incrementals and synthetic fulls; 
you can run cumulative incrementals and synthetic fulls; but you cannot 
run cumulative and differential backups and get successful synthetics. 
They will work for a single cycle (seed full, mixed incrementals, 
synthetic full), but the next time a synthetic is attempted it will fail 
with a 610. 

Took us months to figure that one out and that was working with Symantec 
support. 

Ken Zufall
Operating Systems Administrator
The Goodyear Tire  Rubber Company




From:pranav batra pranav_vent...@hotmail.com 
To:Veritas veritas-bu@mailman.eng.auburn.edu 
Date:06/04/2013 02:53 AM 
Subject:[Veritas-bu] Synthetic backups failing with 610 
Sent by:veritas-bu-boun...@mailman.eng.auburn.edu 




Hello Geeks, 

I am here facing issues with synthetic backup.  There are 7-8 windows 2008 
clients that are giving me issues with synthetic backup. 
The backup is failing with 610. 

1: (610) end point terminated with an error 

Environment : Master windows 2008 R2 -7.5.0.5 
Client 7.5.0.5 -2008R2 

We are taking their backups on Pure Disk pool ( We have created MSDP ). 
All the backups are happening over the WAN and thus we are using synthetic 
backups for the weekends. 


FUll backups runs fine ,incremental runs file ,synthetic also does runs 
fine but fails after running/writing few Gigs with 610. 

1: (610) end point terminated with an error 


Not able to get any clue even from Symantec till now. 

Any help would be appreciated. 
Anyone else faced similar issue before. 

Thanks, 
PranavB 
___
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] Synthetic backups failing with 610

2013-06-04 Thread pranav batra
We are only trying to synthesize full and differential. We are not taking 
cumulative and still backup is failing with 610.
Thanks,PranavB

To: sm...@peppas.gr
CC: pranav_vent...@hotmail.com; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Synthetic backups failing with 610
From: ken_zuf...@goodyear.com
Date: Tue, 4 Jun 2013 10:45:50 -0400

No, that configuration doesn't work either.
 You're limited to a single synthetic schedule per policy.



Ken Zufall

Operating Systems Administrator

D660C

The Goodyear Tire  Rubber Company

GTN 446.0592 or 330.796.0592









From:  
 sm...@peppas.gr

To:  
 ken_zuf...@goodyear.com,
pranav_vent...@hotmail.com

Cc:  
 veritas-bu@mailman.eng.auburn.edu

Date:  
 06/04/2013 10:15 AM

Subject:
   RE: [Veritas-bu]
Synthetic backups failing with 610








But ,

I think that you can run
differential incrementals and synthesize a cumulative  backup.

Then you can use the full
and the latest synthetic cumulative and create a new synthetic full. 

As you do not mix incremental
and cumulative backups you are ok

 

stefanos

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu]
On Behalf Of ken_zuf...@goodyear.com

Sent: Tuesday, June 04, 2013 2:33 PM

To: pranav_vent...@hotmail.com

Cc: veritas-bu@mailman.eng.auburn.edu

Subject: Re: [Veritas-bu] Synthetic backups failing with 610

 

We had a similar problem last year, discovered
that the problem--for us, anyways--is that you can't have mixed incrementals
when using synthetics.  For example, you can run differential incrementals
and synthetic fulls; you can run cumulative incrementals and synthetic
fulls; but you cannot run cumulative and differential backups and get successful
synthetics.  They will work for a single cycle (seed full, mixed incrementals,
synthetic full), but the next time a synthetic is attempted it will fail
with a 610. 



Took us months to figure that one out and that was working with Symantec
support. 



Ken Zufall

Operating Systems Administrator

The Goodyear Tire  Rubber Company









From:pranav
batra pranav_vent...@hotmail.com


To:Veritas
veritas-bu@mailman.eng.auburn.edu


Date:06/04/2013
02:53 AM 

Subject:[Veritas-bu]
Synthetic backups failing with 610


Sent by:veritas-bu-boun...@mailman.eng.auburn.edu












Hello Geeks, 



I am here facing issues with synthetic backup.  There are 7-8 windows
2008 clients that are giving me issues with synthetic backup.


The backup is failing with 610.




1: (610) end point terminated with an error 



Environment : Master windows 2008 R2 -7.5.0.5


Client 7.5.0.5 -2008R2 



We are taking their backups on Pure Disk pool ( We have created MSDP ).
All the backups are happening over the WAN and thus we are using synthetic
backups for the weekends. 





FUll backups runs fine ,incremental runs file ,synthetic also does runs
fine but fails after running/writing few Gigs with 610.




1: (610) end point terminated with an error 





Not able to get any clue even from Symantec till now.




Any help would be appreciated.


Anyone else faced similar issue before.




Thanks, 

PranavB 

___

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] Synthetic Full Backup not starting

2011-02-22 Thread ianbutton1
We have two big fileshares (900GB, 1.5TB, both about 2 million files) that I 
recently changed to Synthetic Full backups to speed up backups. [We're on 
NetBackup Enterprise 6.5, backing up to disk and then duplicating to tapes].  
But every few weeks these SynthFulls just don't start!
A traditional Full works OK (to start off the sequence).
Then daily Differential Incrementals work OK (window 21:00-00:00 Mon-Fri) and 
finish about 01:30.  
The Synthetic Full window is 00:00 Sat-00:00 Sun, but I see that the job goes 
into the Activity monitor queue at 1 second after the Friday evening DiffInc 
starts.  A couple of minutes after the Friday DiffInc finishes, the SynthFull 
starts, and it goes on about 12 hours - OK when that happens.
But twice in the last couple of months one or both of these SynthFulls just 
doesn't even start.  The Friday DiffInc starts  finishes OK, but no SynthFull, 
no warnings, no error messages.  Nothing in the bpsynth log directory that day, 
no syn_ entries in the bptm log.  It looks as though the Policy Execution 
Manager doesn't have the entry in its schedule.  When the SynthFulls run, they 
don't gradually start later  later, so it doesn't look like they are losing 
the window.
Running another Traditional Full seems to get things going OK again for a few 
weeks.
Any ideas, please?  Having to run these large jobs manually, and then 
duplicating the images to tape, takes a couple of days and ties up tape drives 
that might be needed for restores!
TIA
Ian

+--
|This was sent by ian.but...@calderdale.gov.uk via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] synthetic

2010-10-03 Thread Crowey

terry712 wrote:
 running synthetic backups . windows backups and all 6.5.6.  the backups are 
 synthesiing without problem - only thing that i still need to get setup is i 
 want a monthly backup to get ported onto tape.
 
 how do you do this?


Gidday, what we do for our EOM backups is do a separate tape copy that grabs 
its tapes from our EOM volume pool.  Admittedly, its time consuming ... but its 
worked perfectly for us for 3+ years now (and that's for two separate synthetic 
backups every weekend - and this puts both onto one set of tapes)

I should add that we do have Vault ... I don't know if that makes much 
difference.

Hope that helps.

Cheers
John

+--
|This was sent by jcr...@marketforce.com.au via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] synthetic

2010-10-01 Thread David Stanaway
 Find out and let me know :P

There is a touchfile to allow the synth to write 2 copies at the same
time. One to disk, one to tape.  I wish the NBU developers would get off
their asses and enable SLP as a backup target for synthetics. This
omission is pathetic to have been left as a known issue for so long.

http://www.symantec.com/business/support/index?page=contentid=TECH72168



On 10/1/2010 3:22 PM, terry712 wrote:
 running synthetic backups . windows backups and all 6.5.6.
 the backups are synthesiing without problem - only thing that i still need to 
 get setup is i want a monthly backup to get ported onto tape

 how do you do this?

 thanks

 +--
 |This was sent by terry.r...@lpct.scot.nhs.uk via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--


 ___
 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] Synthetic Backup Fails Code 671 / 238

2009-10-13 Thread Steve Fogarty
Anybody pulling, or have pulled, their hair out on this one?

Synthetic Backup Fails Code 671

*error=the database contains conflicting or erroneous entries(238)*

I found the following, but even though it seemed to match my issue, it was
of no use.

http://seer.entsupport.symantec.com/docs/275030.htm

Anybody try anything that worked?

Steve
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups

2009-07-08 Thread W. Curtis Preston
Nope.  You verified what I believed to be the case.  Although the
documentation suggests otherwise, and something that the original poster is
experiencing does as well, it's nice to see that it works as I thought it
should -- at least somewhere. ;)

Thanks.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Crowey
Sent: Tuesday, July 07, 2009 10:52 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Synthetic Backups



cpreston wrote:
 And you're verifying that the original full does not need to be kept
around?
 


OK ... I missed two important points I guess.  With a 1 month retention
period, I always have 4 (weekly) synthetic backups in my library, and so yes
I've never had any problem about recovering files very quickly that were/are
less than one month old.

However, we do also have another separate policy that duplicates the most
recent synthetic copy to another set of tapes for our EOM set.

And, again, I've restored from our EOM tapes (from various months/years)
more than enough times to know that the process works just fine.

And I do know for sure that we do not keep an initial full backup - it
expires (after one month) like any other backup.  Its the seed for the
initial synthetic, but then its no longer required - moreover, its no longer
useful (in the synthetic backup process) if you don't have differentials
that date back to the creation of that 'seed' full backup.

Is that clearer? Anything else that I missed?

+--
|This was sent by jcr...@marketforce.com.au via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
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] Synthetic Backups

2009-07-08 Thread Jim H

There is a case open with Symantec about this issue, and I am told an EEB will 
be made available soon.

You are not supposed to have to keep a full around, but once the full expires a 
new full is taken automagically.

QuoteSo it appears I need to keep the Full backup around even though the 
Synthetic Full is suppose to be its equivalent. 

The Full backup runs on Day 5 even though I don't have it scheduled. In Fact 
Full are manual. Synthetics are scheduled. 

+--
|This was sent by jhilt...@excite.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups

2009-07-08 Thread Jim Horalek
Yeh, I'm not crazy! Or at least about this one.

Thanks Jim H

From another JimH


-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jim H
Sent: Wednesday, July 08, 2009 8:59 AM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Synthetic Backups



There is a case open with Symantec about this issue, and I am told an EEB
will be made available soon.

You are not supposed to have to keep a full around, but once the full
expires a new full is taken automagically.

QuoteSo it appears I need to keep the Full backup around even though the
Synthetic Full is suppose to be its equivalent. 

The Full backup runs on Day 5 even though I don't have it scheduled. In Fact
Full are manual. Synthetics are scheduled. 

+--
|This was sent by jhilt...@excite.com via Backup Central. Forward SPAM 
|to ab...@backupcentral.com.
+--


___
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] Synthetic Backups

2009-07-08 Thread bob944
 There is a case open with Symantec about this issue, and I am told
 an EEB will be made available soon.
 
 You are not supposed to have to keep a full around,

No.  You _must_ have a full plus subsequent TIR and diffs or cincs
to synthesize a new full, but it does not matter how the full was
generated.  (That was for clarity--I assume you meant to keep a
traditional full around.)

 but once the
 full expires a new full is taken automagically.

I've used synthetic fulls and cincs for years, demonstrated them in
this mailing list and found the documentation to be pretty darned
clear.  IME, they always work.  

What's been missing from this discussion (apologies if I've missed
it) is detail about what setup you or the original poster have.
What release, what platform, what is the policy config, what images
and TIR are available when it doesn't work for you, what's the
bpdbjobs output (easy way to track the progress of a synth and the
components it is using)?

I've confirmed it is working properly in 6.5.3.1 Solaris:  no
natural full exists, nor is one created--just the current synthfull
+ cinc = new synthful.  Is this (your experience, and the support
case and EEB) a 6.5.4 issue?

 QuoteSo it appears I need to keep the Full backup around even
  though the Synthetic Full is suppose to be its equivalent.
  
  The Full backup runs on Day 5 even though I don't have it
  scheduled. In Fact Full are manual. Synthetics are scheduled. 


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups

2009-07-08 Thread Jim Horalek
As I stated in a previous post. 

The issue here may not be Synthetic Backups.

An unsheduled Full backup(not synthetic) runs the next day !!!after I expire
the original full!!! The original Full was run manually. Using Calendar
based with no date to start.

Remember this was just a test to see what happened if I expired the full.

However Bob states you must have the full plus TIRs. This is a TIR policy.
All diffs exist. I expect an error if a requirement is not met, not running
a full backup, unless this is something new.

Running 6.5.4 but it may not be related to this release. Suse 10 ia64 (old
sgi)

Job is gone so I'll need to regenerate.

Jim

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of bob944
Sent: Wednesday, July 08, 2009 12:26 PM
To: veritas-bu@mailman.eng.auburn.edu
Cc: j...@federaledge.com; jhilt...@excite.com
Subject: Re: [Veritas-bu] Synthetic Backups


 There is a case open with Symantec about this issue, and I am told an
 EEB will be made available soon.
 
 You are not supposed to have to keep a full around,

No.  You _must_ have a full plus subsequent TIR and diffs or cincs to
synthesize a new full, but it does not matter how the full was generated.
(That was for clarity--I assume you meant to keep a traditional full
around.)

 but once the
 full expires a new full is taken automagically.

I've used synthetic fulls and cincs for years, demonstrated them in this
mailing list and found the documentation to be pretty darned clear.  IME,
they always work.  

What's been missing from this discussion (apologies if I've missed
it) is detail about what setup you or the original poster have. What
release, what platform, what is the policy config, what images and TIR are
available when it doesn't work for you, what's the bpdbjobs output (easy way
to track the progress of a synth and the components it is using)?

I've confirmed it is working properly in 6.5.3.1 Solaris:  no natural full
exists, nor is one created--just the current synthfull
+ cinc = new synthful.  Is this (your experience, and the support
case and EEB) a 6.5.4 issue?

 QuoteSo it appears I need to keep the Full backup around even
  though the Synthetic Full is suppose to be its equivalent.
  
  The Full backup runs on Day 5 even though I don't have it scheduled.
  In Fact Full are manual. Synthetics are scheduled. 


___
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] Synthetic Backups

2009-07-07 Thread tsimerson

Jim,

I've been testing it myself.  I think you do need to keep that full backup 
around.  The synthetic part of a synthetic backup is the consolidation of the 
full backup and the incrementals into a single image.  This is done via 
duplication.

The test scenario I'm working with is the following:
Full backup taken every 4 weeks and kept for 2 months
Incremental every night kept for 2 months
Synthetic full every week which is kept for 1 month (offsite retention only)

This seems to be working fine.  I see a full backup during in the backup 
image list for the test client.  I've not actually trying doing a restore of 
this full backup to see what tapes are loaded and how long it will take.


 I have a bit of an oddity.
 
 I'm testing Synthetic Backups.
 
 I have
 
 Day 1 Full backup. Day 2 Incremental
 Day 3 Synthetic-Full Day 4 Incremental (and manually expire the Day 1 Full) 
 Day 5 Full backup runs
 
 So it appears I need to keep the Full backup around even though the Synthetic 
 Full is suppose to be its equivalent.
 
 The Full backup runs on Day 5 even though I don't have it scheduled. In Fact 
 Full are manual. Synthetics are scheduled.
 
 Is this normal?
 
 Running 6.5.4 


+--
|This was sent by t...@tjsimerson.org via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Synthetic Backups

2009-07-07 Thread cpreston


 I've been testing it myself. I think you do need to keep that full backup 
 around. The synthetic part of a synthetic backup is the consolidation of 
 the full backup and the incrementals into a single image. This is done via 
 duplication. 


What makes it synthetic is that it is created tape to tape instead of 
transferring a bunch of non-changed data from the client again.  Once that new 
(synthetic) full is created, there is no need for previous fulls (other than 
for retention).  The new full DOES NOT rely on the old full once it's created.

+--
|This was sent by wcplis...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups

2009-07-07 Thread Jim Horalek
Thanks all,

Though keeping the orginal full around(to create other synthetics) does seem
a bit strange. Hopefully Netbackup will mature to elimnate the constraint.

Jim

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of cpreston
Sent: Tuesday, July 07, 2009 1:39 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Synthetic Backups




 I've been testing it myself. I think you do need to keep that full 
 backup around. The synthetic part of a synthetic backup is the 
 consolidation of the full backup and the incrementals into a single 
 image. This is done via duplication.


What makes it synthetic is that it is created tape to tape instead of
transferring a bunch of non-changed data from the client again.  Once that
new (synthetic) full is created, there is no need for previous fulls (other
than for retention).  The new full DOES NOT rely on the old full once it's
created.

+--
|This was sent by wcplis...@gmail.com via Backup Central. Forward SPAM 
|to ab...@backupcentral.com.
+--


___
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] Synthetic Backups

2009-07-07 Thread Dean
From what I've read, and from what Curtis says below, you DON'T need to keep
the original full backup around, once you've created at least one more
synethtic full backup. You can do just one full backup, then keep creating
synthetic fulls by merging the previous synthetic full with incrementals,
forever. The original full backup does not need to be retained as long is
there is always at least one unexpired synthetic full available.

Regards
Dean

On Wed, Jul 8, 2009 at 9:28 AM, Jim Horalek j...@federaledge.com wrote:

 Thanks all,

 Though keeping the orginal full around(to create other synthetics) does
 seem
 a bit strange. Hopefully Netbackup will mature to elimnate the constraint.

 Jim

 -Original Message-
 From: veritas-bu-boun...@mailman.eng.auburn.edu
 [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of cpreston
 Sent: Tuesday, July 07, 2009 1:39 PM
 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
 Subject: [Veritas-bu] Synthetic Backups




  I've been testing it myself. I think you do need to keep that full
  backup around. The synthetic part of a synthetic backup is the
  consolidation of the full backup and the incrementals into a single
  image. This is done via duplication.


 What makes it synthetic is that it is created tape to tape instead of
 transferring a bunch of non-changed data from the client again.  Once that
 new (synthetic) full is created, there is no need for previous fulls (other
 than for retention).  The new full DOES NOT rely on the old full once it's
 created.

 +--
 |This was sent by wcplis...@gmail.com via Backup Central. Forward SPAM
 |to ab...@backupcentral.com.
 +--


 ___
 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] Synthetic Backups

2009-07-07 Thread A Darren Dunham
On Wed, Jul 08, 2009 at 10:11:46AM +1000, Dean wrote:
 From what I've read, and from what Curtis says below, you DON'T need to keep
 the original full backup around, once you've created at least one more
 synethtic full backup. You can do just one full backup, then keep creating
 synthetic fulls by merging the previous synthetic full with incrementals,
 forever. The original full backup does not need to be retained as long is
 there is always at least one unexpired synthetic full available.

That is not what the admin guide says (I'm looking at Admin guide 1 for
UNIX NBU 6.5, page 128).  I had assumed this would be possible, but it
says a non-synthetic full must be used as the source.

Synthetic backup
A synthetic full or synthetic cumulative incremental backup is a
backup assembled from previous backups. The backups include one
previous, traditional full backup, and subsequent differential
backups and/or a cumulative incremental backup. (A traditional full
backup means a non-synthesized, full backup.) A client can then use
the synthesized backup to restore files and directories in the same
way that a client restores from a traditional backup.

-- 
Darren
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups

2009-07-07 Thread Dean
I see what you mean. But I suspect that's just a poorly worded paragraph.

The diagram on page 200 of the Admin Guide (Vol 1, Windows version)
indicates the original full is not required ongoing.

I wish I could say for sure from experience, but I've never been able to get
synthetic backups working at all :(

Cheers,
Dean

On Wed, Jul 8, 2009 at 10:21 AM, A Darren Dunham ddun...@taos.com wrote:

 On Wed, Jul 08, 2009 at 10:11:46AM +1000, Dean wrote:
  From what I've read, and from what Curtis says below, you DON'T need to
 keep
  the original full backup around, once you've created at least one more
  synethtic full backup. You can do just one full backup, then keep
 creating
  synthetic fulls by merging the previous synthetic full with incrementals,
  forever. The original full backup does not need to be retained as long is
  there is always at least one unexpired synthetic full available.

 That is not what the admin guide says (I'm looking at Admin guide 1 for
 UNIX NBU 6.5, page 128).  I had assumed this would be possible, but it
 says a non-synthetic full must be used as the source.

 Synthetic backup
A synthetic full or synthetic cumulative incremental backup is a
backup assembled from previous backups. The backups include one
previous, traditional full backup, and subsequent differential
backups and/or a cumulative incremental backup. (A traditional full
backup means a non-synthesized, full backup.) A client can then use
the synthesized backup to restore files and directories in the same
way that a client restores from a traditional backup.

 --
 Darren
 ___
 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] Synthetic Backups

2009-07-07 Thread Crowey

Gidday, I've been running synthetics for nearly two years now to backup about 
3/3.5 TBs and have to say has generally run extremely well.

Within the same policy I have 3 schedules.

The first is an ad-hoc full - I used this to create the first full backup, and 
on the very few occasions when the synthetic has stuffed up and I needed to 
start again.  It has a 1 month retention.

Second is a daily differential that runs every three hours and goes to disc.  
They have a two week retention period.

Lastly, I have the synthetic full backup.  Runs every saturday and also has a 1 
month retention.

Like I said, it occasionaly stuffs up, but works 99% of the time, and appears 
to run 3 to 4 times faster than a traditional full.

I HIGHLY recommend it.

+--
|This was sent by jcr...@marketforce.com.au via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backups Or May A Red Herring.

2009-07-07 Thread Jim Horalek (Federal Edge)
Unfortunately my test showed you do.(or do they?). I'm to understand why 
expiring the full backup triggered another full backup (not synthetic). There 
maybe an obsure reason that my test failed or it may be a bug.

Maybe the Full backup running has nothing to do with the synthetics but is 
actually a scheduling or retension issue. Since all my Fulls are manual this 
is a bit perplexing as to why a Full ran automatically.

Something to do with running a manual backup and the system thinks it hasn't 
run since the image was expired?


jim




From: Dean 
Sent: Tuesday, July 07, 2009 5:11 PM
To: Jim Horalek 
Cc: VERITAS-BU@mailman.eng.auburn.edu 
Subject: Re: [Veritas-bu] Synthetic Backups


From what I've read, and from what Curtis says below, you DON'T need to keep 
the original full backup around, once you've created at least one more 
synethtic full backup. You can do just one full backup, then keep creating 
synthetic fulls by merging the previous synthetic full with incrementals, 
forever. The original full backup does not need to be retained as long is 
there is always at least one unexpired synthetic full available.

Regards
Dean


On Wed, Jul 8, 2009 at 9:28 AM, Jim Horalek j...@federaledge.com wrote:

  Thanks all,

  Though keeping the orginal full around(to create other synthetics) does seem
  a bit strange. Hopefully Netbackup will mature to elimnate the constraint.

  Jim


  -Original Message-
  From: veritas-bu-boun...@mailman.eng.auburn.edu
  [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of cpreston
  Sent: Tuesday, July 07, 2009 1:39 PM
  To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
  Subject: [Veritas-bu] Synthetic Backups




   I've been testing it myself. I think you do need to keep that full
   backup around. The synthetic part of a synthetic backup is the
   consolidation of the full backup and the incrementals into a single
   image. This is done via duplication.


  What makes it synthetic is that it is created tape to tape instead of
  transferring a bunch of non-changed data from the client again.  Once that
  new (synthetic) full is created, there is no need for previous fulls (other
  than for retention).  The new full DOES NOT rely on the old full once it's
  created.

  +--
  |This was sent by wcplis...@gmail.com via Backup Central. Forward SPAM
  |to ab...@backupcentral.com.
  +--


  ___
  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] Synthetic Backups

2009-07-07 Thread W. Curtis Preston
And you're verifying that the original full does not need to be kept around?

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Crowey
Sent: Tuesday, July 07, 2009 5:55 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Synthetic Backups


Gidday, I've been running synthetics for nearly two years now to backup
about 3/3.5 TBs and have to say has generally run extremely well.

Within the same policy I have 3 schedules.

The first is an ad-hoc full - I used this to create the first full backup,
and on the very few occasions when the synthetic has stuffed up and I needed
to start again.  It has a 1 month retention.

Second is a daily differential that runs every three hours and goes to disc.
They have a two week retention period.

Lastly, I have the synthetic full backup.  Runs every saturday and also has
a 1 month retention.

Like I said, it occasionaly stuffs up, but works 99% of the time, and
appears to run 3 to 4 times faster than a traditional full.

I HIGHLY recommend it.

+--
|This was sent by jcr...@marketforce.com.au via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
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] Synthetic Backups

2009-07-07 Thread Crowey


cpreston wrote:
 And you're verifying that the original full does not need to be kept around?
 


OK ... I missed two important points I guess.  With a 1 month retention period, 
I always have 4 (weekly) synthetic backups in my library, and so yes I've never 
had any problem about recovering files very quickly that were/are less than one 
month old.

However, we do also have another separate policy that duplicates the most 
recent synthetic copy to another set of tapes for our EOM set.

And, again, I've restored from our EOM tapes (from various months/years) more 
than enough times to know that the process works just fine.

And I do know for sure that we do not keep an initial full backup - it expires 
(after one month) like any other backup.  Its the seed for the initial 
synthetic, but then its no longer required - moreover, its no longer useful (in 
the synthetic backup process) if you don't have differentials that date back to 
the creation of that 'seed' full backup.

Is that clearer? Anything else that I missed?

+--
|This was sent by jcr...@marketforce.com.au via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Synthetic Backups

2009-06-25 Thread Jim Horalek
I have a bit of an oddity. 
 
I'm testing Synthetic Backups. 
 
I have
 
Day 1 Full backup. 
Day 2 Incremental
Day 3 Synthetic-Full 
Day 4 Incremental (and manually expire the Day 1 Full) 
Day 5 Full backup runs
 
So it appears I need to keep the Full backup around even though the
Synthetic Full is suppose to be its equivalent.
 
The Full backup runs on Day 5 even though I don't have it scheduled. In Fact
Full are manual. Synthetics are scheduled.
 
Is this normal?
 
Running 6.5.4 
 
Jim
 
 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

2007-08-14 Thread Cruice, Daniel \(US - Glen Mills\)
When performing a synthetic full, what should I use, a differential
Incremental or a cumulative incremental?...and why?

 

Thanks

Dan Cruice

Deloitte Technology Service

Deloitte  Touche Tohmatsu

Direct: +1 610-479-5179

Fax: +1 610-479-6179

E-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 

www.deloitte.com 
 
This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message and are hereby 
notified that any disclosure, copying, or distribution of this message, or the 
taking of any action based on it, is strictly prohibited.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

2007-08-14 Thread rcarlisle
What is your goal for Synthetic fulls?  Are you running the incrementals to
tape or disk?  Are you running the fulls to tape or disk?
 
 
 
Reneé Carlisle 
ServerWare Corporation



 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Cruice,
Daniel (US - Glen Mills)
Sent: Tuesday, August 14, 2007 3:48 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc



When performing a synthetic full, what should I use, a differential
Incremental or a cumulative incremental?...and why?

Thanks

Dan Cruice

Deloitte Technology Service

Deloitte  Touche Tohmatsu

Direct: +1 610-479-5179

Fax: +1 610-479-6179

E-mail:  mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]

www.deloitte.com

 
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message and are
hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited. 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

2007-08-14 Thread Cruice, Daniel (US - Glen Mills)
Right now we are running Incrementals to disk and tape the same w/ the fulls.

 

Thanks

Dan



From: rcarlisle [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 14, 2007 4:19 PM
To: Cruice, Daniel (US - Glen Mills); VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

 

What is your goal for Synthetic fulls?  Are you running the incrementals to 
tape or disk?  Are you running the fulls to tape or disk?

 

 

 

Reneé Carlisle 

ServerWare Corporation

 

 

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, Daniel 
(US - Glen Mills)
Sent: Tuesday, August 14, 2007 3:48 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

When performing a synthetic full, what should I use, a differential Incremental 
or a cumulative incremental?...and why?

Thanks

Dan Cruice

Deloitte Technology Service

Deloitte  Touche Tohmatsu

Direct: +1 610-479-5179

Fax: +1 610-479-6179

E-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 

www.deloitte.com

 

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message and are hereby 
notified that any disclosure, copying, or distribution of this message, or the 
taking of any action based on it, is strictly prohibited. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

2007-08-14 Thread Martin, Jonathan
My guess is that you would get a performance boost using cumulative, because 
NBU would only have to splice two backups.  The full and the one cumulative 
versus the full and a week's worth of differentials.  You also get the added 
advantage of if a tape fails you're covered (unless its your most recent.)  Of 
course, you also get longer backup windows for the cumulative (versus diff), 
the same data written to tape multiple times (potential tape / disk cost 
issue.)  Given that you are using disk, I'd say differentials is probably the 
way to go all around.
 
-Jonathan



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, Daniel 
(US - Glen Mills)
Sent: Tuesday, August 14, 2007 4:23 PM
To: rcarlisle; VERITAS-BU@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc



Right now we are running Incrementals to disk and tape the same w/ the fulls.

 

Thanks

Dan



From: rcarlisle [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 14, 2007 4:19 PM
To: Cruice, Daniel (US - Glen Mills); VERITAS-BU@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

 

What is your goal for Synthetic fulls?  Are you running the incrementals to 
tape or disk?  Are you running the fulls to tape or disk?

 

 

 

Reneé Carlisle 

ServerWare Corporation

 

 

 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, Daniel 
(US - Glen Mills)
Sent: Tuesday, August 14, 2007 3:48 PM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Synthetic fulls Diff Inc VS cumulative Inc

When performing a synthetic full, what should I use, a differential Incremental 
or a cumulative incremental?...and why?

Thanks

Dan Cruice

Deloitte Technology Service

Deloitte  Touche Tohmatsu

Direct: +1 610-479-5179

Fax: +1 610-479-6179

E-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 

www.deloitte.com

 

This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law. If you 
are not the intended recipient, you should delete this message and are hereby 
notified that any disclosure, copying, or distribution of this message, or the 
taking of any action based on it, is strictly prohibited. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Synthetic Full Backups

2007-05-14 Thread markjessup
I am curious if anyone is using the Synthetic Full Backup feature that
is provided with Netbackup now.  If people are using it, what issues if
any have you come across with this feature and what specific workload
have you applied this feature to?   Also, what benefits have you seen ?
Thanks!




Mark Jessup - IS Manager
Enterprise Storage and Content Management/Imaging 
Northwestern Mutual
(414) 661-3968
[EMAIL PROTECTED]

/prefont face=ArialThis e-mail and any attachments may contain confidential 
information of Northwestern Mutual. If you are not the intended recipient of 
this message, be aware that any disclosure, copying, distribution or use of 
this e-mail and any attachments is prohibited. If you have received this e-mail 
in error, please notify Northwestern Mutual immediately by returning it to the 
sender and delete all copies from your system. Please be advised that 
communications received via the Northwestern Mutual Secure Message Center are 
secure. Communications that are not received via the Northwestern Mutual Secure 
Message Center may not be secure and could be observed by a third party. Thank 
you for your cooperation./fontpre
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Full Backups

2007-05-14 Thread Curtis Preston
I'm a big fan, but I would agree that they're not for everybody.  One
thing that makes them faster is using disk as the target (at least) and
the source (hopefully).

---
W. Curtis Preston
Author of O'Reilly's Backup  Recovery and Using SANs and NAS
VP Data Protection
GlassHouse Technologies


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wayne T
Smith
Sent: Monday, May 14, 2007 1:25 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Synthetic Full Backups

This was some time ago, but I found synthetic backups to be either 
irrelevant (due to restrictions on their applicability) or unusable (due

to the occasional problems that seem to require new full backups) at my 
shop (v5.1).   That, and the last thing that my shop needed were more 
long tape-to-tape copies, caused me to quickly try and then scrap its 
use.   Increasing network capability and moving large data accumulations

to the central site have helped my problem of long full backups.  Adding

backup to disk or maybe VTL is another step to smooth our operations 
(and be able to feed more modern tape drives).

Thanks to everyone for the fine discussion of VTL in another thread!

cheers, wayne

[EMAIL PROTECTED] wrote, in part,  on 2007-05-14 3:18
PM:

 I am curious if anyone is using the Synthetic Full Backup feature that

 is provided with Netbackup now.  If people are using it, what issues 
 if any have you come across with this feature and what specific 
 workload have you applied this feature to?   Also, what benefits have 
 you seen ?   Thanks!

___
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] Synthetic Backup

2006-10-16 Thread Barber, Layne \(Contractor\)



NBU 5.1 - MP5 
HP-UX

I want to use 
synthetic backups for a large client. The question is, Can I have the Normal 
full go to tape and then have the diff inc go to a dsu and have the synth full 
go to tape? If so, how would I set up a policy for this?

Thank You,

Layne Barber
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Synthetic Backup

2006-10-16 Thread Paul Keating
Title: Message



Set up 
3 schedules in the policy.

Full
Diff
Synth 
Full

in 
each sched, select "override default storage unit".

Point 
the Full and Synth Full to the regular tape STU, and theDiffto the 
DSU.

Paul

-- 

  
  -Original Message-From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of Barber, 
  Layne (Contractor)Sent: October 16, 2006 10:52 AMTo: 
  veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Synthetic 
  Backup
  NBU 5.1 - MP5 
  HP-UX
  
  I want to use 
  synthetic backups for a large client. The question is, Can I have the Normal 
  full go to tape and then have the diff inc go to a dsu and have the synth full 
  go to tape? If so, how would I set up a policy for this?
  
  Thank You,
  
  Layne 
Barber

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