Justin
Disagree. We run fulls weekend and incr during week. Works for us.
An outage or Disaster could occur anytime, not just at the weekend.
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: Simon.Weaver AT Astrium-eads DOT net
-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz.backup AT gmail DOT com]
Sent: 13 May 2006 17:55
To: Hillman, Eric
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Planned Network Outage - What should I do about
backups?
One comment - running all fulls on the weekend is an extremely bad practice,
if something happens on Friday, then you lose a week's worth of data,
depending on your incremental schedule. A better practice is to run Fulls
each day of the week and split it up in your environment. When the
connection is cut the jobs should fail, but I have not done too much with
DSSU/disk backups myself to comment on that part.
On 5/12/06, Hillman, Eric <Eric.Hillman AT blackrock DOT com> wrote:
>
>
>
> We start weekly backups every Friday night. They run through Sunday.
> There is a scheduled network outage on Saturday morning between 5am
> and noon. This will disconnect clients from the backup servers and the
> media servers from the master servers. Can anyone recommend the best
> way to pause these jobs? Here are the choices I'm considering:
>
> 1. Stop Netbackup daemons on all master and media servers Friday night
> and restart them after the network outage is done. I believe this
> will not allow all backups enough time to finish by Sunday night when
> our next backup window starts
>
> 2. Don't do anything. I'm not sure what will happed to jobs that are
> running including "User" database backups which get sent to the master
> server and run on a media server when the communication between those
> servers is gone. Also DSSU archival to tapes may experience problems
> when communication is cut between the master server who is sending the
> list of backup images to the media server to archive to tape.
>
> 3. Login immediately prior to the network outage and kill all backup
> jobs, stop Netbackup deamons and restart deamons after the network is
> back up. This has never ended cleanly. There's always jobs that don't
> stop. I almost always need to do some kill -9's to get the job
> processes to die and the rest of the daemons to stop. Also, partial
> images will be left on DSSU's which won't get removed. When jobs get
> restarted, they'll eventually run out of disk space because Netbackup
> left those partial images. Does anyone know of an easy way of
> cleaning out partial images on DSSU's?
>
> Any recommendations are helpful. Thanks!
> THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE
> PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM
> DISCLOSURE. If the reader of this message is not the intended
> recipient, you are hereby notified that any dissemination,
> distribution, copying or use of this message and any attachment is
> strictly prohibited. If you have received this message in error,
> please notify us immediately by replying to the message and
> permanently delete it from your computer and destroy any printout
> thereof.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
|
