Tony

Administrators
  • Posts

    2,435
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Tony

  1. The server is being shutdown now to run the file system check.
  2. The aggregate switch fas05a.sr01.sjc01 has been replaced with new hardware, and the network has been normalized. The maintenance is complete.
  3. The aggregate switch fas05a.sr01.sjc01 has been replaced with new hardware, and the network has been normalized. The maintenance is complete.
  4. On Monday April 30th starting at 9am PDT we will be taking the sjc003 server down to run a file system check on one of the partitions the operating system is reporting to have issues. This is necessary maintenance as otherwise the problem could result in an unplanned outage and potential data loss if it's file system check is not done within a reasonable time frame. We've set aside a window of 4 hours meaning the window ends at 1pm PDT. We estimate the actual file system check will take less than two hours to be completed so the estimated downtime will be around 2 hours. Date: 04/30/2012 Start time (PDT): 9:00am End time (PDT): 1:00pm Duration: 4 hours Estimated Down Time: 120 minutes
  5. SCHEDULED Maintenance - [Maintenance ID 4714300] fas05a.sr01.sjc01 SJC01 [04/29/2012] Date: Tuesday, April 29, 2012 (04/29/2012) Start Time: 9:01 PM PDT End Time: 01:01 AM PDT Services affected: Public Network Connectivity Location: SJC01 Duration: 4 hours Network Engineers have identified a hardware issue on an aggregate switch, fas05a.sr01.sjc01, which provides connectivity for our server sjc004. To prevent an unplanned outage resulting in significant downtime, Engineers will be replacing the switch per the manufactures instructions during a scheduled maintenance window. During this maintenance, customer servers may experience higher latency than normal on the public network. The aggregate switch fas05a.sr01.sjc01 has displayed sings of increased instability. As a precaution against further network interruptions this maintenance has been scheduled for today.
  6. SCHEDULED Maintenance - [Maintenance ID 4714300] fas05a.sr01.sjc01 SJC01 [04/29/2012] Date: Tuesday, April 29, 2012 (04/29/2012) Start Time: 9:01 PM PDT End Time: 01:01 AM PDT Services affected: Public Network Connectivity Location: SJC01 Duration: 4 hours Network Engineers have identified a hardware issue on an aggregate switch, fas05a.sr01.sjc01, which provides connectivity for our server sjc003. To prevent an unplanned outage resulting in significant downtime, Engineers will be replacing the switch per the manufactures instructions during a scheduled maintenance window. During this maintenance, customer servers may experience higher latency than normal on the public network. The aggregate switch fas05a.sr01.sjc01 has displayed sings of increased instability. As a precaution against further network interruptions this maintenance has been scheduled for today.
  7. I handled your ticket for you but please understand sales and billing are available during business hours which is Monday-Friday 9am to 5pm EDT.
  8. Hello, Our Sales and billing are not 24/7 and a Saturday is outside business hours which is why you will get a delayed response.
  9. This maintenance has been canceled and will be scheduled at a later date.
  10. Starting on Saturday April 21st we will be migrating the Jupiter server to new higher end hardware as well as better system configuration. We feel this will benefit all users on the Jupiter server. We estimate this will be completed no later than Tuesday April 24th. We expect no more than 5 minutes of downtime per account as we will be moving accounts to the new server then re-routing the IP address to the new hardware. This means there will be no changes to DNS and as a result no dns propagation issues. In our experience our migration method means the large majority of users will not even realize that they've switched servers. If you do however run into any issues do not hesitant to contact us as our system administrators are prepared to resolve any issues experienced. The new Jupiter server will be similar to that of our recent deployment of servers: Old Jupiter: Dual Xeon E5520 24GB RAM 4x300GB Raid-10 New Jupiter: Dual Xeon X5670 24GB RAM 4x600GB Raid-10 So this is a pretty big upgrade as it will have four additional CPU cores with 8 to the operating system counting hyper threading. It will also be using 600GB disks over 300GB disks of the old system. Once the migration starts as accounts transfer over they will go onto the newjupiter hostname until the entire migration is complete when the new hardware will become jupiter and the old server oldjupiter. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 04/21/2012 End Date: 04/24/2012 Estimated Down Time: less than 5 minutes Duration: 4 days
  11. The drive has been replaced and has finished rebuilding.
  12. On Tuesday April 17th we will be replacing a failed drive on the Mirage server between 9am and 12pm CDT. We do not expect any downtime to swap out the failed drive as the system is hot swap capable. Once the drive is replaced disk I/O may be slightly slower than usual while the drive rebuilds. Date: 04/17/2012 Start time (CDT): 9:00am End time (CDT): 12:00pm Estimated Down Time: 0 minutes
  13. The drive has finished rebuilding.
  14. The drive has been replaced and is currently rebuilding.
  15. On Monday April 16th we will be replacing a failed drive on the Blackbird server between 9am and 12pm PDT. We do not expect any downtime to swap out the failed drive as the system is hot swap capable. Once the drive is replaced disk I/O may be slightly slower than usual while the drive rebuilds. Date: 04/16/2012 Start time (PDT): 9:00am End time (PDT): 12:00pm Estimated Down Time: 0 minutes
  16. This has been completed.
  17. This has been completed.
  18. This has started.
  19. We're adjusting this window to go until the end of Friday as the migration has gone slower than expected.
  20. Starting on Friday April 13th we will be migrating the Lightning server to new higher end hardware as well as better system configuration. We feel this will benefit all users on the Lightning server. We estimate this will be completed no later than Sunday April 15th. We expect no more than 5 minutes of downtime per account as we will be moving accounts to the new server then re-routing the IP address to the new hardware. This means there will be no changes to DNS and as a result no dns propagation issues. In our experience our migration method means the large majority of users will not even realize that they've switched servers. If you do however run into any issues do not hesitant to contact us as our system administrators are prepared to resolve any issues experienced. The new Lightning server will be similar to that of our recent deployment of servers: Old Lightning: Dual Xeon E5620 24GB RAM 4x300GB Raid-10 New Lightning: Dual Xeon X5670 24GB RAM 4x600GB Raid-10 So this is a pretty big upgrade as it will have four additional CPU cores with 8 to the operating system counting hyper threading. It will also be using 600GB disks over 300GB disks of the old system. Once the migration starts as accounts transfer over they will go onto the newlightning hostname until the entire migration is complete when the new hardware will become lightning and the old server oldlightning. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 04/13/2012 End Date: 04/15/2012 Estimated Down Time: less than 5 minutes Duration: 3 days
  21. This is well underway
  22. This has been completed.
  23. Starting on Tuesday April 10th we will be migrating the Tornado server to new higher end hardware as well as better system configuration. We feel this will benefit all users on the Tornado server. We estimate this will be completed no later than Thursday April 12th. We expect no more than 5 minutes of downtime per account as we will be moving accounts to the new server then re-routing the IP address to the new hardware. This means there will be no changes to DNS and as a result no dns propagation issues. In our experience our migration method means the large majority of users will not even realize that they've switched servers. If you do however run into any issues do not hesitant to contact us as our system administrators are prepared to resolve any issues experienced. The new Tornado server will be similar to that of our recent deployment of servers: Old Tornado: Dual Xeon E5520 24GB RAM 4x300GB Raid-10 New Tornado: Dual Xeon X5670 24GB RAM 4x600GB Raid-10 So this is a pretty big upgrade as it will have four additional CPU cores with 8 to the operating system counting hyper threading. It will also be using 600GB disks over 300GB disks of the old system. Once the migration starts as accounts transfer over they will go onto the newtornado hostname until the entire migration is complete when the new hardware will become tornado and the old server oldtornado. If you have any questions regarding the maintenance do not hesitate to contact us. Our system administration department is available to answer any questions regarding this. Start Date: 04/10/2012 End Date: 04/12/2012 Estimated Down Time: less than 5 minutes Duration: 3 days
  24. This is well underway
  25. We do not offer anonymous FTP and have no intentions of ever offering it unfortunately.