353
edits
Changes
no edit summary
=<span dir="auto">BCP Notes</span>=
<div idclass="bodyContentclearfix" classid="clearfixbodyContent"><div id="contentSub">'''</div><div idspan class="jumpmw-toheadline-navnumber">1</span> Overview'''</div><div id="bs-bodytext"><div idclass="mw-content-text" lang="en-GB" dir="ltr" classid="mw-content-ltrtext"><div idlang="toc" class="toc"><div id="toctitle">==Contents==<span class="toctoggle"> [hide] </span></div>* [index.php/Bxp_en-_End_to_End_encryption_and_High_Availability#Overview <span class=GB"tocnumber">1</span><span classdir="toctext">Overview</span>]* <span class="tocnumber">2</span><span class="toctext">Back-ups<br /></span>* <span class="toctext"><span class="tocnumber">3 Recovery times</span><span class="toctext"><br /></span></span>* <span class="tocnumber">4</span><span class="toctext">Logical Architecture</span>** [index.php/Bxp_-_End_to_End_encryption_and_High_Availability#Web_Tier <span class="tocnumber">3.1</span><span class="toctext">Web Tier</span>]** [index.php/Bxp_-_End_to_End_encryption_and_High_Availability#Database_Tier <span class="tocnumberltr">3.2</span><span class="toctext">Database Tier</span>] </div>==<span id="Overview" class="mw-headline"><span class="mw-headline-number">1</span> Overview</span>==
Below are set notes on bxp's back-up redundancy operations
==<span id="Hosting" class="mw-headline"><span class="mw-headline-number">2</span> Back-ups</span>==
1 - '''Image Level -''' Snap shots are held of our Live serversweekly. These are available to for us to rollback the windows instance in the event of system failure.
2 - '''File level - '''Our database files are backed up nightly. We currently hold 7 days in a row followed by backup increments of one file per week dating back 6 months from the current date.
==<span id="Hosting" class="mw-headline">3 Back-up recovery</span>==
1 - '''Image Level -''' Snap shots are held of our Live servers. These are available for us to rollback the windows instance in the event of failure. The time for a image recovery can be from 2 hours up to 8 hours
2 -''' File level''' - For database files we can recover data from backup files 1-2 hours upon client request. Larger request (full system restore) can take up to 6-10 hours pending on the size of the clients system.
*Client requests can range from recovering a single record to a full system.
==<span id="Logical_Architecture" class="mw-headline">4 Logical Architecture - High Availability</span>==
bxp uses an n-Tier design architecture ( [[]http://en.wikipedia.org/wiki/Multitier_architecture http://en.wikipedia.org/wiki/Multitier_architecture] )
===This allows us to provide the client with no single point of failure. All resources have a replica waiting to take the load while we replace the defective server/service===
===<span class="mw-headline-number">34.1</span> Web Database TierBack-up===The web ''*Please note this back-up tier is implemented using the High Availability Microsoft Internet Information Server (IIS) again in an architecture way that allows numerous servers to be added as demand requiresnot used for data recovery. <br />It is finally at this tier a replica database server that the encrypted SSL packets from the users browser are decrypted and is used. Instructions at this stage usually require some form of database interaction. Communications from in the web servers to event that the live database tier are then encrypted using SSL over ODBCserver fails. ( [http:All file//dev.mysql.com/doc/refman/5.6/en/ssl-connections.html http://dev.mysql.com/doc/refman/5.6/en/ssl-connections.html] ) <br />At no point is decrypted data stored on recover will be done through the IIS server.back-up recover methods above''
Finally the data, such as a customer record, reaches the database tier. The data is stored in a primary server, with a secondary mirroring backup server in identical configuration logging the data.