Breaking Through the Backup Barrier

Total Page:16

File Type:pdf, Size:1020Kb

Breaking Through the Backup Barrier JPJ8;D@E BackupPC ZXcXdlj#=fkfc`X 9i\Xb`e^k_ifl^_k_\YXZblgYXii`\i JDFFK?FG<I8KFI BackupPC handles backups over the network for a ranges of platforms. Find out more about this user-friendly, configurable, high-performance open source backup system. BY DAVID NALLEY etwork backup platforms are ated wiki, and the project is still led by the files to see whether they are identi- often unwieldy, partly because the original primary author, Craig Bar- cal. If it determines that the files are the Eof the complexities of schedul- ratt. Although the tool has been around same, it moves a single copy of the file ing logic and media management. User since 2001 and is relatively mature, the to the “pool” and creates hard links to friendliness can be hard to find in an en- latest version – BackupPC 3.1.0 – seems each instance of the file in the backup terprise-ready backup system. The Back- to be reaching new users. set. The results are surprising: In the upPC project [1] fills the backup niche first test I ran on eight machines (per- elegantly, handling backups over the 9\e\]`kj forming uncompressed backups and network for a plethora of platforms and One of the defining features of Back- retention of two full backups and six transports. upPC is data de-duplication. In a tradi- incrementals), my total data store was BackupPC follows the Unix tradition tional backup system, having multiple ~1TB, but BackupPC’s data de-dupli- of small programs that perform a single backups of files that haven’t changed cation brought the actual size on disk task very well. Like other classic Unix in more than one full backup interval to ~675GB. utilities, BackupPC leverages the power requires storing the same information BackupPC also offers several nice of other applications instead of trying to more than once. The problem is only scheduling features, such as the ability reinvent the wheel. BackupPC supports compounded when you back up multi- to prioritize backups. By default, several protocols for both Windows and ple computers – particularly if they are BackupPC wakes hourly and identifies Unix-like clients – from rsync and SMB/ end-user machines that might be on the any computer that hasn't completed a CIFS, to tar and rsync tunneling over same circulation list for memos, spread- backup within the specified interval. SSH. The focus is on efficient scheduling sheet, and other common documents. Also, it checks to see which machines and a user-friendly restore process. BackupPC addresses this problem with are on the network, and after combining BackupPC has an active user commu- a two-tier check. The first check locates these two lists, BackupPC prioritizes nity with mailing lists and a user-gener- files with the same names and hashes the list of available hosts on the basis of 72 ISSUE 93 AUGUST 2008 BackupPC JPJ8;D@E time since the last backup. Other factors RAID to combine multiple disks, but you So that BackupPC will start automati- can also influence this priority list. For can only use a single filesystem to hold cally, you must add init scripts to your instance, a machine that is on the net- the store. system. In the init.d subdirectory, you work 24 hours a day is generally pre- BackupPC tests to ensure that it can will find init scripts for a variety of dis- empted by a machine with a more spo- create these hard links at each startup. tributions. radic network presence record. You’ll need to know the mount point of Copy this to /etc/init.d, set it to start My favorite feature of BackupPC is this filesystem during installation. on boot, and then start the daemon: that end users can initiate and perform The next two steps are really one-lin- their own restores without the interac- ers in the console and consist of creating $ su -c tion of the backup operator or system a user for BackupPC to run as and in- "cp linux-backuppc administrator. If you have been involved stalling the software prerequisites. Of /etc/init.d/backuppc" in backups on any scale, you know that course, this assumes that you have httpd $ su -c "chkconfig handling restores of a lost or mangled already installed and configured for your --add backuppc" file is time consuming. If the user needs server: $ su -c "chkconfig to find a specific version of the file, the --level 345 backuppc on" restore process can grow into a multi- # adduser backuppc $ su -c "chkconfig hour effort. BackupPC offers a friendly # yum install --list backuppc" web interface that provides a directory perl-Compress-Zlib $ su -c "service and file tree for each backup. Users can perl-Archive-Zip backuppc start" select a single file or multiple files in the perl-XML-RSS tree, and BackupPC will restore these perl-File-RsyncP :fe]`^liXk`fe files without the need for a system ad- Although the installation process han- ministrator. BackupPC even checks for After the prerequisites are out of the dles the basic configuration elements, whether the user has the necessary ac- way, you can grab the source [1] and other options are available via the web cess permissions to view the file before uncompress it: interface or command line. beginning the restore. BackupPC configuration is contained Users also have some control over $ tar -zxvf in two files under /etc/BackupPC: hosts when to start a backup (full or incre- BackupPC-3.1.0.tar.gz details the identity of the hosts to be mental) or whether to remove their ma- $ cd BackupPC-3.1.0 backed up, and config.pl controls the chines from the backup list for a number $ su -c "perl ./configure.pl" server configuration. of hours. The hosts file lists the hostnames to be This launches the installer, which per- backed up and the authorized users for @ejkXccXk`fe forms the basic configuration and instal- that machine: Installation of BackupPC is relatively lation of BackupPC. The default answers painless because it’s included in most are fine, with a few exceptions. The data host dhcp user moreUsers mainstream distribution package reposi- directory should be the mount point of # <--- do not edit this line tories. However, sometimes it doesn’t the filesystem for the backup pool (e.g., nalleyt61 0 david include the latest available code or has /data/BackupPC or a subdirectory # <--- example static some special installation requirements, therein). Also, you might need to enter IP host entry so I’ll cover installation from source. If the correct path for the CGI bin directory host2 1 bill jeff,fred you used your distribution’s package for (e.g., /var/www/cgi-bin/). # <--- example DHCP host entry BackupPC, skip ahead to the Configuration section. Before working on the installation, you must consider disk space and how it is set up. Because BackupPC handles de-du- plication by creating hard links from the file loca- tion in the directory struc- ture of the backups to the pool where duplicated files are actually stored, the backup store must be on a single filesystem. This doesn’t mean that you can’t use LVM, soft- ware RAID, or hardware =`^li\(1@ek_\:fe]`^liXk`fe<[`kfi#pflZXeX[aljkk_\j\im\iZfe]`^liXk`fej\kk`e^j% AUGUST 2008 ISSUE 93 73 JPJ8;D@E BackupPC backuppc ฀ ALL=NOPASSWD: /usr/ ฀ bin/rsync then modify the com- mand arguments so that it uses sudo to call rsync: $Conf{RsyncClient ฀ Cmd} = '$sshPath -l backup ฀ $host nice -n 19 sudo /path/to/ ฀ rsyncSend $argList+'; =`^li\)1:_\Zbk_\jkXkljf]Zlii\ekcpilee`e^YXZblgjXe[]X`cli\j% Although you shouldn’t limit yourself to just these When I cover authenticating to the will only look at the minimum options configuration options, setting these web interface, I’ll explain authorized that must be configured to start backups items at a minimum will take care of users more, but the vital points are the on either Windows or Linux. Also, it’s backing up Windows machines or Linux hostname and the DHCP setting. If important to remember that you can machines with Samba shares exposed. your machine gets its address via DHCP, make modifications on a per-machine Although you can configure a number you still want to use 0 for the DHCP set- basis, too. of other things, such as file/ directory ex- ting, which tells BackupPC to use DNS One thing to set up is the admin user clusions and compression levels, the last to find the host. Setting this value to 1 and how backups will be transferred in required item is configuring the web in- tells BackupPC only to use nmblookup your environment (see Listing 1). How- terface. The installation automatically to query for the host address via Net- ever, I don’t advocate the use of root as installed the web interface, but you need BIOS. the backup user; instead, I suggest that to set up authentication for it, and you The default config.pl is configured to you use a low-privileged account and set need a way to authenticate the users in wake up every hour to look for hosts to up sudo so that rsync is accessible. As the hosts file and the admin users. Be- back up, do a full backup approximately the backuppc user, you’ll also need to cause you are using Apache to provide every 7 days, and do an incremental log in to the client machine via SSH so authentication, you have a variety of backup every day (Figure 1). that it becomes a known host.
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]
  • 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.
    [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]