ARKEIA SERVER BACKUP USER GUIDE

(1)

A

RKEIA

S

ERVER

B

ACKUP

U

SER

G

UIDE

(2)

Copyright

MySQL® is a registered trademark of MySQL AB in the United States, the Euro-pean Union and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries.

Arkeia 1808 Aston Avenue Suite 220 Carlsbad, CA 92008 USA Tel : +1 (760) 431 - 1319 Fax : +1 (760) 602 - 8599 Arkeia Europe 31, rue Delizy 93692 Pantin Cedex France Tel : +33 (0)1 48 10 89 89 Fax : +33 (0)1 48 10 89 90 US, Canada, Mexico, South America,

Australia, Pacific Rim, China

Europe, Middle East Africa, and central Asia

(3)

ARKEIA SOFTWARE LICENSE AGREEMENT

In order to preserve and protect its rights within the framework of currently applicable legislation, Arkeia Corporation and Arkeia SA, hereinafter referred to as ARKEIA, does not sell rights to this SOFTWARE, but grants the right to use this SOFTWARE, within the terms of this license agreement, hereinafter referred to as LICENSE AGREEMENT, and expressly retains ownership rights to all ARKEIA SOFTWARE. If you do not agree with all the terms and conditions of this LICENSE AGREEMENT you can obtain a refund by return-ing the SOFTWARE, all its manuals, its documentation and the original sealed license envelope, in salable condition, to the place you obtained them.

1. GRANT OF LICENSE. In return for payment of LICENSE fees included in the cost of the SOFTWARE and your commitment to comply with the terms and conditions of this LICENSE AGREEMENT as well as the limited warranty attached to, ARKEIA, the licenser, grants to you, the LICENSEE, the exclusive and non-transferable right to use the SOFTWARE on a single computer known as the backup server, here in after referred to as the SERVER, and its associated client computers, here in after referred to as CLIENTS, provided that the terms and conditions of the license are complied with.

If the SERVER or CLIENT on which the SOFTWARE is operated constitutes a sys-tem with several users, the LICENSE AGREEMENT shall apply to all such users without incurring additional costs.

ARKEIA reserves all rights that are not expressly granted to the LICENSEE. 2. COPYRIGHT. The beneficiary of the LICENSE is the owner of the magnetic

media, or any other type of media on which the SOFTWARE is initially, or subse-quently, recorded or stored. However, this License is granted on the express condi-tion that ARKEIA retains copyrights to the SOFTWARE recorded on the original media as well as copyrights to all copies made, irrespective of the format and the media of said original media and said copies

This LICENSE does not constitute a sale of the original SOFTWARE or of any copy thereof.

3. REPRODUCTION RESTRICTIONS. This SOFTWARE and the accompanying written materials are protected by copyright. Unauthorized reproduction of the SOFTWARE, including its modification, integration or inclusion in another soft-ware, or of the accompanying written materials is strictly forbidden. The LIC-ENSEE is liable to legal sanctions for any copyright infringement caused or prompted by any breach, on the part of the LICENSEE, of the terms and conditions of this LICENSE AGREEMENT.

Subject to the above-mentioned restrictions, the LICENSEE is authorized to make one (1) backup copy of the SOFTWARE if said SOFTWARE is not copy-protected. - Notice of copyright must appear on the backup copy.

4. RESTRICTIONS OF USE. The LICENSEE is authorized to physically transfer the SOFTWARE from one SERVER to another SERVER on condition that said SOFT-WARE is completely and totally removed from the original SERVER. Electronic transfers of the SOFTWARE from one SERVER to another within a distribution network for the purpose of copying the SOFTWARE or the accompanying written materials are strictly forbidden. The LICENSEE shall not modify, adapt, translate,

(4)

reverse engineer, decompile, disassemble or create written materials based on the SOFTWARE, and shall not modify, adapt, translate or write literature based on the written materials without the prior express written consent from ARKEIA.

5. TRANSFER RESTRICTIONS. No person whomsoever shall be authorized to oper-ate this SOFTWARE without the prior express written consent from ARKEIA. Any beneficiary of a transfer thus authorized shall be bound by the terms and conditions of this LICENSE AGREEMENT and the limited warranty attached there. Under no circumstances shall the LICENSEE be entitled to transfer, convey, lease or sell the SOFTWARE, nor shall it be entitled to dispose thereof, in any manner whether tem-porary or permanent, except where otherwise expressly provided for herein. 6. CANCELLATION. This LICENSE AGREEMENT shall remain valid until its

can-cellation and shall be canceled, as a right without prior notice by ARKEIA should the LICENSEE fail to comply with the terms and conditions of this LICENSE AGREEMENT. In the event of cancellation, the LICENSEE shall immediately destroy all written materials and all copies of the SOFTWARE, including modified copies, where appropriate.

7. MISCELLANEOUS. This LICENSE AGREEMENT is governed by the laws of the State of California (USA) if the LICENSEE acquired the SOFTWARE in the USA with respect to ARKEIA, their successors and assigns. This LICENSE AGREE-MENT is governed by the laws of the country of France if the LICENSEE acquired the SOFTWARE in any country except the USA, with respect to ARKEIA, their successors and assigns.

