Tony

Administrators
  • Posts

    2,435
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Tony

  1. This has been completed.
  2. This has been completed.
  3. This has been completed.
  4. This has been completed.
  5. This has been completed.
  6. This has been completed.
  7. This has been completed.
  8. This has been completed.
  9. This has been completed.
  10. This has been completed.
  11. Just in case things overlap and our site is down http://status.hawkhost.com/ will be live the entire time and contain up to date information.
  12. Just in case things overlap and our site is down http://status.hawkhost.com/ will be live the entire time and contain up to date information.
  13. Just in case things overlap and our site is down http://status.hawkhost.com/ will be live the entire time and contain up to date information.
  14. Just in case things overlap and our site is down http://status.hawkhost.com/ will be live the entire time and contain up to date information.
  15. Just in case things overlap and our site is down http://status.hawkhost.com/ will be live the entire time and contain up to date information.
  16. I believe you can add a file cpbackup-exclude.conf which can exclude folders from being backed up. Then I think you can do something like this: public_html/addondomain.com It's line by line so one exclusion per line. Although I'm not positive on the exact syntax or if it'll work.
  17. This has been completed. As always if you run into any issues contact us as soon as possible.
  18. There is a process limit on the SSH end so if you have more than x amount it won't let you spawn anymore. On the web / PHP side there is a 10 process limit. The web server will keep a maximum pool of 10 for requests. This is 10 simultaneous requests keep in mind which is quite a bit. Even then it does not stop requests it just puts them on wait for a PHP process to open up to be used. With process limits if you're hitting them and it's causing issues typically you need your owm server at that point anyways so not something to really worry about.
  19. 75% completed at this point. It should probably be finished today which is way ahead of schedule.
  20. This has started.
  21. We are bumping this forward a day to start Thursday to hopefully avoid doing any migration during this maintenance window: http://forums.hawkhost.com/showthread.php?t=705
  22. There will be emergency network maintenance on FCR01 which our Titan server is on. This window is on Monday November 30th starting at 12:30am PST and lasting until 1:30am PST. Although the window is for 1 hour we estimate that there will only be a down time of 15-20 minutes. This maintenance is necessary to correct an issue that could cause network interruptions that would not be scheduled. Further information about this can be found at: Emergency Network Maintenance [11/30/2009] Emergency Data Center Maintenance - FCR01.SEA01 [11/30/2009] Date: Monday, November 30, 2009 (11/30/2009) Start time (PST): 00:30 End time (PST): 01:30 Services affected: Public Network Location: SEA01 Duration: 1 hour
  23. There will be emergency network maintenance on FCR01 which our Bosco server is on. This window is on Monday November 30th starting at 2:00am CST and lasting until 3:00am CST. Although the window is for 1 hour we estimate that there will only be a down time of 15-20 minutes. This maintenance is necessary to correct an issue that could cause network interruptions that would not be scheduled. Please note this only affects accessing backups via your cPanel. Our backups will still be made during the window as it does not affect our private network. Further information about this can be found at: Emergency Network Maintenance [11/30/2009] Emergency Data Center Maintenance - FCR04.DAL01 [11/30/2009] Date: Monday, November 30, 2009 (11/30/2009) Start time (CST): 02:00 End time (CST): 03:00 Services affected: Public Network Location: DAL01 Duration: 1 hour
  24. There will be emergency network maintenance on FCR02 which our NS2 server is on. This window is on Monday November 30th starting at 1:00am CST and lasting until 2:00am CST. Although the window is for 1 hour we estimate that there will only be a down time of 15-20 minutes. This maintenance is necessary to correct an issue that could cause network interruptions that would not be scheduled. Further information about this can be found at: Emergency Network Maintenance [11/30/2009] Emergency Data Center Maintenance - FCR02.DAL01 [11/30/2009] Date: Monday, November 30, 2009 (11/30/2009) Start time (CST): 01:00 End time (CST): 02:00 Services affected: Public Network Location: DAL01 Duration: 1 hour
  25. There will be emergency network maintenance on FCR01 which our NS1 server is on. This window is on Monday November 30th starting at 1:00am EST and lasting until 2:00am EST. Although the window is for 1 hour we estimate that there will only be a down time of 15-20 minutes. This maintenance is necessary to correct an issue that could cause network interruptions that would not be scheduled. Further information about this can be found at: Emergency Network Maintenance [11/30/2009] Emergency Data Center Maintenance - FCR01.WDC01 [11/30/2009] Date: Monday, November 30, 2009 (11/30/2009) Start time (EST): 01:00 End time (EST): 02:00 Services affected: Public Network Location: WDC01 Duration: 1 hour