Bxp - BCP Notes - Revision history

Thomas Glennon at 14:02, 11 September 2019

2019-09-11T14:02:10Z

Thomas Glennon at 12:10, 11 September 2019

2019-09-11T12:10:07Z

Thomas Glennon: Created page with "=BCP Notes=

2019-09-10T15:24:17Z

Created page with "=<span dir="auto">BCP Notes</span>= <div id="bodyContent" class="clearfix"><div id="contentSub"></div> <div id="jump-to-nav"></div> <div id="bs-bodytext"><div id="mw-content-t..."

New page
=<span dir="auto">BCP Notes</span>=
<div id="bodyContent" class="clearfix"><div id="contentSub"></div>
<div id="jump-to-nav"></div>
<div id="bs-bodytext"><div id="mw-content-text" lang="en-GB" dir="ltr" class="mw-content-ltr"><div id="toc" class="toc"><div id="toctitle">
==Contents==
<span class="toctoggle"> [hide] </span></div>
* [index.php/Bxp_-_End_to_End_encryption_and_High_Availability#Overview <span class="tocnumber">1</span><span class="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="tocnumber">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 servers. These are available to us to rollback the windows instance in the event of failure

2 - '''File level - '''Our database files are backed up nightly. We currently hold 7 days in a roll 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 up to 8 hours

2 -''' File level''' - For database files we can recover data from backup files 1-2 hours upon client request.

==<span id="Logical_Architecture" class="mw-headline">4 Logical Architecture - High Availability</span>==
[[]]

===<span class="mw-headline"><span class="mw-headline-number">bxp uses an n-Tier design architecture ( [http://en.wikipedia.org/wiki/Multitier_architecture http://en.wikipedia.org/wiki/Multitier_architecture] )</span></span>===
===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">3.1</span> Web Tier===
The web 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 requires.

<br />It is finally at this tier that the encrypted SSL packets from the users browser are decrypted and used. Instructions at this stage usually require some form of database interaction. Communications from the web servers to the database tier are then encrypted using SSL over ODBC. ( [http://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 the IIS server.

===<span id="Database_Tier" class="mw-headline"><span class="mw-headline-number">3.2</span> Database Tier</span>===
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.

<br />The data from IIS is decrypted and stored in the database.

<br />However the hard drives in the database server are also encrypted at the operating system level. The term for this is that "the data is encrypted at rest". ( [http://technet.microsoft.com/en-us/library/cc732774.aspx http://technet.microsoft.com/en-us/library/cc732774.aspx] )

<br />All data backups at this point are encrypted into Zip files using AES 256 encryption. ( [http://www.winzip.com/aes_info.htm http://www.winzip.com/aes_info.htm] )

</div>
</div>
</div>

@@ Line 1: / Line 1: @@
 =<span dir="auto">BCP Notes</span>=
-<div id="bodyContent" class="clearfix"><div id="contentSub">'''<span class="mw-headline-number">1</span> Overview'''</div>
+<div class="clearfix" id="bodyContent"><div id="contentSub">'''<span class="mw-headline-number">1</span> Overview'''</div>
-<div id="bs-bodytext"><div id="mw-content-text" lang="en-GB" dir="ltr" class="mw-content-ltr">
+<div id="bs-bodytext"><div class="mw-content-ltr" id="mw-content-text" lang="en-GB" dir="ltr">
 Below are set notes on bxp's back-up redundancy operations
@@ Line 11: / Line 10: @@
 - '''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.
@@ Line 28: / Line 28: @@
 ===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===
 ===4.1 Database Tier Back-up===
 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.

@@ Line 1: / Line 1: @@
 =<span dir="auto">BCP Notes</span>=
-<div id="bodyContent" class="clearfix"><div id="contentSub"></div>
+<div id="bodyContent" class="clearfix"><div id="contentSub">'''<span class="mw-headline-number">1</span> Overview'''</div>
-<div id="jump-to-nav"></div>
+<div id="bs-bodytext"><div id="mw-content-text" lang="en-GB" dir="ltr" class="mw-content-ltr">
-<div id="bs-bodytext"><div id="mw-content-text" lang="en-GB" dir="ltr" class="mw-content-ltr"><div id="toc" class="toc"><div id="toctitle">
+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>==
-- '''Image Level -'''  Snap shots are held of our Live servers. These are available to us to rollback the windows instance in the event of failure
+- '''Image Level -'''  Snap shots are held of our Live servers weekly. These are available for us to rollback the windows instance in the event of system failure.
-- '''File level - '''Our database files are backed up nightly. We currently hold 7 days in a roll followed by backup increments of one file per week dating back 6 months from the current date
+- '''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>==
-- '''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 up to 8 hours
+- '''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
 ==<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">3.1</span> Web Tier===
+===4.1 Database Tier Back-up===
 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.