If you would like further information on this LICENSE AGREEMENT, please write to: Arkeia Corporation

1808 Aston Avenue Suite 220

Carlsbad, CA 92008 USA

(5)

WARRANTY *

ARKEIA warrants its SOFTWARE for a period of ninety (90) days as of the date of deliv-ery thereof. This warranty also includes reconditioning or replacing SOFTWARE media. ARKEIA does not warrant and does not enter into any commitments regarding the content of the documentation and the software. ARKEIA further disclaims any implicit warranties tied to the sale of the right to use license of this SOFTWARE with respect to its quality, its results, its merchantability or its suitability for a particular purpose. Consequently, the license to use this SOFTWARE is granted “as is”, without any promise being made. In the event of a defect in the software or in the documentation, the LICENSEE, and not ARKEIA, its dealers, distributors, agents, or employees shall bear all costs needed for ser-vicing, repair or correction.

Under no circumstances shall ARKEIA, or anyone else participating in the design, produc-tion and delivery of this SOFTWARE, be liable for any damages, whether direct, indirect, secondary or incidental, including, but not limited to, damages caused by loss of profit, business interruption, loss of information or any other loss, resulting from the use of this SOFTWARE, even if ARKEIA has been informed of the possibility of such damages. Information or advice given verbally or in writing by ARKEIA, its dealers, distributors, agents or employees shall not constitute a warranty, nor affect in any way this warranty, and as such, the recipient shall not in any way depend on any such information or advice. Arkeia and ARKEIA SOFTWARE are registered trademarks (TM) of ARKEIA Software, All Rights Reserved. All other trademarks mentioned in this documentation are the prop-erty of their respective owners.

(6)

(7)

T

ABLE

OF

C

ONTENTS

Copyright ...2

ARKEIA SOFTWARE LICENSE AGREEMENT ...3

WARRANTY * ...5

Introduction ...9

Prerequisites and installation ...9

Next ...10

Setup ...11

Software...11

Licenses ...11

How licenses work ...11

Password and email ...12

Email reports ...13

Exit Arkeia Server Backup ...13

Hardware ...13 Autodetect ...14 Tapes...14 Next ...15 Types of backup...17 Backup content ...17 Total backup ...17 Differential backup ...18 Incremental backup ...18 Backup start ...19 Interactive backup ...19 Deferred backup ...19 Periodic backup ...19

The backup cycle...19

Backup configuration information ...19

Next ...20

Backup to a tape drive...21

Total interactive backup ...21

Find the tape drive ...21

Log messages ...24

Email reports ...24

Total deferred backup, command before and after...25

Total periodic backup...26

Daily backup ...28

Differential periodic backup ...29

Incremental periodic backup...30

Next ...32

Backup using a tape library ...33

Tape cartridges ...34

The backup schedule...34

Total monthly backup...34

Differential weekly backup ...36

Incremental daily backup ...38

Next ...39

Restore data ...41

Restore a file or directory...41

Restore to a different location ...43

(8)

(9)

Introduction

Thank you for using Arkeia Server Backup, we are confident it will meet your requirements for a powerful yet simple-to-use single server backup manager. This User Guide describes in detail how to perform a range of typical backups, using all the features available in Arkeia Server Backup:

• backup configuration by start time and type;

• exceptions to scheduled backups;

• execution of commands before and after backup;

• using a tape library (autoloader);

• email reports of backup results;

• restoration to a different location; but how are you going to use it?

We don’t think you will want to read it from start to finish, or even work your way through the different backup configurations. We think you should treat the manual as a colleague who does the same kind of work that you do, someone who has already set up backups using Arkeia who can tell you how they got started. Look at the Table of Contents and find a backup like the one you want to set up, then fol-low the example in the book, making changes for your particular environment. Other sources of information are:

• Arkeia Server Backup Quick Start Guide. Use this guide to install and quickly familiarize yourself with the software by doing a simple backup. This guide booklet is supplied with the installation CD, and is also available online at the Arkeia website http://www.arkeia.com/a5manuals.html.

• The online context-sensitive User Guide appears in a second window when the Arkeia Server Backup interface is started. Use this as a reminder of the steps and button presses possible in the window actually displayed on your screen.

If it is not showing on your screen, click on the button.

Prerequisites and installation

If you have not yet installed Arkeia Server Backup, the Quick Start Guide

explains:

• what other software you need to run Arkeia Server Backup;

• how to get the Arkeia Server Backup software;

• how to install Arkeia Server Backup; and

• how to start Arkeia Server Backup.

Follow the guide to get your installation up and running. We also suggest you con-tinue with the Quick Start Guide to make two simple backups. This will verify that

(10)

your installation is working, and show you how the interface works. If everything runs smoothely, it will take less than an hour.

Setup

In this chapter, we take the basic working system which was installed by following the Quick Start Guide, and configure it to our system.

Software

There is very little to do to configure Arkeia Server Backup before you start using it. The main requirements are to enter your Arkeia licenses, and create a password to secure access to the server interface.

Licenses

Click on the Manage licenses button to access the Licenses management screen.

You may have purchased licenses for Arkeia hot-backup plug-ins, for disaster recovery or for larger amounts of stored data. Here is where the license information given to you by your supplier is entered to activate the full capabilities of your installa-tion.

