Difference between revisions of "Bxp - BCP Notes"
From All n One's bxp software Wixi
(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...") |
|||
| Line 1: | Line 1: | ||
=<span dir="auto">BCP Notes</span>= | =<span dir="auto">BCP Notes</span>= | ||
| − | <div id="bodyContent" class="clearfix"><div id="contentSub">< | + | <div id="bodyContent" class="clearfix"><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 id="mw-content-text" lang="en-GB" dir="ltr" class="mw-content-ltr"> | + | 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>== | ==<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 | + | 1 - '''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. |
| − | 2 - '''File level - '''Our database files are backed up nightly. We currently hold 7 days in a | + | 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>== | ==<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 | + | 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>== | ==<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=== | ===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. | 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. | ||
Revision as of 13:10, 11 September 2019
Contents
1 BCP Notes
Below are set notes on bxp's back-up redundancy operations
1.1 2 Back-ups
1 - 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.
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.
1.2 3 Back-up recovery
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.
1.3 4 Logical Architecture - High Availability
bxp uses an n-Tier design architecture ( http://en.wikipedia.org/wiki/Multitier_architecture )
1.3.1 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
1.3.2 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.
The data from IIS is decrypted and stored in the database.
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 )
All data backups at this point are encrypted into Zip files using AES 256 encryption. ( http://www.winzip.com/aes_info.htm )
