Closed
Bug 940968
Opened 11 years ago
Closed 11 years ago
archive talos data on bm-remote web hosts before move to scl3
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: jlund)
References
Details
We should make sure we have a backup of the talos web data on the bm-remote web hosts before we attempt to move these machines to scl3. Callek said he'd own making sure this happened.
Assignee | ||
Comment 1•11 years ago
|
||
Through Callek I will be dealing with this before Friday.
Assignee | ||
Updated•11 years ago
|
Assignee: bugspam.Callek → jlund
Assignee | ||
Comment 2•11 years ago
|
||
from bm-remote-talos-webhost-01, a backup was made on my local disk for the following files/dirs: /etc/httpd/conf/httpd.conf -- bm-remote-talos-webhost-01_apache-httpd_bup_211113.conf /root -- bm-remote-talos-webhost-01_root-home_bup_211113.tar.gz size=21M /var/www -- bm-remote-talos-webhost-01_www_bup_211113.tar.gz size=241M I think this covers the apache conf settings, the www and html dirs, and some installation logs saved in the root dir. I have 3 questions: 1) Is all we would require to be relatively safe? Should I back up more or less? 2) Should I upload this to one of our remote machines or is my external hdd + computer "good enough"? 3) I know that /var/www is rsync'd between bm-remote-talos-webhost-0{1-3} but is there other files on 02 and 03 that I should backup that is not in 01? :)
Assignee | ||
Comment 3•11 years ago
|
||
I am going to say this is resolved since I assume these machines have been moved and I still hold tar balls of their valuable state
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•