Follow the instructions in the help screen which appears next to the Licenses manage-ment screen, to add your licenses.

How licenses work

Your license to use Arkeia Server Backup is based on the volume of data you want to keep in backup

storage, from which you can restore. First level of license

The first level of license is free. You can keep up to 50GB of data in storage, ready for restoration. When you have stored 42GB of backup data, a warning will be given. Once the limit of 50GB has been reached, Arkeia will advise you to buy a license for the next level. If you try to start a backup when you already have 50GB of data in storage, Arkeia will warn you and prevent the backup from starting. Second level of license

The next level of license is 100GB. You can have up to 120GB of backup data stored with this license. When you reach 100GB of data in storage, Arkeia will

(12)

warn you that it is time to upgrade your license. If you try to start a backup when you already have100GB of data in storage, Arkeia will warn you and prevent the backup from starting.

Licenses cover volumes in 100GB increments up to 1000GB, then 500GB incre-ments up to 5000GB, and they do not expire.

An indicator of the percentage of licensed data volume used is displayed in each screen, under the button bar.

The license level is proportional to the volume of data you have stored in backup, not the volume of data transferred. If it is acceptable to shorten the period covered by your backups, you can decrease the volume of data in storage by re-cycling tapes, and the percentage of license used will be lower.

Plugin Licenses

This is what the Arkeia plugin for MySQL license looks like. Hot backup plug-ins for spe-cific applications and data such as Microsoft Exchange and MySQL have their own separate licenses, one for each plugin. Enter the serial num-bers and checksums given to you when you purchased your plug-ins.

To see the details, highlight the license in the License name panel, and read the details in the panel below.

Password and email

Click on the Change password & email button, and follow the instructions in the context help screen to add your password.

(13)

When you first install

Arkeia Server Backup, there is no password. Before you con-figure the software to your live environment, you should add a password. Note that the Old password field will be empty, the first time you establish a password.

Changing the default root password of a network application such as Arkeia is the most basic security measure that can be applied, and should be considered mandatory in a production environ-ment.

Email reports

Arkeia Server Backup activity reports can be sent by email. If you want to activate email reporting, enter the email address in the Email field. One email report is gen-erated for each backup, and contains:

• date and time of the backup start and end;

• name of the backup server;

• name of the backup;

• type of backup (total, incremental or differential);

• name of the tapes which have been used;

• global statistics (amount of data, number of files, speed);

• a warning if the data volume limitation is exceeded; and

• report if the backup is aborted.

Exit Arkeia Server Backup

To exit Arkeia Server Backup, click on Server button, then click on Quit in the Arkeia Server Backup Login screen.

If you have installed Arkeia Server Backup on other servers, you can logon to them by click-ing the Server button, and entering the Server host name and Password of the new server.

Hardware

Hardware setup is also very simple, you just need to:

• run autodetection to find the tape drives and tape libraries connected to the server on which Arkeia Server Backup is running; and

• declare the tapes you will use.

(14)

Declaring the tapes is done when you create a backup. You define the tapes to be used by the backup, and Arkeia then tells you how to label them so that they can be retrieved when necessary.

Autodetect

Click on the hardware management button and follow the directions in the Arkeia Server Backup Help screen to list attached hardware.

You probably ran autodetect when went through the Quick Start Guide, but you can do it again any time you need Arkeia Server Backup to check for new or different hardware.

Here, we see the details of a tape library which was detected. To see details, we highlight it in the list panel. In this screen we can control the autoloader. We see how to do this in the chapter Backup using a tape library on page 33.

A server with a single drive attached will list that drive. See Find the tape drive on page 21 for an example. All accessible tape drive hard-ware will be displayed.

Tapes

When you create a backup, you will be asked to add tapes. Arkeia Server Backup will create logical tapes with label names, for the backup. You also add or remove tapes in the backup screen. If the backup requires more tapes, it will be paused and a message will appear requesting you to label an additional tape and put it in the tape drive.

The tapes you add will now be managed by Arkeia Server Backup. Arkeia will keep track of the tape life, remind you when it needs to be cleaned and warn you if it becomes faulty. Your responsibility is to label the tapes with the name Arkeia gives you to make them easy to identify, and keep them in a safe place where they can be found when needed.

(15)

Types of backup

Arkeia Server Backup allows you to configure different types of backup by choos-ing combinations of backup content and backup start. The available combinations are:

Backups are usually (or certainly should be) done regularly. The time between each backup we refer to as the backup period (or just period).

When we refer to files, we mean files in the UNIX sense. We mean a file, a direc-tory, a directory tree, a disk or the data content of the whole server.

Backup content

The content of a backup you make describes the state of the data files which are to be stored in the backup, compared to their state in a previous backup. Since a pre-vious backup, a file will:

• have changed;

• have not changed; or

• be new.

If there is no previous backup, all the files are considered to be new. There are three backup classes based on the backup content:

1. total,

2. differential, and 3. incremental.

Total backup

A total backup includes all files, whether they are changed, not changed or new. The total backup takes longer to do and requires more storage space than a differ-ential or incremental backup.

Yes this combination is

possible

No this combination is not

possible

Backup content

Total Differential Incremental

Backup start

Interactive Yes No No Deferred Yes No Yes

