We break our large datasets into multiple streams and restart that way.
It's much easier for me to say to an app group "all of the backups
finished except /lun7 and I'm rerunning that now" than "The backup is
80% complete and we're rerunning it from wherever it failed." For
backups that run 48 hours, we just feel more comfortable knowing exactly
what backups are complete and which directories can be restored from
now, rather than hoping the whole thing completes later.

-Jonathan

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
Piszcz
Sent: Wednesday, September 29, 2010 10:10 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] poll: checkpoint restart

Hi,

I was curious, as backups get larger and larger, how many out there are 
using checkpoint restart (yes I know it slows down the backups a bit)
but 
it saves a lot of time having to start a 2-8TB backup again from scratch

if something goes wrong (network issue or otherwise).

Is it becoming more commonplace to use this?

Justin.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu