We'll need a heck of a lot of space to replace all of 10.253.0.10:/vol/ftp_stage 10.253.0.11:/vol/stage 10.253.0.3:/vol/fx_candidates 10.253.0.139:/data/try-builds 10.253.0.139:/data/tinderbox-builds 10.253.0.139:/data/mobile-tinderbox-builds and any other volumes that are added between now and shutting down the netapps in scj1. Once this is up, we'll need to keep the volume reasonably in sync with the above mounts, so that we can make it official with a relatively short downtime (make the sjc1 volumes read-only, one final rsync, and start writing to the scl3 volume) Are there any additional parameters we need to determine before then?
(In reply to Dustin J. Mitchell [:dustin] from comment #0) Total Used Mounted from: 6.5T 6.4T 10.253.0.10:/vol/ftp_stage 4.2T 3.8T 10.253.0.11:/vol/stage 500G 254G 10.253.0.3:/vol/fx_candidates 14T 4.0T 10.253.0.139:/data/try-builds 10.253.0.139:/data/tinderbox-builds 10.253.0.139:/data/mobile-tinderbox-builds ==== ==== 26T 15T Totals The last three appear to be different mount points on the same filesystem on the server end, so they collectively share the same disk space.
I've started an initial ndmpcopy for mpt-netapp-a:/vol/ftp_stage to scl3-na1b:/vol/ftp_stage. It will take a long time.
Making use of our SnapMirror demo licenses to copy this, instead of ndmpcopy.
The space is available for all the mounts listed above. All data is snapmirrored except for the stuff on 10.253.0.139, which is equallogic. That data will need to be migrated when the systems are ready to move. When that time comes, please open a bug for that.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.