| Worksheet ID: |
1043 |
| Record Location: |
710 James Robertson Parkway
Andrew Johnson Tower, 9th Floor |
| File Arrangement: |
Numeric |
| Media Format Generated: |
Electronic |
| Media Format Stored: |
Electronic: Other |
| Date Range: |
1991 - current |
| Annual Accumulation: |
20 MB |
| Current Volume: |
137 MB |
| Record Value: |
Fiscal |
| Audit Requirements: |
Both |
| Reference Frequency: |
| Current Year per Month: |
6 |
| Past Year: |
2 |
| 2 - 5 Years: |
5 |
| Over 5 Years:
|
0 |
|
| Data Update Frequency: |
Yearly |
| Information Shared Outside of State: |
Yes |
| If Shared, List Agencies: |
National Center for Education Statistics |
| Essential Record: |
No |
| Essential Record Stored: |
|
| Essential Record Media Type: |
Electronic |
| Confidential: |
No |
| Confidential Legal Citation: |
|
| Media Recommendation: |
Current Format |
| Media Recommendation Other: |
|
| Agency Retention: |
5 Years, 0 Months |
| Agency Retention - Years Active: |
|
| Agency Retention - Years Inactive: |
|
| Records Center Retention Period: |
0 |
| Final Disposition after Retention Expires: |
Destroy |
| Legal Citation: |
TCA 49-3-316 |
| Record Sample: |
No Sample |
| Legal Documentation: |
No Legal Documentation |
| Electronic Records Plan Inventory |
| System Name: |
Harris, Mackessy, and Brennan (HMB) eGrants Web Application |
| IT-ABC Number: |
|
| Hardware Description: |
Windows Azure runs in data centers managed and operated by Microsoft Global Foundation Services (GFS). These geographically dispersed data centers comply with key industry standards, such as ISO/IEC 27001:2005, for security and reliability. They are managed, monitored, and administered by Microsoft operations staff that have years of experience in delivering the world’s largest online services with 24 x 7 continuity.
Windows Azure SQL Database mitigates outages due to failures of individual devices, such as hard drives, network interface adapters, or even entire servers. Data durability and fault tolerance is enhanced by maintaining multiple copies of all data in different physical nodes located across fully independent physical sub-systems such as server racks and network routers. At any one time, Windows Azure SQL Database keeps three replicas of data running—one primary replica and two secondary replicas. Windows Azure SQL Database uses a quorum based commit scheme where data is written to the primary and one secondary replica before we consider the transaction committed. If the hardware fails on the primary replica, the Windows Azure SQL Database detects the failure and fails over to the secondary replica. In case of a physical loss of the replica, Windows Azure SQL Database creates a new replica automatically. Therefore, there are at least two physical transactionally consistent copies of your data in the data center.
|
| Software Description: |
Application is hosted by Microsoft Azure and consists of the following
sections hosted in the cloud:
* Microsoft Azure Cloud Service
* Microsoft Azure SQL Database
* Microsoft Azure Cloud Storage
* Microsoft Azure Virtual Machine
Of these sections, the Cloud Storage is set up to be Geo-Redundant, meaning that it consists of three redundant copies in the Primary Data Center (North Central) and three additional redundant copies in a Secondary Data Center (South Central). On a failure in the North Central Data Center,
Microsoft Azure will automatically forward requests for the storage data to the secondary data center, so no action is required for recovery.
|
| System Location: |
The Cloud Storage is set up to be Geo-Redundant, meaning that it consists of three redundant copies in the Primary Data Center (North Central) and three additional redundant copies in a Secondary Data Center (South Central). On a failure in the North Central Data Center, Microsoft Azure will automatically forward. |
| Backup Procedures: |
1- Create New Cloud Service; HMB creates cloud service in another, stable region. 2- Modify Cloud Service Configuration; HMB modifies the solution configuration to target this new cloud service. 3- Provide Updated DNS; HMB provides client with address of new cloud site, for example tennesseegmsdr.cloudapp.net. 4- Update DNS Entry; Client Updates DNS settings to point client address to the new cloud site. 5- Deploy New Service; HMB deploys updated solution to new cloud service. |
| Disaster Recovery: |
1- Create New Server/Database; HMB creates a SQL database server and database in another, stable region. 2- Load Database; HMB loads most recent database; backup onto this new database. 3- Modify Cloud Service Configuration; HMB updates solution configuration to point to this new server and database. 4- Deploy Cloud Service; HMB deploys updated solution to cloud service. This plan supports the recovery of the above named application/system using only documentation and data stored remotely to the primary recovery location. This plan is designed to contain the information to support initial recovery during a disaster, i.e., recovery at a Disaster Recovery site. It does not contain the details required for reinstatement, the plan for which would be built at the time of a disaster and based on this plan. |
| Data Migration Description: |
These geographically dispersed data centers comply with key industry standards, such as ISO/IEC 27001:2005, for security and reliability. They are managed, monitored, and administered by Microsoft operations staff that have years of experience in delivering the world’s largest online services with 24 x 7 continuity. |
| Metadata Description: |
This plan supports the recovery of the above named application/system using only documentation and data stored remotely to the primary recovery location. This plan is designed to contain the information to support initial recovery during a disaster, i.e., recovery at a Disaster Recovery site. It does not contain the details required for reinstatement, the plan for which would be built at the time of a disaster and based on this plan. |