(18)

Differential backup

A differential backup stores all of the changed files since the last total backup. The longer the time since the last total backup, the larger is the size of the differential backup, and the longer it takes to complete. In the diagram above, the backup Dif-ferential 2 is bigger than Differential 1 because it includes Differential 1, and the new or changed files since Differential 1.

To restore to a given point in time in the cycle, you require: 1. the last total backup, and

2. the last differential backup for that point in time.

Incremental backup

An incremental backup stores all the new and changed files since the last backup, whether it is a total backup or an incremental backup. Incremental backups (after the first incremental backup) are usually smaller than differential backups, because they do not include the data recorded in the previous incremental backups.

Total backup

Differential 1

Differential 2

Differential n

Incremental 1 Incremental 2 Incremental n

Differential backups

Incremental backups

Backup period 2 Backup period n Backup period 1

(19)

To restore to a given point of time in the cycle, it is necessary to have available ALL the incremental backups since the last total backup. For example in the dia-gram above, to restore to the state as at Backup period 3, you require:

1. the last total backup, 2. Incremental 1, 3. Incremental 2, and 4. Incremental 3.

Backup start

Arkeia Server Backup provides three methods of choosing when to start a backup: 1. interactive,

2. deferred, and

3. periodic (or scheduled).

Interactive backup

You can start an interactive backup at any time. The interactive backup only starts on your command, and runs once.

Deferred backup

A deferred backup is a backup whose start time has been delayed. It may originally have been an interactive or periodic backup, which you want to commence at a later time.

Periodic backup

Periodic backups start unattended, at a time specified by you in the backup config-uration. They are scheduled backups which repeat at regular intervals of time. You can create exceptions to individual scheduled backups.

The backup cycle

It is not economical or practical to make every backup on a new tape. Normally, the backup tapes are kept for a period of time then recycled by overwriting with a new backup.

An efficient way to minimize the time and memory space used while ensuring data security, is to first back up everything, then at regular intervals backup the changed data. After a few of these intermediate backups, it is advisable to again back up everything, then restart the cycle and make backups of the changed files. This is the backup cycle.

Backup configuration information

When you configure a backup, you will need to supply the following information to Arkeia Server Backup:

• a name for the backup;

• backup start method;

• backup content type;

(20)

• start time for deferred backups or

start time and backup period and exceptions for periodic backups.

Backup to a tape drive

In this section, we are going to describe in some detail the backups we made on our server lune. This server handles all the data and applications used to run the (imaginary) Arkeia Sports Centre, which consists of:

• Management and administration

• Maintenance department

• Shop

• Swimming pool

• Tennis courts

• Gymnasium

We don’t really have a sports centre like this at Arkeia, as you could probably guess when you look at the title bar in some of the panels in the manual: they refer to our test servers. But we can always dream...

The examples in this and the next section range from a simple total backup to one drive, to periodic backup schemes with exceptions, and backups using a tape library. Follow these examples to find out how to use all the features of Arkeia Server Backup.

Our first backup project was to make a total backup of the Arkeia Sports Centre files, which are located on the server lune. Arkeia Server Backup has been installed on lune, so we fired up the GUI on our worksta-tion, and entered the server name and pass-word in the Login screen.

Eventually, we will design a backup which

will schedule a new total backup each week, and make more frequent backups of changed data. A backup like this will optimize the tape space we use, and allow a roll-back of the data to any end-of-day point in time. But first, we wanted to feel our way with an interactive total backup, just to see how things work.

Total interactive backup

The centre had just opened for operations so the staff were all new and had no experience with the particular computerized management system being used, so we wanted to get the present data on tape before someone accidentally obliterated it, and to give us something to roll back to if things went wrong.

Find the tape drive

Since this was the first time we had run Arkeia Server Backup on lune, we found the tape drive by clicking:

(22)

We saw that our single attached tape drive has been found, so then we moved on to design the backup.

To design a backup, we clicked:

Backup management > Create

In this screen we entered a name for the backup and chose Interactive backup type. We called our backup

sports_centre_total_bckp.

We click on Next in the step navigator at the bottom of this screen:

(23)

In this step we selected the list of files to be included in the backup.

The upper panel in this screen shows the server on which we are working. We double-clicked on the server line to reveal the next level of data below, and continued double-clicking to navigate our way to the files (or directories or disks) we wanted to include in this backup.

We found the directory called Arkeia_sports_centre, which is the one we want to include in this backup. With this direc-tory highlighted, we clicked on to include it in

the list, which is shown in the lower panel. We could add other files from anywhere on lune by navigating to them in the same way. To backtrack up the navigated path, click . Remove removes the file currently highlighted, and Remove all does just that, removes all the files from the Selected files list.

We clicked on Next to go to step 3. The hardware for the backup was selected in this step. In our case, there is a single drive, so no choice was necessary. We clicked on to save the backup configura-tion, and

Arkeia Server Backup imme-diately asked us to prepare a tape for this backup, by label-ling it with the name sug-gested.

We took an unused tape, labeled it:

sports_centre_total_bckp_Tape_1 and put it in our tape drive.

It is tempting to skip this small task and start the backup, after all, Arkeia Server Backup writes the label to the tape itself. But think what it would be like after some time when we have a box full of backup tapes,

