Closed Bug 1136233 Opened 10 years ago Closed 10 years ago

move legacy vcs-sync dirs off of NFS volume

Categories

(Developer Services :: General, task)

Product:
Developer Services
Component:
General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hwine, Assigned: hwine)

References

Details

There are 3 conversion jobs still using NFS volumes. Move them to a different box, so NFS volume can be removed from backup rotation.
(In reply to Hal Wine [:hwine] (use needinfo) from comment #0) > There are 3 conversion jobs still using NFS volumes. > > Move them to a different box, so NFS volume can be removed from backup > rotation. When this bug is completed, can we stop backing up the nfs volume?
(In reply to Rob Tucker [:rtucker] from comment #1) > When this bug is completed, can we stop backing up the nfs volume? yes
Flags: needinfo?(hwine)
future searchbait, this vol is 10.22.74.20:/github_sync
transferring nfs data to github-sync1.dmz in process
Status: NEW → ASSIGNED
Flags: needinfo?(hwine)
See Also: → 1136607
Jobs moved off NFS and from github-sync1-dev to github-sync1. This will cause a temporary spike in backup services, as the data appears "new" to github-sync1's backup. Will wait a day to ensure no issues, the NFS volume can stop being backed up. After a week, NFS volume can be deleted
Depends on: 1140593
Am I ok to stop backing up 10.22.75.85:/github_sync now?
I asked :atoll to make a one-shot full of the vol, because bug 1140593 is listed as blocking this one. So, I think we've got the backups done there (nudged atoll last week but ZLB happened, haven't pushed again) via netvault, and sounds like bacula too. I believe the backup of the volume is related to hal's evac of the seamicro nodes, so, tagging him for a status check on the volume in particular, and that he's unblocked on the seamicros in general.
Flags: needinfo?(hwine)
Parsing error (consider caffeine infusion). This has nothing to do with the seamicro evacuation (just the opposite - we needed to add more work on the sea micro due to disk space issues on the hp blade). However, I am not blocked on anything related to the seamicro evacuation. (In reply to Rob Tucker [:rtucker] from comment #6) > Am I ok to stop backing up 10.22.75.85:/github_sync now? Yes, please! What do I need to do to get these volumes detached from these hosts, and then destroyed? I've already unmounted them from the boxes (as nothing is using them anymore)
Flags: needinfo?(hwine)
It's still mounted on github-sync3.dmz.scl3 and github-sync4.dmz.scl3. Verify/pull those, and the only places it'll still be mounted is on the backup boxes, which we can then get moving on and destroy the volume.
I unmounted from github-sync3.dmz.scl3 -- we've already decommed github-sync4 gcox: If you find it mounted, feel free to unmount on your own -- I'm long done with it.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
NFS vol is offline'd on the filer and will be destroyed permanently in about a week.
NFS github_sync volume deleted
You need to log in before you can comment on or make changes to this bug.