Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
15 views2 pages

DataManagement Lab6 Part3

The document outlines the infrastructure availability of an organization, detailing key components such as servers and firewalls. It emphasizes the importance of high availability through strategies like deploying multiple application servers, automated backups, and network load balancing. Additionally, it discusses recovery operations, highlighting the need for defined recovery point and time objectives to minimize data loss and downtime.

Uploaded by

vkpshabnam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views2 pages

DataManagement Lab6 Part3

The document outlines the infrastructure availability of an organization, detailing key components such as servers and firewalls. It emphasizes the importance of high availability through strategies like deploying multiple application servers, automated backups, and network load balancing. Additionally, it discusses recovery operations, highlighting the need for defined recovery point and time objectives to minimize data loss and downtime.

Uploaded by

vkpshabnam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

INFRASTRUCTURE AVAILABILITY:

1) RECORD OF THE ORGANIZATIONS INFRASTRUCTURE:


 Primary server
 Backup servers
 Network firewall
 Storage server
 Storage devices
 Application server
 File server

2) SYSTEM DESIGN FOR HIGH AVAILABILITY:

i. DEPLOYING MULTIPLE APPLICATION SERVERS


Overburdened servers have a tendency to slow down or eventually crash. To maintain application
efficiency and minimise downtime, we must implement our application across a variety of servers.

ii. SCALING UP AND DOWN


Scaling your servers up or down depending on the demand and availability of the application is
another method for achieving high availability. At the server level, we can accomplish both vertical
and horizontal scalability.

iii. MAINTAINING AN AUTOMATED RECURRING ONLINE BACKUP SYSTEM

Automating backup ensures the safety of your critical business data in the event you forget to
manually save multiple versions of your files. It is a good practice that pays dividends under multiple
different circumstances, including internal sabotage, natural disasters and file corruption.

iv. IMPLEMENTING NETWORK LOAD BALANCING

We can increase the availability of application by implementing load balancing. If a server failure is
detected, the instances are seamlessly replaced and the traffic is then automatically redirected to
functional servers.

3) BACKUP SERVICES AND STORAGE


With backups, we can avoid losing both our data and customers’ data. Backups provide a solid
foundation for a business, and are useful in a number of situations. These include hard drive damage,
hacking, natural disaster or even human error. Few backup and storage services are mentioned below:

i. Acronis is the most powerful online-backup solution available for consumers, and includes
antivirus software and ransomware protection.
ii. Carbonite is a cloud-based backup and recovery software that provides end-to-end data
protection and compliance solutions.
iii. SSDs use integrated circuits to store data because they are faster and consume less power.

4) RECOVERY OPERATIONS

The Recovery operations are the business processes to be set up in order to get the business back up-
and-running during a disaster. Important indicators for defining DRP strategies are:

 The RPO (recovery point objective). This term refers to the maximum allowable data loss rate. It
is measured over a period of time.
 The RTO (recovery time objective). This refers to the maximum time that an application can
remain down before it is restarted.

The RTO and RPO for Uxer should be zero or nearby zero.

References:

https://www.kaseya.com/blog/2021/08/10/high-availability/
https://www.linode.com/docs/guides/introduction-to-high-availability/

You might also like