(24)

some labeled and some not labeled. We need to find a file, Arkeia Server Backup tells us what tape it is on but we did not label that tape, or five others that we have in our box. Now we will have to load each unlabeled tape so that the software can read it and check whether it is the tape needed. Too bad if we are in a hurry to restore that file!

We clicked on OK and a message appeared asking if we want to start the backup now. We clicked Yes.

Here in the Job activity screen we saw that the backup was progressing.

Global progression

Arkeia Server Backup enables you to run a backup and a restore in parallel, one on each disk drive attached to the server. The Global progres-sion panel gives information for all backups and restora-tions currently running. Flow activity

A backup and a restoration running simultaneously in there own Flows. Data for indi-vidual flows shown below the global progression informa-tion. Our backup has only one flow.

Log messages

At the bottom of this screen, we saw the two most recent lines of a log of activity. We expanded the window by drag-ging on the corners to see more of the log. This is what it looked like after our backup finished.

Email reports

(25)

From: root <[email protected]> To: [email protected] Subject: Arkeia backup report

Backup server : lune.bat1.fr.arkeia.com Backup start : 2005/05/04 10:08:53 Backup type : Total

Backup name : sports_centre_total_bckp Backup end : 2005/05/04 10:10:24

Backup statistics : "27" files, "94" MB, compressed at "1.0", "89" seconds, +"63" MB/mn Used tapes : sports_centre_total_bckp TAPE 1 Flow 1 2005/05/04 10:09:39 [1] Backup of +"lune.bat1.fr.arkeia.com!file:/home/hub/Arkeia_Sports_Centre" OK, "27" files, +"94" MB, "19" seconds, "296" MB/mn, "0" warnings

Email reports are sent for every backup that is successfully started, provided you have supplied an email address (see Password and email on page 12).

Total deferred backup, command before and after

Quiet times for the Arkeia Sports Centre are nights from midnight to 5am the next day, unless the maintenance staff are working on a project. The only time the main-tenance folks are not likely to be working is from midnight on Sunday to 8am on Monday. I needed to make a total backup of everything:

• with as little disturbance as possible to the Centre, and

• without having to be on-site myself at some inconvenient time.

When the amount of data in the backup grows big, hot backup plug-ins will be the answer. These allow databases and server processes to remain operating while the backup is running. For the moment, with a small installation, we used the Manage backups > Advanced options to run scripts to shut down the running applications before the backup started, and re-start the applications once the backup finished. We created two scripts:

1. stop_sports

a. checks if applications are currently running,

b. warns the user that the application is closing and will be unavailable during backup, then

c. closes the applications.

2. start_sports which re-starts the applications which were stopped before the backup started.

We created the new backup by editing the previous backup. We clicked on: Manage backups;

(26)

the name of the backup we have already cre-ated;

to make changes to the highlighted backup; then to display the advanced options:

In this screen, we selected Deferred backup from the drop-down list in the Type field, and entered the com-mands needed to start the shell scripts which stop and start the applications whose data is being backed up. The syntax is: hostname:/path/command and the hostname is in the form of a fully-qualified domain name.

Notice that we checked the box Execute command if backup fails. This will restart the applications even if the backup fails. We did not check the box Backup if command execution fails, to avoid clashes which could occur if Arkeia and the application try to access the same data simultaneously.

These are the only changes we wanted to make to the backup, so we clicked through the following screens accepting the current settings, until the Backup launcher panel became available:

Here, we set the date and start time for the backup. The date fields are month/day/year. The backup was set to start at

11:30pm on Sunday, May 8th, at which time the system adminis-trator was at home.

Total periodic backup

That worked, so we decided to make it a regular program by creating a periodic backup which will run at the same time every Sunday night. One small problem we had to deal with was that during the next school vacation period, there was a Kids’ Camp with competitions running all night for one Sunday, requiring the system to be available to record results. We handled that situation with the Exceptions option.

(27)

Again using sports_centre_total_backup, we edited it to make it repeat weekly. We clicked on:

Manage backups >

sports_centre_total_backup > Edit

and changed Type to Periodic backup. In the Every field, we chose (1) week(s), and checked Sunday, then dialled up start time of 23:30 in the Repeat at field. We checked the Activate box, then clicked on Next to go to the next step.

There is nothing to change in the last two steps, because the data we want to backup and the tape drive we use does not change, so we clicked through these step to get back to the to the Manage backups screen.

Here, we clicked sports_centre_total_backup then on to show a cal-endar view of the backup schedule we created:

We scrolled to the month of July in the date bar. The kids’ overnight gym camp is on July 10th to 11th, and there is a backup scheduled for that night so we want to stop that backup (and substitute another night to replace it).

(28)

We clicked on the back button then on , which displayed a calendar view.

We scrolled to July in the date bar, then clicked on the 10th to cancel the backup for that night.

We clicked on to confirm the exception. The lat-est message in the log window confirms that we successfully modified the backup.

So, from now until the end of time, if:

1. the server and network remain operational; 2. nobody changes the backup configuration; and

3. a tape labeled by Arkeia Server Backup with sufficient space on it is in the tape drive before 11:30pm on Sunday nights;

