/
2017-08-22 ServerAD

2017-08-22 ServerAD

Owned by Priya Srinivasan
Last updated: Aug 29, 2017Version comment

Date

 

Attendees

Agenda

  • Agenda:

    We are currently planning DR for filenet @ SDSC. No timelines have been established. 

    All Filenet VMs currently use ServerAD DC. Meeting is to discuss if there are plans to create ServerAD redundancy at SDSC and/or AWS.  Need to evaluate cost, LOE and timeline. 

    Also discuss estimated timeline for AD DC creation at AWS and/or SDSC.

Discussion items

 TopicNotes
1.

ServerAD @ SDSC

Do we need it?

LOE

Cost

Timeline

  • DBA team would need to have ServerAD and AD DC @ SDSC
  • Currently using cached credentials @ SDSC. This will work if campus DC is down
    • Will not work in complex networking setup
  • ServerAD is typically preferred for restricted data per DB team
  • LOE - Effort is similar to AD DC. Need to setup multiple sites
    • Will determine which site to connect based on proximity
    • Requires coordination with network and security team
  • Limited pipeline
  • Exchange is on higher priority track
  • Check with WSG by end of Sep regarding AD DC setup @ SDSC and establish timeline for Sever AD
  • Can Filent move to AD DC instead of Server AD? - Question raised by Jeff
  • Same specs as AD DC @ SDSC

 

ServerAD @ AWS

Do we need it?

LOE

Cost

Timeline

  • If we migrate apps that require ServerAD, do not migrate them until they migrate to ServerAD or if the application server switches to AD DC.
 

AD DC @ SDSC

Do we need it?

LOE

Cost

Timeline

  • End of September 2017

 

 

Action items

  •  Priya Srinivasan to add above 5 servers to AWS migration timeline  
  • Priya Srinivasan Check with David S and Derek on MTA Linux migration timeline