a backup as a service (baas) software solutionintranet.pop-sc.rnp.br/...de_backup_com_bacula.pdf ·...
TRANSCRIPT
A Backup as a Service (BaaS) Software Solution
Heitor Medrado de [email protected]
Departamento de Ciencia da ComputacaoInstituto de Ciencias Exatas
Universidade de Brasılia
11 de Setembro de 2017
1
IntroductionLiterature Review
The Proposal
Topics
1 IntroductionObjective
2 Literature ReviewCloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
3 The ProposalScopeObjectivesScheduleBibliography
2
IntroductionLiterature Review
The ProposalObjective
Topics
1 IntroductionObjective
2 Literature Review
3 The Proposal
3
IntroductionLiterature Review
The ProposalObjective
Introduction
Backup is the replica of any data that can be used torestore its original form [Guise]
Digital data created worldwide more than doubles everytwo years - 44 zetabytes in 2020 [IDC]
Backup is old and popular, but most backup systems areoutdated [Russel et. al]
Modern backup should provide integration to thegrowing Cloud [Russel]
4
IntroductionLiterature Review
The ProposalObjective
Objective
The present study aims to propose and deploy a Backup as aService software solution
Cloud/backup parameters
Cloud backup challenges
Architectures
BaaS system requirements
Prototype construction and deploy
5
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Topics
1 Introduction
2 Literature ReviewCloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
3 The Proposal
6
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Cloud Computing
Shift data and computational services from individualdevices to distributed architectures [Armbrust, Buyya]
Global market revenues growing from U$ 67 billions by2015 to U$ 241 billions by 2020 [Columbus, Ried et al.]
5 characteristics, 3 service categories, 4 deploymentmodels [NIST]
7
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Cloud Disaster Recovery Model
DR is persistent problem for the CSP - must provideservices to their customers even if a data center is down
Data, application and system level [Khoshkholghi et al.]
Figure: Comparison of DR models [Raju et al.]
8
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
DR Parameters [Alhazmi and Malaiya]
RPO ∝ 1
FB(1)
RTO = fraction of RPO +5∑
jmin
Tj (2)
Minimum RPO and RTO.
Minimal impact on the normal system operation.
Should be geographically separated.
Application shall be restored to a consistent state.
DR solution must guarantee integrity, privacy andconfidentiality.
9
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Cloud DR Challenges
Dependency.
Cost (initializing, ongoing and potential disaster costs).
Failure Detection.
Security.
Replication Latency.
Limited Data Transmission Capabilities.
Increasing Data Storage Demand.
Lack of Redundancy.
10
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Remote Backup to the Cloud [Camacho et al.]
Local Data CenterBackup Clients
TLS / Data Encryption
Cloud StorageBackup Service
Figure: A Cloud Environment for Backup and Data Storage Architecture
11
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Local Backup from the Cloud
Figure: Local Backup Architecture [Javaraiah]
12
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Geographical Redundancy and Backup (GRB)
Figure: GRB Architecture [Pokharel et al.]
13
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Inter-Private Cloud Storage (IPCS)
Figure: The Inter-Private Cloud Storage architecture [Jian-hua and Nan]
14
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Secure-Distributed Data Backup (SDDB)
Figure: Basic configuration of the SDDB Architecture [Ueno et al.]
15
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
BaaS Provider Requirements [Ismail et al., Rimal et al.]
Autonomy.
Cloud Scalability.
Self-description.
Fault-tolerance.
Interoperability.
Load Balancing.
Multi-party.
Multi-Tenancy.
Optimal Provisioned Infrastructure Usage.
Quality-of-Service.
Standard Interface.
Storage and Data Management.
Workload Management.
16
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
BaaS User’s Requirements [Ismail et al., Rimal et al.]
Adaptability and Learning.
Automation.
Backup Standardization.
Data Consistency (Application specific, Crash andFile-system).
Data Integrity.
Firewall Protected or NATed Clients Backup.
Non-disruptive Backup.
Service Level Agreements (SLAs).
User-Centric Privacy.
User Consumption-based Billing and Metering.
User Experience (UX).
17
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
BaaS Candidate Solutions
Figure: Magic Quadrant for Data Center Backup and Recovery Software[Russel].
18
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
BaaS Candidate Solutions
Figure: Backup Software Solutions Google Queries for the Last 5 years[Google].
19
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
BaaS Candidate Solutions Comparison
Table: BaaS focused Backup Software Comparison
Solution S3 Stor-age Sup-port
Self-serviceportal?
NumberofPlugins
U$ Monthly Priceper Client
Arcserve Yes No 4 3.08-7.59Bacula Enterprise Yes No 17 3.90-16.90Bareos Yes No 5 5.46-52.45Commvault Yes Yes 22 12.71-31.66EMC No No 9 38.25 or moreSpectrum Protect Yes No 10 90.66-146.67Veeam No Yes 7 12.25Veritas Netbackup No No 14 10.58-332.91
20
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
The Overlying Backup Software
Bacula is the 3rd most popular enterprise multi-platformserver backup system, and open source [Google Trends]
Full, differential, incremental, copy and migratemultiplexed jobs supported
Compression, block deduplication, backups from FIFO,communication and data encryption [Sibbald]
Job 1 Data and Metadata
Job 2 Data and Metadata
Job 3 Data and Metadata
Figure: Bacula traditional volume writing format.
21
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Bacula Architecture
Figure: Bacula Services Distribution and Network Ports [Preston].
22
IntroductionLiterature Review
The Proposal
Cloud ComputingDisaster RecoveryArchitectureCloud Backup Macro RequirementsThe Overlying Backup Software
Bacula Features
General Features (organization, resource efficiency,architecture multi-thread etc.).
Job Features(scheduler, job types, multiplexing etc.).
Interface Features (CLI, GUI, REST, monitoring, multi-partyetc.).
Catalog Features (SQL, file browsing, pruning routines etc.).
Storage Features (tape, Tape-Library, disks, NAS, NDMP, S3,object storage etc.).
Data Reducing Features (compression, deduplication etc.).
Security Features (backup server DR, backup files checksum,storage integrity verification etc.).
Specific Applications Backup (virtual machines, databases,LDAP bases, system state etc.).
23
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Topics
1 Introduction
2 Literature Review
3 The ProposalScopeObjectivesScheduleBibliography
24
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Choosen ArchitectureRemote Backup to the Cloud
Local Data CenterBackup Clients
TLS / Data Encryption
Cloud StorageBackup Service
Figure: A Cloud Environment for Backup and Data Storage Architecture.
25
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Choosen Requirements
Id Requirement Macro Re-quirement
2 Shall contain interactive illustration ordemonstration to instruct unaware users.
adaptabilityand learning
9 Shall provide the usage of a Bacula singleinstance of the object code and database inorder to support multiple customers.
multi-tenancy
12 Shall be able to easily create new tenants automation16 Shall involve feedback of end-user on the in-
terface design, and deployuser experience
26
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Objectives
This work aims to deploy a Backup as a Service solution under theRemote Backup to the Cloud architecture. In order to achieve whatis aimed the following specific Objectives have been determined.
1 To enroll cloud backup challenges.
2 To find current proposed cloud backup architectures.
3 To determine what BaaS features must be added totraditional backup software.
4 To deploy, evaluate and validate the proposal prototype.
27
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Activities
1 Architecture Design and Adjustment. Verify and documentthe technical specifications, boundaries and conditions of theexperiment.
2 Determine performance metrics, system and workloadparameters. Select evaluation techniques.
3 Prototype Development. Description and documentation offeatures deploy and inner workings.
4 Validation. Analyze and interpret data. Present the results.
5 Prototype Adjustments.
6 Dissertation Writing.
7 Defense.
8 Scientific Papers Writing.
28
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
Activities
Table: Research activities schedule.
Act. Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul
1 X X X
2 X X
3 X X X X X X
4 X X X
5 X X X
6 X X X X X
7 X
8 X X X X X X X
29
IntroductionLiterature Review
The Proposal
ScopeObjectivesScheduleBibliography
1 P. d. Guise, ”Enterprise Systems Backup and Recovery”. CRC Press, 2008.2 ”The Digital Universe of Opportunities: Rich Data and the Increasing Value of the Internet of Things.”
[Online]. Available: https: //www.emc.com/leadership/digital-universe/2014iview/executive-summary.htm3 D. Russell, P. Rinnen, and R. Rhame, ”Magic Quadrant for Data Center Backup and Recovery Software”,
2016.4 D. Russel, ”The Future of Backup May Not Be Backup”, 2011.5 M. Armbrust, I. Stoica, M. Zaharia, A. Fox, R. Griffith, A. D. Joseph, R. Katz, A. Konwinski, G. Lee, D.
Patterson, and A. Rabkin, ”A view of cloud computing”, Communications of the ACM, vol. 53, no. 4, p.50, Apr. 2010.
6 R. Buyya, J. Broberg, and A. Goscinski, Cloud computing: principles and paradigms. USA: Wiley, 2011.7 L. Columbus, ”Roundup Of Cloud Computing Forecasts”, 2017.8 S. Ried, H. Kisker, and A. Bartels, ”Sizing The Cloud”, 2011.9 P. Mell and T. Grance, ”The NIST Definition of Cloud Computing,” 2011.
10 M. A. Khoshkholghi, A. Abdullah, R. Latip, S. Subramaniam, and M. Othman, ”Disaster Recovery inCloud Computing: A Survey”, Computer and Information Science, vol. 7, no. 4, p. 39, Sep. 2014.
11 M. R. Raju, J. P. Prakash, and G. R. Rao, ”Disaster Recovery of Servers using Virtualized CloudComputing”, 2012.
12 O. Alhazmi and Y. Malaiya, ”Evaluating Disaster Recovery Plans Using the Cloud”, 2013.13 H. Camacho, A. Brambila and A. Pena, ”A Cloud Enviroment for Backup and Data Storage”, 2014.14 V. Javaraiah, ”Backup for cloud and disaster recovery for consumers and SMBs”, in Advanced Networks
and Telecommunication Systems, 2011 IEEE 5th International Conference on. IEEE, 2011, pp. 1?3.15 M. Pokharel, S. Lee, and J. S. Park, ”Disaster Recovery for System Architecture Using Cloud Computing.”
IEEE, Jul. 2010.16 Z. Jian-hua and Z. Nan, ”Cloud Computing-based Data Storage and Disaster Recovery.” IEEE, 2011.17 Y. Ueno, N. Miyaho, S. Suzuki, and K. Ichihara, ”Performance Evaluation of a Disaster Recovery System
and Practical Network System Applications.” IEEE, Aug. 2010, pp. 195?200.18 B. I. Ismail, M. N. M. Mydin, and M. F. Khalid, ”Architecture of scalable backup service for private
cloud”,? in Open Systems (ICOS), 2013 IEEE Conference on. IEEE, 2013, pp. 174?179.19 B. P. Rimal, A. Jukan, D. Katsaros, and Y. Goeleven, ”Architectural Requirements for Cloud Computing
Systems: An Enterprise Cloud Approach”, Journal of Grid Computing, vol. 9, no. 1, pp. 3?26, Mar. 2011.20 ”Google Trends: Arcserve, Bacula, Netbackup popularity search worldwide”, 2016.21 K. Sibbald, ”Main Reference”, 2011. [Online]. Available: http://www.bacula.org/7.
4.x-manuals/en/main/Main Reference.html22 C. Preston, Backup and Recovery: Inexpensive Backup Solutions for Open Systems. ”O’Reilly Media,
Inc.”, 2007.
A Backup as a Service (BaaS) SoftwareSolution
Heitor Medrado de [email protected]
Departamento de Ciencia da ComputacaoInstituto de Ciencias Exatas
Universidade de Brasılia
11 de Setembro de 2017
29