a total backup will be made of the sports centre data, but...

Daily backup

After some months, the sports centre became very busy, especially the shop, and it was too risky to rely on a weekly backup of the shop sales and inventory data. We needed daily backups of the shop data, and the ability to roll it back to any day since the last total backup.

The shop data is backed up once per week in the Sunday total backup, so we only needed to backup the shop data which had changed since the total backup. This suggests a differential daily backup, based on the total backup we have already cre-ated.

(29)

Differential periodic backup

We created a new backup: sports_cen_shop_daily_backup, with the configuration shown here.

This is a differential backup, which will run at 1am. Note that although it is a daily backup, we did not want it to run on Sundays because that is when our total backup, which includes the shop data, will run. So we selected Every 1 week, and checked every day except the Sunday box. In the next step, we chose the files to be added.

We navigated our way down the tree which contains the sports centre data, one level further below the last backup to the Shop directory, and Added it.

The next step selects the tape drive to use, nothing to change here so we clicked Save, and created one new tape for this backup when the New Tape Notification panel appeared.

(30)

Now all we have to do is ensure the correct tape is in the tape drive each night before the backup starts. Since this is an unattended backup, we also need to ensure that the tape in the drive has enough space on it for the next backup.

Incremental periodic backup

Things started hotting up in the Arkeia sporting community: a lot of training was being done in preparation for some big competitions coming up, so the training logs were changing every day. The coaches were worried about losing the training data and at the last weekly staff meeting asked for daily backups to be made. “Okay” we said, thinking we could easily add a training log file backup in Arkeia Server Backup to run at 2am. But, can you spot the problem?

We are already running a daily backup of the Shop data. Who will come in at 2am to change the tape cartridge for the training log data? Not me!

We decided to make a combined daily backup of the Shop data and the training data. Noticing that some files only change once or twice per week, we chose to make this backup an incremental backup. An incremental daily backup will store only those files which have changed since yesterday, but each differential daily backup stores all the files which have changed since Sunday (the last total backup), so the files which have changed only once are duplicated every day. An incremen-tal backup could save tape space, and time.

Delete a backup

We clicked on then sports_cen_shop_daily_backup then to remove it. We also clicked on then highlighted the names of the tapes assigned to this backup, then to release the tape from its backup, then

to delete the logical tapes assigned to this backup. Note that

Arkeia Server Backup would not allow us to delete a tape which has not been recy-cled.

(31)

We created a new backup: sports_centre_daily_bckp, with this configuration in Step 1.

In the field Based on, the first backup in the list of backups appears. Our incremental backup must be based on itself if it is to be a daily backup, however we have not finished creating it. It will be necessary to return to this screen and edit it to correctly base the daily incremental backup.

We clicked on Next to start adding files and trees to this new backup.

We navigated through the directory structure to locate the Training files in the Gym-nasium, Swimming and Tennis directories, and added them to the backup. We also added the Shop data to the backup, then clicked Next.

Step 3 chooses the tape drive, which remains unchanged, so we clicked on Save, and cre-ated a new tape in the next screen.

To make it easier to keep track of backups, we decided to cre-ate one tape for each daily backup.

We clicked on to open

the Tapes management screen, then we highlighted the existing tape for the backup sports_cen_daily_bckp Tape 1, then clicked on and added another five tapes, so we then had one tape for each daily backup, for one week.

(32)

Make it a daily backup

To be a daily backup, this incremental backup must base itself on the previous daily backup, that is, on itself. To do this, we clicked on then

to re-visit Step 1 in the backup creation process.

Here, we changed the Based on field to sports_centre_daily, to make this

incre-mental backup a daily backup. We clicked through the remaining steps, without changing anything.

We now have a weekly total backup program of all the Sports Centre data, and a daily incremental backup of the shop and training log data.

Backup using a tape library

Some time later, the backup requirements of the Arkeia organization have increased, and a tape library has been installed on a new server. The backups for the Sports Centre have also increased in size and number, and we have been allo-cated some tape slots in the library to use in our backup program. We decided to make an entirely new program, to take advantage of the new hardware.

We logged in to

Arkeia Server Backup on the new server, and clicked on

to see the tape library. Clicking on the device in the list revealed the library con-tents.

In this screen, the details of the tape library are shown, and we can load, unload and read labels. To move tapes between slots:

1. load the tape into the drive,

2. click on the empty slot where you want to put the tape, and

3. click on Unload.

The first thing to notice is the red bezel, which shows that it is turned off to

Arkeia Server Backup. It is not physically turned off. We clicked on the left bezel to reconnect with it.

Note: re-initializing the tape library by clicking the red, then the green bezel will often clear minor hold-ups.

The scroll frame beneath the bezels show the device driver, /dev/st0 in our case, and the contents of the tape drive, which was [Empty] at this time. The Voltag is the Arkeia identifier given to each tape cartridge.

(34)

Tape cartridges

When a backup is created, one logical tape cartridge is defined by Arkeia Server Backup. In the manual system, we had to:

1. find an available cartridge; 2. label it; and

3. put it in the tape drive for the backup to proceed. Now, steps 2 and 3 are done for us by the tape library.

