please confirm current backup policy

CVNRneuroimaging / infrastructure

Issue tracking, system documentation and configs for operations side of the neuroimaging core @ Atlanta VA CVNR / Emory University

3 stars 2 forks source link

please confirm current backup policy #158

Open stowler opened 8 years ago

stowler commented 8 years ago

Hi Rob @rrmm ,

I need to clear some space on pano, but before I do so can you confirm the frequency with which hippoback is getting backed up to tripleback, and when the last error-free backup occurred? Once I know that hippoback's /data/backup/Atlanta/stowlerWIP/sharedReadOnly/ is being backed up frequently and completely I can make space on pano without worry.

Thanks, Stephen

stowler commented 8 years ago

Hi Rob @rrmm . Any luck with this one? I really need to clear some space on pano.

Thanks, Stephen

stowler commented 8 years ago

Hi Keith @kmcgregor123456 ,

Spoke to Rob about this today, and he says he's not yet familiar with your backup scheme. Can you please brief him on the current hippoback->tripleback backup config, and answer the questions above?

Thanks, Stephen

(cc @rrmm )

kmcgregor123456 commented 8 years ago

Actually, hippoback is being backed up to hippostore. Last good was last night.

stowler commented 8 years ago

A couple of questions so that I can decide how to proceed:

How frequently is the hippoback-to-hippostore backup launched?
How long does it typically take to complete?
Are you notified of errors or do you have to check for them?
Does your configuration generate roll-back-able snapshots, or does deleting data from hippoback also delete it from hippostore during the subsequent backup?

rrmm commented 8 years ago

daily (20:00)
at least an hour, depends on the size of the changeset (there may be an issue here)
must check for log
no deletion appears to take place (no --delete)