[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [HTCondor-users] Backup guidance

For protecting against system failure bringing down your cluster, the high-availability section of the manual might be useful: http://research.cs.wisc.edu/htcondor/manual/v8.6/3_13High_Availability.html.

I keep our condor config files under version control, and that's about all the backing up we do. We're using ganglia to track usage history, so we should back up the RRD data (*shrug*; we don't), but otherwise we're okay with losing log data in a system crash. It's easy enough to reinstall and copy over the proper config files to start anew.

-Grant Goodyear-

On Wed, Jul 18, 2018 at 7:07 AM Nathan Sharp <nsharp@xxxxxxxxxxxxxxx> wrote:
Hello all,
ÂWe are investigating HTCondor for some potential production uses and so far been having great success! A huge thanks to all who have helped create all the online documentation on HTCondor.

ÂSo far I have had not very good luck finding information about how to properly back up an HTCondor system to protect against system failure and data loss. Is there information on this available somewhere? Can the execute, spool, log, and lock folders be backed up live, or do we need to shut down the daemons to get a clean state? Are there other pieces that need to be backed up with the files?

Thanks so much,

Nathan Sharp
Phoenix Integration Inc

HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Grant Goodyear   Â
web: http://www.grantgoodyear.org Â
e-mail: grant@xxxxxxxxxxxxxxxxx