When we create a backup, a logical tape is created at the same time. When the backup first starts, the tape library finds an unused tape (listed as Unknown in the Drives and Libraries Management screen), labels it with the backup name and a tape number, then inserts it into the drive. The next time that backup is run, or if we want to restore data from a previous backup, Arkeia Server Backup knows where to find this tape, and loads into the drive again. If the tape becomes full, during the backup, Arkeia will:

1. unload the full tape cartridge from the tape drive; 2. find another available tape;

3. load it into the tape drive;

4. label it with the backup name and the next tape number; then 5. continue the backup.

The life of the backup administrator becomes easier, more than one backup can be run unattended, because the tape library will handle tape changes.

The backup schedule

A monthly total backup is required. Data which changes frequently is backed up in daily incremental backups. Data which changes less frequently is backed up in weekly differential backups.

Total monthly backup

We clicked on to start creating the total backup, and noticed that some backups had already been created by other departments in the organisa-tion. Our Sports Centre data is on a shared server.

(35)

We clicked on to start configuring the total backup. It is a periodic total backup running on the first Sunday of each month, starting at 11pm, and we named it sports_centre_total.

It is again necessary to run the scripts which started and stopped any open processes, and we set this up after click-ing to display the advanced options.

(36)

We clicked our way through the directory structure to find the Arkeia_Sports_Centre tree, and clicked on to include it in the list, which is shown in the lower panel.

In the next step, we made sure the tape library was selected, then clicked on to save the backup configuration.

A new tape notification message appeared. At this point, only a logical tape has been created, no tape in the tape library has been selected or labeled.

When the total backup we have just created first runs (next Sunday night), Arkeia Server Backup will select an unused tape in the tape library, label it sports_centre_total Tape 1, insert it into the drive and start the backup. If the tape is filled before the backup is completed, a second tape will be selected from the library, labeled then inserted, and the backup will continue.

Differential weekly backup

The sports centre administration data changes often enough to require weekly backup, so we decided to make a weekly differential backup, based on the monthly total. Each differential backup will contain the data which has changed since the last total backup.

(37)

We clicked on to start creating the differential backup, which starts at 2am on Mondays. It is based on the total backup, which means that each Monday, all the files which have changed since the last total monthly backup will be saved to tape.

In the Advanced screen, we entered our stop_sports script to run before the backup, and our start_sports script to run after the backup, even if the backup fails.

We clicked on to go to the next screen.

In this screen, we clicked on the directories and files to be included in the backup, and on

to put them in the list, which is in the lower panel. We selected the directo-ries Accounting, Management and Operations, for the weekly backup.

We clicked on to go to the next screen, and con-firmed that the tape library was selected for this backup then on to save the backup.

The New Tape Notification screen appeared, confirming that the backup was saved and that a new logical tape was created. When this backup first runs, an unused tape will be taken from the library, inserted into the tape drive, labeled as sports_centre_weekly Tape 1, and the backup will start.

(38)

Incremental daily backup

The sports centre shop data and training log data changes frequently, and must be backed up daily. We chose to make this backup an incremental backup.

We clicked on to start creating the incremental backup, which starts at 4am every day of the week. To be a

daily backup, it must be based on itself.

The first time it runs, all the selected files will be backed up

The second time it runs and every other time, until the tape is recycled, it will save the files to tape which have changed since the previous daily incremental backup. We will have to return to this screen after the daily backup is saved, and change the Based on field to refer to sports_centre_daily.

When the tapes containing the daily backups are recycled, the backup cycle re-starts, and the first incremental backup will copy all the files selected onto the new tape.

We clicked on to go to the Advanced screen, where we entered our com-mand to run the stop_sports script before the backup, and run our start_sports script after the backup, even if the backup fails. Then we clicked on to go to the next screen.

(39)

In this screen, we navigated our way to the directories and files needed in this backup by highlighting them in the top panel, and on to put them in the list, which is in the lower panel.

We clicked on to go to the next screen, and con-firmed that the tape library was selected for this backup then on to save the backup.

Arkeia Server Backup created a new logical tape: sports_centre_daily Tape 1. When this backup first runs, an unused tape will be taken from the library, inserted into the tape drive, labeled as sports_centre_backup Tape 1, and the backup will start.

Make it a daily backup To be a daily backup, this incremental backup must base itself on the previous daily backup, that is, on itself. To do this, we clicked on then

to re-visit Step 1 in the backup creation process.

Here, we changed the Based on field to sports_centre_daily, to make this

incre-mental backup a daily backup. We clicked through the remaining steps, without changing anything.

Restore data

An obvious point, but one which needs to be made, is that you can only restore data if you can find it on a tape cartridge. This means that tape cartridges need to be labeled and put in a place where they can be found. Arkeia Server Backup will tell what tape contains the data you want to restore, using the label title given to you when you created the backup.

Restore a file or directory

A new clerical assistant in the Arkeia Sports Centre administration office spent a day entering data from membership forms into the membership records. Unfortu-nately, due to various problems of communication, the current member data and the non-current member data has been mixed up. The manager thinks it would be better to restore the files to their last known correct state, and re-enter the new data.

The last good copy of this data is in the weekly total backup, so we need to: 1. find the files to restore;

2. find the backup containing those files;

3. find the tape cartridge containing the backup.

This is an example of a restoration from a single tape drive system. We clicked on to start the process.

