AWS DR Validation

We have been asked to validate that the DR environment is truly ready in the event of a disaster.  The CFA team have met and discussed the project and what will be required to test the DR completely.

1. Validate the UI by using a "dummy" - static database that we can write to - Database is created and called cfadrtest.  These entities exist in that database with 13 months of data: 
   • 123 00198 - Northwest Arkansas Mall
     271 00442 - College Mall
     875 01580 - Castle Rock FSU
     32 00048 - Chapel Hills Mall
     671 01171 - Dulles Town Crossing FSU
     588 01023 - Kingsland FSU
     902 01640 - St. Johns Town Center FSU
     1041 01919 - Denton Towne Crossing FSU
     1810 02693 - George Washington FSU
     1287 70049 - Truett's Grill Griffin
     371 00636 - Perimeter Pointe FSU
2. Validate the AS/2 server by sending a test order (completed on 10/9 by SaaS Ops and Stacy Privalova)
   1. Validate that the log shipping truly has all the data that the production database does by comparing a subset of the data - This is the actionable item for Development.  SaaS Ops will change all necessary config files to point to the correct database (see Jira ticket: MXCHG-3310 in HS JIRA).    Once Development is ready with scripts, Stacy Privalova will validate the environment by:
      1. Having SaaS Ops switch to the test config files  (Static DB (CFADRTest))
      2. Validating data by using the scripts provided by development
      3. Validating ordering, counting, etc.
      4. Once completed, having SaaS Ops switch the config files back