1 |
Zálohování dokumentů v informačních systémech státní správy / Backup of documents in goverment information systemsStarosta, Martin January 2012 (has links)
The thesis is focused on backup documents in the public administration information systems. First chapters of thesis are devoted to general theories of backup files and databases. Next is described storage media what is used for backups, their advantages and disadvantages. Afterwards are described the most common backup strategies and rotation scheme. Thesis is devoted after that to analysis of a representative information system that is used to publish documents to the public. Based on information obtained from analysis is selected optimal backup strategy and this strategy is implemented and tested in designed application.
|
2 |
A Backup-as-a-Service (BaaS) software solutionFaria, Heitor Medrado de 01 July 2018 (has links)
Dissertação (mestrado)—Universidade de Brasília, Instituto de Ciências Exatas, Departamento de Ciência da Computação, 2018. / O backup é uma réplica de todos os dados que podem ser usados para restaurar seu formato
original. No entanto, a quantidade total de dados digitais criados em todo o mundo mais do que
dobra a cada dois anos e deve atingir 44 trilhões de gigabytes em 2020, trazendo novos desafios
constantes aos processos de backup. O backup corporativo é uma das tarefas mais antigas e
executadas por profissionais de infraestrutura e operações. Ainda assim, a maioria dos sistemas de
backup foi projetada e otimizada para ambientes desatualizados e casos de uso. Esse fato gera
frustração sobre os desafios atuais de backup e leva a uma maior disposição para modernizar e
considerar novas tecnologias. As soluções tradicionais de backup e arquivamento não são mais
capazes de atender às necessidades atuais dos usuários. O software de backup e recuperação
moderno ideal não deve apenas fornecer recursos para atender a um data center tradicional, mas
também permitir a integração e exploração da crescente nuvem, incluindo “backup client as a
service” e “backup storage como um serviço”'. O presente estudo tem como objetivo propor e
implantar uma solução de software Backup como Serviço. Para isso, são determinados os
parâmetros de backup/nuvem, os desafios de backup na nuvem, as arquiteturas pesquisadas e os
requisitos do sistema de BaaS. Em seguida, selecionamos um conjunto de recursos desejados do
BaaS a serem desenvolvidos, o que resulta na primeira interface Backup-as-a-Service baseada na
API REST, chamada de “bcloud”'. Realizamos uma consulta de usabilidade on-line com um número
significativo de usuários e realizamos uma análise de resultados. A avaliação média geral das
perguntas objetivas de zero a dez foi de 8,29%, indicando uma percepção muito satisfatória do
usuário do protótipo da interface de BaaS bcloud. / Backup is a replica of any data that can be used to restore its original form. However, the
total amount of digital data created worldwide more than doubles every two years and
is expected reach 44 trillions of gigabytes in 2020, bringing constant new challenges to
backup processes. Enterprise backup is one of the oldest and most performed tasks by infrastructure
and operations professionals. Still, most backup systems have been designed
and optimized for outdated environments and use cases. That fact, generates frustration
over currently backup challenges and leads to a greater willingness to modernize and to
consider new technologies. Traditional backup and archive solutions are no longer able
to meet users current needs. The ideal modern currently backup and recovery software
product should not only provide features to attend a traditional data center, but also
allow the integration and exploration of the growing Cloud, including “backup client as a
service” and “backup storage as a service”. The present study aims to propose and deploy
a Backup as a Service software solution. To achieve that, the cloud/backup parameters,
cloud backup challenges, researched architectures and BaaS system requirements are determined.
Then, we select a set of BaaS desired features to be developed, that results
in the first truly cloud REST API based Backup-as-a-Service interface, namely “bcloud”.
We conduct an on-line usability inquiry with a significant number of users and perform a
result analysis. The overall average objective zero to ten questions evaluation was 8.29%,
indicating a very satisfactory user perception of the bcloud BaaS interface prototype.
|
3 |
Automated Router and Switch BackupBjurdelius, Andreas, Bjurdelius, Pierre, Blomqvist, Alexander January 2014 (has links)
Today's companies are growing in a steady pace, with more and more network devices added to the network it is very important to keep track of and monitor the status of devices. Even though the wireless evolution has come, it all depends on the wired connections to supply a continuous connection to the rest of the world. This thesis explores, tests and informs about creating a functional system that automatically creates backups of configuration files from network devices and how to troubleshoot networking problems and maintain a network to keep it in good shape. Even though many companies have manual backups of router and switch configurations, the possibility to have this part automated should be desired by most companies. It can open up for the administrators in the company to have more time over to help the employees that are experiencing problems at the same time as the automated system eliminates the possible errors that a human can cause. Of course one can see it the other way, that it takes away manual labor for the employees, but it is just a small part of the job yet it is so very important that making this service automated is a good choice for a company. Integrity is proven by the means of backups and by the option to see the difference between the previous backups and the most recent. The three of us have worked as a group to do all tests and to write the documentation. After working with a couple of companies it is clear that well functional backup systems of network devices are not as common as it should be. Companies that do take backups of the network devices often do this manually. When seeing this it makes sense to use a reliable system that uses revision handling so it is easy to see the recent changes made to the devices. The results ended up in a working automated backup system for routers and switches. The automated system is running Debian and connects to all the routers and switches in the network to collect the configuration files with the help of rancid. The thesis also explains the functions of concepts such as disaster recovery and different maintenance models.
|
4 |
Enterprise Information Security - Backup Systems Planning and PracticeLin, Gary 05 July 2002 (has links)
It is well understood that competitiveness is the foundation of business. Efficient information acquisition, distribution and protection proves to not only improve business¡¦ competitiveness but also extend business value to both business partners and customers. Consequently, Information Security has been the rigorous and sustaining challenge to the business.
Thanks to the booming evolution of information technology, business nowadays has proliferated it widely for business operations. Sept 11 catastrophe in US has brought to business a significant yet unforeseen impact ¡V information security reassessment on both backup systems and disaster recovery planning. This document aims at exploring the status quo of domestic enterprises in this regard as well as possible obstacles of the implementation. Through field research and thorough understanding, we¡¦ve observed the differentiation among the industries we investigated. Meanwhile, we hoped to come out some solid recommendations and awareness to the business by applying generally acknowledged standard ¡V BS7799 rules and policies. With that in mind, enterprises then would be able to move themselves faster toward globalization.
For a long time, IT professionals tend to use tape or jukebox as primary data backup media. Today, we can only rely on those tools for alternatives. By current working field, I¡¦m taking the advantage by introducing high-level technologic system frameworks, practices and experiences from international key players in this field. Enterprises are also recommended to start the ¡§BIA ¡V Business Impact Analysis¡¨ to outline a proper DR and Contingency Plan for the sake of substantial and continual support to business interests and long-term benefits!
|
5 |
Fileserving und Backup im URZEhrig, Matthias 27 May 2002 (has links)
Gemeinsamer Workshop von Universitaetsrechenzentrum und Professur Rechnernetze und verteilte Systeme der Fakultaet fuer Informatik der TU Chemnitz.
Darstellung der aktuellen Situation des Fileserving und Backup im URZ der TU Chemnitz, Betrachtung alternativer Technologien wie NFS, GFS, SAN/NAS oder P2P und Diskussion möglicher Entwicklungen im URZ.
|
6 |
CABS - Chemnitzer AFS Backup SuiteMüller, Thomas 02 July 2003 (has links)
Workshop Mensch-Computer-Vernetzung
Der Vortrag stellt das im Rechenzentrum der TU Chemnitz eingesetzte Verfahren zur Datensicherung im Kontext von OpenAFS vor.
|
7 |
Effectiveness of Backup and Disaster Recovery in Cloud : A Comparative study on Tape and Cloud based Backup and Disaster RecoveryYarrapothu, Sindhura January 2015 (has links)
Context: Backup and Disaster Recovery, DR play a vital role in day-to-day IT operations. They define extensive aspects of business continuity plan in an enterprise. There is a continuous need to improve backup and recovery performance concerning attributes such as backup window size, high availability, security, etc. Definitive information is what enterprises strive for and rely upon to deviate from traditional methods towards advancing technologies, which are an intrinsic segment of business mundane actions. Objectives: In this study, we investigate Backup and DR plans on an enterprise level. They are compared in terms of performance metrics such as Recovery Time Objective, Recovery Point Objective, Time taken to backup, Time taken to recover and Total cost of ownership. Also, how CPU and memory utilization conduct differ in both tape-based, cloud-based Backup and DR. Methods: Literature study was the first step to formulate research questions by understanding present technologies in Backup and DR. This led us to conduct a survey for further understanding of challenges faced in industries gaining a more practical exposure. A case study was conducted in an enterprise to capture accurate values. An experiment had been deployed to compare performance of both scenarios and analyze which methodology elevates Backup and DR performance by overcoming challenges. Results: The results attained through this thesis encompass performance related metrics and also the load in terms of CPU and memory utilizations. Survey results were observed to gain better understanding of current technologies and challenges with Backup and DR in enterprises. The cloudbased backup has proved to be better in considered enterprise environment during experimentation in terms of RPO, RTO, CPU, memory utilizations and Total Cost of ownership. Conclusions: There have been numerous research works conducted on how backup and DR plans can be made better. But, they lack accurate information on how their performances vary, what all parameters can be improved by shifting towards advanced and contemporary methodologies withaddressing features such as scalability, flexibility and adaptability, which is provided in this study.
|
8 |
Um Algoritmo de Disponibilidade em Sistemas de Backup Distribuído Seguro Usando a Plataforma Peer-to-peerDuarte, Marcos Pinheiro 31 January 2010 (has links)
Made available in DSpace on 2014-06-12T15:56:38Z (GMT). No. of bitstreams: 2
arquivo2959_1.pdf: 5622692 bytes, checksum: 03f9776f9c2fee455957a3c73eddfd9b (MD5)
license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5)
Previous issue date: 2010 / Com o desenvolvimento tecnológico e a diminuição de preços dos computadores pessoais
as empresas passaram a investir na compra de equipamentos, buscando automatizar
processos, interligarem setores, criando assim uma atmosfera favorável a captura de dados
para análise estratégica e políticas de expansão e investimento [2]. Tal fato gerou uma
grande quantidade de recursos que podem ser considerados ociosos dentro das empresas.
Por outro lado, surgiu um novo problema, a informação pode se perder devido a erros de
operação do usuário, falhas de software e/ou hardware.
Neste contexto, a plataforma p2p mostra-se eficiente na implementação de um
sistema de backup, por fazer usufruto desta capacidade ociosa para o armazenamento de
dados. A dificuldade de implementação de um software P2P que faça backup esta no fato
que as mesmas podem ficar indisponíveis, fazendo com que o restore dos dados não possa
acontecer quando o usuário necessitar do mesmo, visto que partes do backup podem estar
espalhadas.
O principal objetivo deste trabalho é apresentar uma proposta de um algoritmo que
permita medir a confiabilidade da disponibilidade do restore de um backup efetuado em
uma rede P2P bem como a arquitetura de software, na qual, estão definidos os componentes
que medem as taxas de falhas das máquinas que compõe a rede e realizam a distribuição do
backup com base no calculo estatístico da disponibilidade do restore, fazendo com que
eventuais falhas não afetem o funcionamento ideal da restauração dos arquivos perdidos
|
9 |
Metodiskt backupsystem för lokalkontrollsutrustningar / Methodical backup system for local control equipmentOhlsson, Kristian January 2013 (has links)
Statkraft är helägt av Norska staten och är Sveriges fjärde största elproducent. Detta examensarbete syftar till att ta fram en metod för att lösa hur Statkraft Sverige AB ska lagra mjukvarubackuper av sina lokalkontrollssystem. För närvarande finns det ingen homogen lagringsmetod för backuper på företaget och problemet som ska lösas i examensarbetet är hur man kan lagra backuper från ett flertal heterogena system på en gemensam lagringsplattform. I och med att de allra flesta hjälpsystem för konfigurering av styrdatorer (PLC) bygger på Microsoft DOS/Windows så är det relativt enkelt att överföra backuper till en gemensam plattform. För äldre hjälpmedel kan man dock tänka sig att virtualisera hjälpmedlen på en nyare PC-dator med exempelvis VMware för att undvika problem som kan uppstå med äldre hårdvara. Därefter kan man arkivera backuperna i ZIP-format som man kan lagra på en server. Fördelen med att använda sig av ZIP för arkivering är att man får en inbyggd integritetskontroll av backuperna då ZIP har inbyggd cyclic redundancy check (CRC) som använder sig av kontrollsummor för att kontrollera så att filerna är korrekta. Dessutom så får man endast en fil i jämförelse med många filer per backup om man inte använder sig av arkivering. Backuperna ska sedan lagras på en server som ligger inom företagets intranät/kontorsnät som endast behörig personal har tillgång till. Uppladdningen av filerna kan gå till på flera olika sätt, större backupfiler från PC-system kan laddas upp direkt via nätverket och dokumentationen uppdateras manuellt. Mindre backupfiler skulle dock kunna laddas upp genom en webbsida på intranätet där dokumentationen uppdateras automatiskt i samband med uppladdning. Lagringsutrymmet för båda dessa lösningar är dock detsamma så det går även att ladda upp mindre backuper manuellt genom nätverket. Med dessa lösningar har berörda tekniker tillgång till backuperna vart de än befinner sig så länge internetuppkoppling finns genom ett virtuellt privat nätverk (VPN) till företagets intranät/kontorsnät. / Statkraft is the fourth largest electricity producer in Sweden and is fully owned by the Norwegian state. This thesis aims to develop a method for solving how Statkraft Sweden AB will store software backups of their local control systems. Currently there is no uniform method of storage for backups in the company and the problem to be solved in the thesis is how to store backups from multiple heterogeneous systems on a single storage platform. Based on the fact that the vast majority of help systems for configuring Programmable Logic Controllers (PLC) is based on Microsoft DOS / Windows, it is relatively simple to transfer the backups to a common platform. With older help systems it is also possible to virtualize these help systems on newer PC-based computers with for example VMware instances to avoid issues that can arise with older hardware. You can then archive the backups in ZIP-format that can be stored on a server, the advantage of using ZIP-archiving is to get a built-in integrity check of backups as ZIP has built in cyclic redundancy check (CRC) that uses checksums to check that the files are correct. Additionally, you get only one file in comparison to many files per backup if you do not archive in for example ZIP-format. The backups are then stored on a server within the company intranet / office network that is restricted to authorized personnel. The upload of the files can be done in several different ways; large backup files from PC-systems can be uploaded directly via the network, and the documentation is updated manually. Smaller and incremental backup files could however be uploaded through a web page on the Intranet, where documentation is automatically updated during upload. The storage space for both of these solutions is the same so that it is also possible to upload smaller backups manually through the network. With these solutions, the technicians can access the backups wherever they are as long as an Internet connection is available thru a virtual private network (VPN) Connection to the company’s intranet/office network.
|
10 |
Cluster-Based Routing with Backup Route in Wireless Ad Hoc NetworksHuang, Chi-hsuan 07 September 2006 (has links)
Effective routing is critical in mobile ad hoc networks (MANETs). In recent years, many hierarchical routing protocols have been proposed to build a backbone structure for supporting MANET routing, especially for large scalability. The clustering approach is seen as the first step in providing a flat network with a hierarchical architecture. The clusterheads become the backbone nodes (BNs), which use greater power to transmit packets, forming the backbone network. Backbone network routing can
reduce the number of data-packet forwarding hops throughout the entire network. However, previous protocols have focused on clustering schemes. Fault tolerance in a backbone structure has not been considered. In this paper, we propose a backup routing scheme that can repair broken
links locally without activating a route re-discovery procedure. The backup route is piggybacked in the data packet header to achieve the most durable route. The proposed method can improve the packet delivery ratio and reduce control overhead, compared to general hierarchical
routing protocols.
|
Page generated in 0.0453 seconds