This is a MIME message. If you are reading this text, you may want to
consider changing to a mail reader or gateway that understands how to
properly handle MIME multipart messages.
--=__PartD8F974A1.2__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sure enough - thanks, however;
>From reading the usage it appears that it only works on restores.
Jennifer, your comment below infers it works on backups?
-sj
>>> Jennifer <jc AT goo-rooz DOT com> 6/29/2004 12:07:21 PM >>>
Also to clarify the restart feature - it will restart the backup not at
the POF but at the most recent checkpoint which is set by
minutes....which is still handy
Greenberg, Katherine A wrote:
> I believe you are referring to the checkpoint restart. It became
> available in 5.0 GA for backups for Standard and Windows backups.
> (it's been available for restores since 4.5 FP3).
>
> This is from the release notes for 5.0:
>
>
> 6 NetBackup Release Notes for UNIX and Windows
>
> New Backup Capabilities With This Release
>
> NetBackup 5.0 contains enhancements and new features that enable a
> user to restart a backup at the last check point in the middle of the
> backup, build a new synthetic image, and enhanced open file backups
to
> name a few.
>
> ~ NetBackup Supports Checkpoint Restart for Backup Jobs
>
> Checkpoint Restart allows a failed backup job to be resumed from the
> last checkpoint. Checkpoints are taken periodically during a backup.
> Therefore, if a backup job fails, the issue causing the failure can
be
> corrected and the job can be resumed from the last checkpoint rather
> than at the beginning, thus saving time. In addition, an active
backup
> job may be suspended and then resumed from the last checkpoint at a
> later time. Also, jobs may be restarted from the beginning by
> selecting them from the Activity Monitor.
>
> Checkpoint restart for backups is supported for:
>
> ~ Backup jobs (support for restore jobs was introduced in 4.5 FP3).
>
> ~ Resume on file boundaries. This means the backup is resumed from
the
> next file after the last check-pointed file (for example, a resume
> cannot occur within a file).
>
> ~Backups of file-system backups (backups which use the Standard or
> Microsoft Windows policy types only).
>
> ~File system local and alternate client snapshot backups are
> supported. Other offhost backups (for example, Media Server Copy or
> Third Party Copy) are not supported.
>
>
> ~Kate
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~
> Katherine Greenberg
> Systems Engineer
> Mid-Range Storage Management
> Aetna, Inc.
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Scott
> Jacobson
> Sent: Tuesday, June 29, 2004 1:41 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] 5.1 Feature or Rumor? - Backup Fails; then
> continues from POF
>
> Can anyone confirm....
>
> Have I read that with 5.1 if a backup fails, you can now resubmit the
> job and if Enterprise sees a failure of that host within the same
> backup window that it will now continue the backup from the POF
(point
> of failure) and finish the job?
>
> Would be very handy when backing up a 2 terabyte system that fails
3/4
> of the way into the job.
>
> Thanks,
> Scott
>
> This e-mail may contain confidential or privileged information. If
you
> think you have received this e-mail in error, please advise the
sender by
> reply e-mail and then delete this e-mail immediately. Thank you.
Aetna
>
--=__PartD8F974A1.2__=
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Diso-8859-1"=
>
<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY style=3D"MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Sure enough - thanks, however;</DIV>
<DIV> </DIV>
<DIV>From reading the usage it appears that it only works on restores.</DIV=
>
<DIV> </DIV>
<DIV>Jennifer, your comment below infers it works on backups?</DIV>
<DIV> </DIV>
<DIV>-sj<BR><BR>>>> Jennifer <jc AT goo-rooz DOT com> 6/29/2004 =
12:07:21 PM >>><BR></DIV>
<DIV style=3D"COLOR: #000000">Also to clarify the restart feature - it =
will restart the backup not at <BR>the POF but at the most recent =
checkpoint which is set by <BR>minutes....which is still handy<BR><BR>Green=
berg, Katherine A wrote:<BR><BR>> I believe you are referring to the =
checkpoint restart. It became <BR>> available in 5.0 GA for backups for =
Standard and Windows backups. <BR>> (it's been available for restores =
since 4.5 FP3).<BR>> <BR>> This is from the release notes for =
5.0:<BR>> <BR>><BR>> 6 NetBackup Release Notes for UNIX and =
Windows<BR>><BR>> New Backup Capabilities With This Release<BR>><B=
R>> NetBackup 5.0 contains enhancements and new features that enable a =
<BR>> user to restart a backup at the last check point in the middle of =
the <BR>> backup, build a new synthetic image, and enhanced open file =
backups to <BR>> name a few.<BR>><BR>> ~ NetBackup Supports =
Checkpoint Restart for Backup Jobs<BR>><BR>> Checkpoint Restart =
allows a failed backup job to be resumed from the <BR>> last checkpoint.=
Checkpoints are taken periodically during a backup. <BR>> Therefore, =
if a backup job fails, the issue causing the failure can be <BR>> =
corrected and the job can be resumed from the last checkpoint rather =
<BR>> than at the beginning, thus saving time. In addition, an active =
backup <BR>> job may be suspended and then resumed from the last =
checkpoint at a <BR>> later time. Also, jobs may be restarted from the =
beginning by <BR>> selecting them from the Activity Monitor.<BR>><BR>=
> Checkpoint restart for backups is supported for:<BR>><BR>> ~ =
Backup jobs (support for restore jobs was introduced in 4.5 FP3).<BR>><B=
R>> ~ Resume on file boundaries. This means the backup is resumed from =
the <BR>> next file after the last check-pointed file (for example, a =
resume <BR>> cannot occur within a file).<BR>><BR>> ~Backups of =
file-system backups (backups which use the Standard or <BR>> Microsoft =
Windows policy types only).<BR>><BR>> ~File system local and =
alternate client snapshot backups are <BR>> supported. Other offhost =
backups (for example, Media Server Copy or <BR>> Third Party Copy) are =
not supported.<BR>><BR>> <BR>> ~Kate<BR>> =
<BR>> <BR>><BR>> ~~~~~~~~~~~~~~~~~~~~~~~~~~<BR>> =
Katherine Greenberg<BR>> Systems Engineer<BR>> Mid-Range Storage =
Management<BR>> Aetna, Inc.<BR>><BR>> -----Original Message-----<B=
R>> From: veritas-bu-admin AT mailman.eng.auburn DOT edu <BR>> [<A =
href=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT
edu]">mailto:veritas-bu-=
admin AT mailman.eng.auburn DOT edu]</A> On Behalf Of Scott <BR>>
Jacobson<BR>&=
gt; Sent: Tuesday, June 29, 2004 1:41 PM<BR>> To: veritas-bu AT mailman DOT
eng=
.auburn.edu<BR>> Subject: [Veritas-bu] 5.1 Feature or Rumor? - Backup =
Fails; then <BR>> continues from POF<BR>><BR>> Can anyone =
confirm....<BR>> <BR>> Have I read that with 5.1 if a backup =
fails, you can now resubmit the <BR>> job and if Enterprise sees a =
failure of that host within the same <BR>> backup window that it will =
now continue the backup from the POF (point <BR>> of failure) and =
finish the job?<BR>> <BR>> Would be very handy when backing up =
a 2 terabyte system that fails 3/4 <BR>> of the way into the job.<BR>>=
; <BR>> Thanks,<BR>> Scott<BR>><BR>> This e-mail may =
contain confidential or privileged information. If you<BR>> think you =
have received this e-mail in error, please advise the sender by<BR>> =
reply e-mail and then delete this e-mail immediately. Thank you. Aetna<BR>&=
gt;<BR><BR></DIV></BODY></HTML>
--=__PartD8F974A1.2__=--
|
