VAN Downtime Announcement: Sun, Jun 23, 2019 & Sun, Jul 7, 2019

Created by Stella Pauline, Modified on Thu, 8 Sep, 2022 at 4:14 PM by Stella Pauline

Logo

Data Center Migration

Below please note the final confirmed dates for our migration to a new data center. As previously communicated, before moving our servers, we must start the migration with our multi-service database server, which will affect all NGP VAN sites at the same time. 


This work will take place Sunday, June 23, 2019 from 6 AM to 9 AM Eastern and the second date will be Sunday, July 7, 2019from 6 AM to 9 AM Eastern.


Please note that we’ve been able to shorten the maintenance window by an hour on each day. We understand there is no good time to perform maintenance work, but Sundays are historically low usage days and most site activity – even in advance of primaries or filing deadlines – occurs after 9 AM on Sundays. 


We’ve put together some specific questions below about this work, what is and isn’t affected, and what to expect. Please read the FAQs below carefully. If you have additional questions, please don’t hesitate to contact us directly.


- - - - -

What work are you performing?

We are migrating many of our core workloads between data centers. The first server to migrate performs certain processes and jobs with other databases. As a result, all sites will be affected.


How long will my database be unavailable?

Works starts at 6:00 AM Eastern and access to all sites will fully return by 9:00 AM Eastern.


Will my Online Action Forms remain available? What will supporters experience when they visit those pages?

Online Action forms will remain available during the maintenance windows on June 23 and July 7. Any submissions via your forms will continue to process and will then be recorded to the database after the server comes back online.   


What will happen if I have Email Series or other Targeted Emails scheduled to go out during that time?

Any emails queued during the window will remain queued and go out shortly after 9 AM, once the database server returns to service.

If you don't want to wait until 9 AM to send your emails, please schedule them to send before midnight the day prior to this maintenance window.


Recurring Contributions often happen around 6 AM. What will happen with those?

These will process as normal. The maintenance window is timed to start at the conclusion of these jobs. If this process ends up running long, they will resume at the conclusion of the maintenance window.


What about other nightly jobs that happen during that window (custom imports/exports, Counts and Crosstabs)?

These will run as normal. The maintenance window is timed to start at the conclusion of these jobs. If those end up running long, they will resume at the conclusion of the maintenance window.


What about API-related tasks that happen during this window?

API calls to these databases will return an error (maintenance mode) and API consumers should plan accordingly to resend failed attempts made during this window.


What about Pipeline? Will that be disrupted?

Pipeline will be paused at the beginning of the maintenance window and will resume automatically at its conclusion.


What about Open Virtual Phone Bank?

Open Virtual Phone Bank will not be accessible during the maintenance window, though the work is early enough in the morning that it should not interfere with call time. 


Is this the only work planned as part of the migration?

No, individual sites will also experience an additional maintenance window when your site’s database server migrates. The expected migration window will be sometime between late June and late August, and in the early morning hours. We will be in touch with the specific migration date for your site soon.

MARK PULEO

Vice President of Client Services, NGP VAN

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article