DOCSLIB.ORG

Seleccione Un Host... Aceptar Backuppc

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Seleccione Un Host... Aceptar Backuppc BackupPC BackupPC Introduction Hosts Overview Backup basics Seleccione un host... Resources Road map You can help Installing BackupPC Requirements What type of storage space do I need? Aceptar How much disk space do I need? Step 1: Getting BackupPC Servidor Step 2: Installing the distribution Step 3: Setting up config.pl Estado Step 4: Setting up the hosts file Resumen PC Step 5: Client Setup Edit Config Step 6: Running BackupPC Edit Hosts Step 7: Talking to BackupPC Opciones de Step 8: Checking email delivery administración Step 9: CGI interface Archivo Registro How BackupPC Finds Hosts Registros antiguos Other installation topics Resumen correo Fixing installation problems Colas actuales Restore functions Documentación CGI restore options Wiki Command-line restore options SourceForge Archive functions Configuring an Archive Host Starting an Archive Starting an Archive from the command line Other CGI Functions Configuration and Host Editor RSS BackupPC Design Some design issues BackupPC operation Storage layout Compressed file format Rsync checksum caching File name mangling Special files Attribute file format Optimizations Limitations Security issues Configuration File Modifying the main configuration file Configuration Parameters General server configuration What to backup and when to do it How to backup a client 1 de 75 Email reminders, status and messages CGI user interface configuration settings Version Numbers Author Copyright Credits License BackupPC Introduction This documentation describes BackupPC version 3.1.0, released on 25 Nov 2007. Overview BackupPC is a high-performance, enterprise-grade system for backing up Unix, Linux, WinXX, and MacOSX PCs, desktops and laptops to a server's disk. BackupPC is highly configurable and easy to install and maintain. Given the ever decreasing cost of disks and raid systems, it is now practical and cost effective to backup a large number of machines onto a server's local disk or network storage. For some sites this might be the complete backup solution. For other sites additional permanent archives could be created by periodically backing up the server to tape. Features include: A clever pooling scheme minimizes disk storage and disk I/O. Identical files across multiple backups of the same or different PC are stored only once (using hard links), resulting in substantial savings in disk storage and disk writes. Optional compression provides additional reductions in storage (around 40%). The CPU impact of compression is low since only new files (those not already in the pool) need to be compressed. A powerful http/cgi user interface allows administrators to view the current status, edit configuration, add/delete hosts, view log files, and allows users to initiate and cancel backups and browse and restore files from backups. The http/cgi user interface has internationalization (i18n) support, currently providing English, French, German, Spanish, Italian, Dutch and Portuguese-Brazilian. No client-side software is needed. On WinXX the standard smb protocol is used to extract backup data. On linux, unix or MacOSX clients, rsync or tar (over ssh/rsh/nfs) is used to extract backup data. Alternatively, rsync can also be used on WinXX (using cygwin), and Samba could be installed on the linux or unix client to provide smb shares). Flexible restore options. Single files can be downloaded from any backup directly from the CGI interface. Zip or Tar archives for selected files or directories from any backup can also be downloaded from the CGI interface. Finally, direct restore to the client machine (using smb or tar) for selected files or directories is also supported from the CGI interface. BackupPC supports mobile environments where laptops are only intermittently 2 de 75 connected to the network and have dynamic IP addresses (DHCP). Configuration settings allow machines connected via slower WAN connections (eg: dial up, DSL, cable) to not be backed up, even if they use the same fixed or dynamic IP address as when they are connected directly to the LAN. Flexible configuration parameters allow multiple backups to be performed in parallel, specification of which shares to backup, which directories to backup or not backup, various schedules for full and incremental backups, schedules for email reminders to users and so on. Configuration parameters can be set system-wide or also on a per-PC basis. Users are sent periodic email reminders if their PC has not recently been backed up. Email content, timing and policies are configurable. BackupPC is Open Source software hosted by SourceForge. Backup basics Full Backup A full backup is a complete backup of a share. BackupPC can be configured to do a full backup at a regular interval (typically weekly). BackupPC can be configured to keep a certain number of full backups. Exponential expiry is also supported, allowing full backups with various vintages to be kept (for example, a settable number of most recent weekly fulls, plus a settable number of older fulls that are 2, 4, 8, or 16 weeks apart). Incremental Backup An incremental backup is a backup of files that have changed since the last successful full or incremental backup. Starting in BackupPC 3.0 multi-level incrementals are supported. A full backup has level 0. A new incremental of level N will backup all files that have changed since the most recent backup of a lower level. $Conf{IncrLevels} is used to specify the level of each successive incremental. The default value is all level 1, which makes the behavior the same as earlier versions of BackupPC: each incremental will back up all the files that changed since the last full (level 0). For SMB and tar, BackupPC uses the modification time (mtime) to determine which files have changed since the last lower-level backup. That means SMB and tar incrementals are not able to detect deleted files, renamed files or new files whose modification time is prior to the last lower-level backup. Rsync is more clever: any files whose attributes have changed (ie: uid, gid, mtime, modes, size) since the last full are backed up. Deleted, new files and renamed files are detected by Rsync incrementals. BackupPC can also be configured to keep a certain number of incremental backups, and to keep a smaller number of very old incremental backups. If multi-level incrementals are specified then it is likely that more incrementals will need to be kept since lower-level incrementals (and the full backup) are needed to reconstruct a higher-level incremental. BackupPC ``fills-in'' incremental backups when browsing or restoring, based on the levels of each backup, giving every backup a ``full'' appearance. This makes browsing and restoring backups much easier: you can restore from any one backup 3 de 75 independent of whether it was an incremental or full. Partial Backup When a full backup fails or is canceled, and some files have already been backed up, BackupPC keeps a partial backup containing just the files that were backed up successfully. The partial backup is removed when the next successful backup completes, or if another full backup fails resulting in a newer partial backup. A failed full backup that has not backed up any files, or any failed incremental backup, is removed; no partial backup is saved in these cases. The partial backup may be browsed or used to restore files just like a successful full or incremental backup. With the rsync transfer method the partial backup is used to resume the next full backup, avoiding the need to retransfer the file data already in the partial backup. Identical Files BackupPC pools identical files using hardlinks. By ``identical files'' we mean files with identical contents, not necessary the same permissions, ownership or modification time. Two files might have different permissions, ownership, or modification time but will still be pooled whenever the contents are identical. This is possible since BackupPC stores the file meta-data (permissions, ownership, and modification time) separately from the file contents. Backup Policy Based on your site's requirements you need to decide what your backup policy is. BackupPC is not designed to provide exact re-imaging of failed disks. See Limitations for more information. However, the addition of tar transport for linux/unix clients, plus full support for special file types and unix attributes in v1.4.0 likely means an exact image of a linux/unix file system can be made. BackupPC saves backups onto disk. Because of pooling you can relatively economically keep several weeks of old backups. At some sites the disk-based backup will be adequate, without a secondary tape backup. This system is robust to any single failure: if a client disk fails or loses files, the BackupPC server can be used to restore files. If the server disk fails, BackupPC can be restarted on a fresh file system, and create new backups from the clients. The chance of the server disk failing can be made very small by spending more money on increasingly better RAID systems. However, there is still the risk of catastrophic events like fires or earthquakes that can destroy both the BackupPC server and the clients it is backing up if they are physically nearby. Some sites might choose to do periodic backups to tape or cd/dvd. This backup can be done perhaps weekly using the archive function of BackupPC. Other users have reported success with removable disks to rotate the BackupPC data drives, or using rsync to mirror the BackupPC data pool offsite. Resources BackupPC home page 4 de 75 The BackupPC Open Source project is hosted on SourceForge. The home page can be found at: http://backuppc.sourceforge.net This page has links to the current documentation, the SourceForge project page and general information. SourceForge project The SourceForge project page is at: http://sourceforge.net/projects/backuppc This page has links to the current releases of BackupPC.
Load more