In the Restore window, there are two ways of finding files:

• Navigation • Search

We chose Navigation, and clicked to see the backups available in the drop list Backup done on.

(42)

We selected the backup needed, then clicked our way down through the directory structure to find the files. We highlighted these files and clicked on to add them to the list of files to restore in the lower panel, then clicked .

We located the tape cartridge, which had been labeled clearly at the time it was created, inserted the tape cartridge into the drive and clicked on

to start the resto-ration.

(43)

After some tape rewind and search time, the restoration began and the files from the last total backup were restored.

Restore to a different location

Squash has been added to the Arkeia Sports Centre activities, and management has decided to create a Racquets section which will contain Tennis and Squash. We used Arkeia Server Backup to "restore" /Tennis files to /Racquets/Tennis/.

(44)

dragging the corners.

In this example, we will restore the Tennis training files to a new location. The server is quanta, which has a tape library attached. In the search field Filename containing we entered "training", and clicked on . The files found were displayed in the Result panel, and we found the Tennis training* files, high-lighted them and clicked on to add them to the list in the lower panel. In the next screen, the tapes on which these files were stored were listed. We veri-fied that the tape needed was present in the tape library by:

1. opening a new instance of the Arkeia Server Backup interface; 2. clicking then the name of the tape library in the list; and 3. seeing that the tape is in the list of library tapes.

Since we wanted to redirect the restored files to another location on the server, we clicked the tab then the Apply a redirection box.

We used the scroll list in the Source field to locate the data to be restored, and entered the new location in the Destination field, then clicked on to check that the redirection was correct.

(45)

We then clicked on

to start the restoration process. After a short delay while the autoloader loaded the tape and found the data, the files were "restored" to the new location.

Out of curiosity, we clicked to see how the job progressed, and this log was displayed.

Support

We have described a fairly normal set of backup and restore operations using Arkeia Server Backup, on a small server. There are countless variations and com-binations of tasks you might want to do with this software, some of them might be tricky to implement, so Arkeia Technical Support is available to provide advice and help solve any problems you have. You can contact them through the Arkeia

(46)

website at http://www.arkeia.com/support.html. On this page, you will also find information about:

• Support programs

• the Arkeia FAQ

• the Arkeia knowledge base

• Arkeia user community mailing list

Also, check the website for the latest updates to our software.

Finally, we would like to hear from you! If you have any remarks, corrections or ideas about the documentation, please email them to [email protected]. Note that this email address is only for documentation matters. Tech support and sales mat-ters are handled through the website http://www.arkeia.com.

(47)

I

NDEX

A

activity log 24

add files to backup 23 add tapes to a backup 31 advanced options 25, 26, 35 Arkeia Sports Centre 21 autodetect hardware 13, 14

B

backup 19 add files 37 calendar 27 change 26

command before and after 25 daily 28, 38, 39

date and time 26 deferred 25 delete 30 differential 29, 36 incremental 38 interactive 22 list of files in 23 monthly 34 periodic 34 schedule exceptions 26 total 25, 34 total interactive 21 weekly 36 backup cycle 18, 19

backup if command execution fails 26 Backup management 22 backup type 26 backup types 17 based on field 31

C

calendar 27 checkbox

execute command if backup fails 26 close 13

command

backup if execution fails 26

execute if backup fails 26

command before and after backup 25, 38 commands 25 configuration Arkeia 11 backup 19 context-sensitive help 9 Create 22, 35

D

daily backup 28, 38, 39 data navigator 23 date and time 26

deferred backup 17, 19, 26 define tapes 14 delete backup 30 delete tape 30 Detect 21 differential backup 17, 18, 29, 36 differential periodic backup 29 disaster recovery 11

E

edit backup 26 Email reports 24 email reports 13 enlarge screen 43

exceptions to backup schedule 26 execute command 26 exit 13

F

FAQ 46 files add to backup 37

add to, remove from backup 23 find to restore 41

find files to restore 41 Flow activity 24

(48)

G

Global progression 24

H

hardware autodetection 13, 14 Hardware managemant 21 hot-backup 11

how to use this Guide 9

I

incremental backup 17, 18, 30, 38 incremental periodic backup 30 Index 47

information sources 9 interactive backup 17, 19

J

Job activity 24

job activity monitor 24

K

knowledge base 46

L

license 11 log 24 logical tapes 14 Login screen 21

M

mailing list 46 Manage backups 25 monitor backup 24 monitor job activity 24 multiple instances 13

N

navigator 23

O

online manual 9

P

periodic backup 17, 19, 30 periodic differential backup 29 plug-ins 11

point in time restore 18, 19 progress monitor 24

Q

quit 13

R

recycle tape 30 redirected restore 43 remove

files from a backup 23 remove files from backup 23 reports

email 13, 24 log 24 restore

point in time 18, 19

restore files to new location 43

S

screen

enlarge 43 scripts 25

single attached tape drive 22 software license 11

sources of information 9 support programs 46

T

tape drive, find 21 tape library 33

load and unload tape 33 tapes

add 31

(49)

delete 30 label 23, 34, 41 logical 14 recycle 30 total backup 17 type of backup 26

U

updates 46

W

weekly backup 36

(50)