Recommended publications
  • Resurrect Your Old PC
    Resurrect your old PCs Resurrect your old PC Nostalgic for your old beige boxes? Don’t let them gather dust! Proprietary OSes force users to upgrade hardware much sooner than necessary: Neil Bothwick highlights some great ways to make your pensioned-off PCs earn their keep. ardware performance is constantly improving, and it is only natural to want the best, so we upgrade our H system from time to time and leave the old ones behind, considering them obsolete. But you don’t usually need the latest and greatest, it was only a few years ago that people were running perfectly usable systems on 500MHz CPUs and drooling over the prospect that a 1GHz CPU might actually be available quite soon. I can imagine someone writing a similar article, ten years from now, about what to do with that slow, old 4GHz eight-core system that is now gathering dust. That’s what we aim to do here, show you how you can put that old hardware to good use instead of consigning it to the scrapheap. So what are we talking about when we say older computers? The sort of spec that was popular around the turn of the century. OK, while that may be true, it does make it seem like we are talking about really old hardware. A typical entry-level machine from six or seven years ago would have had something like an 800MHz processor, Pentium 3 or similar, 128MB of RAM and a 20- 30GB hard disk. The test rig used for testing most of the software we will discuss is actually slightly lower spec, it has a 700MHz Celeron processor, because that’s what I found in the pile of computer gear I never throw away in my loft, right next to my faithful old – but non-functioning – Amiga 4000.
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • Referência Debian I
    Referência Debian i Referência Debian Osamu Aoki Referência Debian ii Copyright © 2013-2021 Osamu Aoki Esta Referência Debian (versão 2.85) (2021-09-17 09:11:56 UTC) pretende fornecer uma visão geral do sistema Debian como um guia do utilizador pós-instalação. Cobre muitos aspetos da administração do sistema através de exemplos shell-command para não programadores. Referência Debian iii COLLABORATORS TITLE : Referência Debian ACTION NAME DATE SIGNATURE WRITTEN BY Osamu Aoki 17 de setembro de 2021 REVISION HISTORY NUMBER DATE DESCRIPTION NAME Referência Debian iv Conteúdo 1 Manuais de GNU/Linux 1 1.1 Básico da consola ................................................... 1 1.1.1 A linha de comandos da shell ........................................ 1 1.1.2 The shell prompt under GUI ......................................... 2 1.1.3 A conta root .................................................. 2 1.1.4 A linha de comandos shell do root ...................................... 3 1.1.5 GUI de ferramentas de administração do sistema .............................. 3 1.1.6 Consolas virtuais ............................................... 3 1.1.7 Como abandonar a linha de comandos .................................... 3 1.1.8 Como desligar o sistema ........................................... 4 1.1.9 Recuperar uma consola sã .......................................... 4 1.1.10 Sugestões de pacotes adicionais para o novato ................................ 4 1.1.11 Uma conta de utilizador extra ........................................ 5 1.1.12 Configuração
    [Show full text]
  • Ubuntu® 1.4Inux Bible
    Ubuntu® 1.4inux Bible William von Hagen 111c10,ITENNIAL. 18072 @WILEY 2007 •ICIOATENNIAl. Wiley Publishing, Inc. Acknowledgments xxi Introduction xxiii Part 1: Getting Started with Ubuntu Linux Chapter 1: The Ubuntu Linux Project 3 Background 4 Why Use Linux 4 What Is a Linux Distribution? 5 Introducing Ubuntu Linux 6 The Ubuntu Manifesto 7 Ubuntu Linux Release Schedule 8 Ubuntu Update and Maintenance Commitments 9 Ubuntu and the Debian Project 9 Why Choose Ubuntu? 10 Installation Requirements 11 Supported System Types 12 Hardware Requirements 12 Time Requirements 12 Ubuntu CDs 13 Support for Ubuntu Linux 14 Community Support and Information 14 Documentation 17 Commercial Support for Ubuntu Linux 18 Getting More Information About Ubuntu 19 Summary 20 Chapter 2: Installing Ubuntu 21 Getting a 64-bit or PPC Desktop CD 22 Booting the Desktop CD 22 Installing Ubuntu Linux from the Desktop CD 24 Booting Ubuntu Linux 33 Booting Ubuntu Linux an Dual-Boot Systems 33 The First Time You Boot Ubuntu Linux 34 Test-Driving Ubuntu Linux 34 Expioring the Desktop CD's Examples Folder 34 Accessing Your Hard Drive from the Desktop CD 36 Using Desktop CD Persistence 41 Copying Files to Other Machines Over a Network 43 Installing Windows Programs from the Desktop CD 43 Summary 45 ix Contents Chapter 3: Installing Ubuntu on Special-Purpose Systems 47 Overview of Dual-Boot Systems 48 Your Computer's Boot Process 48 Configuring a System for Dual-Booting 49 Repartitioning an Existing Disk 49 Getting a Different Install CD 58 Booting from a Server or Altemate
    [Show full text]
  • Unidade Curricular – Administração De Redes Prof. Eduardo Maroñas
    SERVIÇO NACIONAL DE APRENDIZAGEM COMERCIAL FACULDADE DE TECNOLOGIA SENAC PELOTAS Unidade Curricular – Administração de Redes Prof. Eduardo Maroñas Monks Roteiro de Laboratório Backup – Parte II (Gerenciadores de Backup) Objetivo: Utilizar e descrever as características de funcionamento de backups em rede. Ferramentas: Wireshark, Vmware Player, Putty, OpenSSH, WinSCP, Apache Web Server, CentOS, Windows XP, FreeNAS, BackupPC, Clonezilla, MySQL, PostgreSQL Introdução: Neste roteiro de laboratório, serão utilizadas diversas ferramentas e sistemas operacionais para analisar o funcionamento dos sistemas de backup. O backup é essencial na administração de rede e deve ser aplicado onde dados importantes sejam utilizados. Atualmente, com o grande volume de dados realizar o backup de forma correta é cada vez mais complexo. Para isto, existem ferramentas que auxiliam nesta tarefa, tornando a vida do administrador de redes mais fácil. Tarefas: 1) Na máquina virtual CentOS, instalar o gerenciador de backups BackupPC. Para isto, devem ser seguidos os seguintes procedimentos: 1. Criar o diretório /backups onde será o repositório dos dados copiados. 2. Instalar os pacotes 1. Perl-setuid: yum install perl-suidperl 2. Archive-Zip: yum install perl-Archive-Zip.noarch 3. File-RsyncP: yum install perl-File-RsyncP Obs.: utilizar o proxy do Mussum (export http_proxy=”http://192.168.200.3:3128” 3. Fazer o download do código-fonte do BackupPC, disponível em http://192.168.200.3/emmonks/admredes4/BACKUP/BackupPC-3.3.0.tar.gz, para o diretório /usr/src 4. Criar o usuário backuppc e dar permissões para este usuário no diretório /backups. 5. Criar o diretório /var/www/html/imagens para ser o repositório de figuras do BackupPC.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • 6.4.0-0 Release of SIMP, Which Is Compatible with Centos and Red Hat Enterprise Linux (RHEL)
    SIMP Documentation THE SIMP TEAM Sep 16, 2020 Contents 1 Level of Knowledge 3 1.1 Quick Start................................................4 1.2 Changelogs................................................4 1.3 SIMP Getting Started Guide....................................... 64 1.4 SIMP User Guide............................................ 81 1.5 Contributing to SIMP.......................................... 228 1.6 SIMP Security Concepts......................................... 263 1.7 SIMP Security Control Mapping..................................... 282 1.8 Vulnerability Supplement........................................ 642 1.9 Help................................................... 644 1.10 License.................................................. 652 1.11 Contact.................................................. 652 1.12 Glossary of Terms............................................ 652 Index 669 i ii SIMP Documentation This is the documentation for the 6.4.0-0 release of SIMP, which is compatible with CentOS and Red Hat Enterprise Linux (RHEL). This guide will walk a user through the process of installing and managing a SIMP system. It also provides a mapping of security features to security requirements, which can be used to document a system’s security conformance. Warning: Be EXTREMELY CAREFUL when performing copy/paste operations from this document! Different web browsers and operating systems may substitute incompatible quotes and/or line endings in your files. The System Integrity Management Platform (SIMP) is an Open Source
    [Show full text]
  • Documentations Techniques
    PPE Rapport Page 1 20/12/2017 Documentations techniques Aurélie DA SILVA, NAPOLEONE Daniel, GAUDILLAT Dylan LYCEE MATHIAS PPE Rapport Page 2 Table des matières Installation d’Active Directory et DNS ...................................................................................................................................... 4 I] Serveur DNS : ................................................................................................................................................................. 10 II] Synchronisation de Glpi avec un AD : ............................................................................................................................ 13 Serveur accès à distance : ...................................................................................................................................................... 17 Le serveur de messagerie ...................................................................................................................................................... 18 I. Installation de hMailServer ............................................................................................................................................ 18 II. Tests de messagerie ...................................................................................................................................................... 19 Configuration d’un switch : ...................................................................................................................................................
    [Show full text]
  • Disaster Recovery
    Topics 1. Backup Decisions 2. Types of Backups CIT 470: Advanced Network and 3. Backup Hardware System Administration 4. Backup Software Backups 5. Snapshots and CDP 6. Cron 7. Backup Security CIT 470: Advanced Network and System Administration Slide #1 CIT 470: Advanced Network and System Administration Slide #2 Backup Decisions Why Backups? Why? Why are you backing up data? What would happen if you lost data and 1. Accidental deletions. didn’t back up? What types of data do you have? What? 2. Hardware failures. What to back up—entire system, or specific filesystems? What OS to backup? What other things to backup—MBR, LVM? 3. Data corruption. When? 4. Security incidents. When is the best time to backup? How often? Where? 5. Plan for the worst. Where will backup occur? Where to store backup volumes? Who? 1. System catches fire. Who is going to provide backup system? Who will do backups? 2. Fire spreads to replicated systems. How? How are you going to do backups? Tape, mirrors, off-site, etc. 3. Sprinklers destroy backup system in data ctr. CIT 470: Advanced Network and System Administration Slide #3 CIT 470: Advanced Network and System Administration Slide #4 What to Backup? Filesystem / Data Types Backups for your backups Operating System – Be able to restore your backup server (software + backup volume db) in case it’s down. Standard OS image on server. Which peripherals? Software – How many drives per server? Software + config files specific to server. – What is the capacity of each drive? How were they partitioned? Data – Drive partitions must be same as before disaster for Data files specific to server.
    [Show full text]
  • Incremental Backup Copies All of the Files That Have Changed Since the Last Backup Was Made
    BackupPC Network Startup Resource Center www.nsrc.org These materials are licensed under the Creative Commons Attribution-NonCommercial 4.0 International license (http://creativecommons.org/licenses/by-nc/4.0/) Data disasters (1) ● System or hard disk crash ● Human error ● Data corrupted or innacessible ● Unintended deletion ● Natural disaster Data disasters (2) ● How much data loss, if any, is acceptable? ● How long can your business function without the data? ● How long can your production system be down during a restore? ● How much transaction time can be lost? ● How much budget is available for a recovery plan? When a disaster strikes, you need a way to recover the data. The recovery process requires procedures and processes in place ahead of time that allow for data recovery when needed. Backup/Restore RESTORE Data backup ● Differential backup copies those files that have been changed since the last full backup took place. The key advantage of differential backups comes when data needs to be restored. Because a full backup was taken and the differentials copied everything that subsequently changed, only the full backup and the latest differential need to be restored. ● Incremental backup copies all of the files that have changed since the last backup was made. They do this whether the last backup was a full one or an incremental copy. ● Full backup copies of all data. The primary advantage to performing a full backup during every operation is that a complete copy of all data is available with a single set of media. Data recovery (1) • Type: • Knowing the type or usage of data can help you determine how quickly it needs to be recovered.
    [Show full text]
  • April 2007 Volume 32 Number 2
    APRIL 2007 VOLUME 32 NUMBER 2 THE USENIX MAGAZINE OPINION Musings RIK FARROW SYSADMIN Autonomic Computing: Freedom or Threat? GLENN FINK AND DEB FRINCKE The Secret Lives of Computers Exposed CHAD VERBOWSKI Lessions Learned from Living with LDAP BRENDAN QUINN Introducing System Engineering to the System Admin JOHN LLOYD Promises, Promises: An Interview with Mark Burgess RIK FARROW Spam and Blogs. Part 1: Spam: A Balancing Act DANIEL L. APPELMAN All Quiet on the Western Front: A Discussion on the Necessity of Good Reporting THOMAS SLUYTER COLUMNS Practical Perl Tools: These Inodes Were Made for Walkin’ DAVID BLANK-EDELMAN VoIP in an Internet Service Provider Network ROBERT HASKINS Asterisk Appliance HEISON CHAK /dev/random ROBERT G. FERRELL BOOK REVIEWS Book Reviews ELIZABETH ZWICKY ET AL. STANDARDS Why Standardize? NICHOLAS M. STOUGHTON USENIX NOTES SAGE Update JANE-ELLEN LONG AND ALVA COUCH CONFERENCES LISA '06: 20th Large Installation System Administration Conference The Advanced Computing Systems Association Upcoming Events 11 TH WORKSHOP ON HOT TOPICS IN OPERATING 3RD WORKSHOP ON STEPS TO REDUCING SYSTEMS (H OT OS XI) UNWANTED TRAFFIC ON THE INTERNET Sponsored by USENIX in cooperation with the IEEE Technical Co-located with the 2007 USENIX Annual Technical Conference Committee on Operating Systems (TCOS) JUNE 18, 2007, SANTA CLARA , CA , USA MAY 7–9, 2007, SAN DIEGO , CA, USA http://www.usenix.org/sruti07 http://www.usenix.org/hotos07 Paper submissions due: April 17, 2007 5TH ACM/USENIX I NTERNATIONAL CONFERENCE INAUGURAL INTERNATIONAL
    [Show full text]
  • Sistema De Backup Distribuído Para Ipbrick
    Faculdade de Engenharia da Universidade do Porto Sistema de Backup Distribuído para IPBrick Bruno Miguel Fernandes Pereira Licenciado em Engenharia Electrotécnica e de Computadores pela Faculdade de Engenharia da Universidade do Porto Relatório de Projecto realizado no âmbito do Mestrado Integrado em Engenharia Electrotécnica e de Computadores Major Telecomunicações Orientador: Prof.Dr. Jorge Manuel Gomes Barbosa Co-orientador: Prof.Dr. Raul Oliveira Porto, Julho 2008 c Bruno Pereira, 2008 Resumo Este projecto destina-se à apresentação de um sistema de backup dis- tribuido e que possui uma configuração e gestão fáceis na óptica do uti- lizador. Deste modo, foi analisado o sistema operativo de suporte IPBrick e a ferramenta de backup que utiliza: o Arkeia. Posteriormente, foram abor- dados breves conceitos sobre backups e foram feitas referências a alguns dos mais populares softwares de backup open source existentes no mer- cado. Tendo existido ainda, uma análise sobre o que é feito pelas outras empresas e o enquadramento do sistema de backup desenvolvido nesses parâmetros. Também foram estudadas as funcionalidades implementadas no desen- volvimento do sistema de backup distribuído, salientando-se a arquitectura do sistema, as bases de dados e a relação do sistema com outras já exis- tentes na IPBrick, minimizando assim as informações que o administrador do backup precisa de fornecer ao sistema. Por último, foi demonstrada a usabilidade da interface com o utilizador, reforçando-se alguns dos aspectos que fazem com que este sistema seja intuitivo e de fácil utilização, dispensado grandes conhecimentos sobre o mesmo. Palavras-chave: Backup, Restore, Disaster Recovery, Saving Data, Online Backup iii Abstract The aim of this project is to present a distribuited backup system witch provides an easy configuration and management in user’s view.
    [Show full text]