Enfoques de las estrategias de aprendizaje

All communications between BackupEDGE and S3 are performed over an encrypted link. Strict authentication ensures that data is kept secure from unauthorized access.

A two-stage authentication process is used to protect the authentication keys.

• On initial setup, the users logs into their Amazon Account through a special URL and selects BackupEDGE as a billable product. An Activation Key valid for only 1 hour is generated.

• With that one hour, the user must run the BackupEDGE EDGMENU program, run S3 setup, and type or paste the 1 hour Activation Key.

BackupEDGE will connect to the S3 service and use a combination of its product code and

the Activation Key to download a Security Key unique to the client account. The

Security Keyset is embedded into BackupEDGE and S3 access becomes transparent from

that point. A private storage area (S3 calls it a bucket) will be created on S3.

If BackupEDGE ever needs to be re-installed from scratch, the Security Keyset can be retrieved at any time by logging back into S3, generating a new Activation Key, and typing/pasting it into BackupEDGE.

As long as the S3 account remains open, stored archives may be retrieved. Closing the account or canceling the BackupEDGE service within the account will result in the loss of all stored data.

Only the https port (port 443) needs to be open on the user firewall for S3 services to function. The following servers are accessed:

• ls.amazonaws.com • s3.amazonaws.com

5.3 - Theory of Operation

BackupEDGE AWS Resources are very similar to the URL Resources used for FTP Backups.

However, there are a few points you should be aware of before using them.

In a tape, DVD, or similar backup, BackupEDGE streams the data directly on to the media as a single complete archive. In AWS backups, as in FTP backups, BackupEDGE streams the data into archive files in the S3 cloud. One of the restrictions in S3 storage is that, before sending an archive file you must tell S3 the length of the file you are sending.

To work with this restriction, BackupEDGE automatically segments archives; that is, it divides one logically long archive into many short archive files (called segments) that are small enough to keep from filling the hard drive while keeping the backup streaming at maximum network bandwidth. By default, these segments are 10 megabytes in length. This is configurable but usually not necessary.

BackupEDGE can write multiple archives to AWS servers, and each archive may contain

multiple segments. BackupEDGE handles segments automatically, and provides tools for managing the segments if desired. To maintain consistent archives, the individual segments should never be manipulated by operating system commands. This is why segments do not have names that make sense to humans.

Slots

BackupEDGE uses the concept of a ‘slot’, similar to a tape library slot, to manage the

archive segments. Every time you write a backup to an AWS resource, you must select which slot to be used. Each archive is a collection of one or more segments automatically managed managed as a single named slot. A slot can hold no more than one backup. You cannot store two different backups in one slot, just like you cannot store more than one tape in an

autochanger slot.

Every slot has a name. While autochangers use ‘st1’, ‘dt0’, or a barcode label, AWS Resources can use any short name at all. The name must be less than 32 characters in length. No two slots on the same medium have the same name.

When setting up a Scheduled Job, you may select the slot name for each day of the week. This way, you have control over when the backups are overwritten; every time a backup is made with a slot name that is already in use on that medium, the existing backup is erased in favor of the new one. The slot name may be entered in the ‘Slot Name’ field of the

scheduler.

The slot name accepts various substitutions to make copying schedules between machines easier, and to provide more flexibility about when backups are overwritten. For example, the substitution ‘%d’ will expand to the day of the month (01..31), so that a slot name of

Slot Name Substitutions

Remember that the slot name after substitution cannot be more than 32 characters. In other words, %Y counts as four characters, since it expands to a four-digit year.

The default slot name is ‘%w.%n.%N’, which is the Scheduled Job day of the week, host name,

and job name. Thus, by default, each backup will be kept for a week. Note that usually, if you are backing up multiple machines and/ or schedules to S3 using the same account, you will create multiple AWS resources, one per machine/schedule combination. Each resource would use a different directory S3. A typical schedule would look like this:

Sample S3 Backup Schedule

This schedule will perform Monday through Friday backups. In the example, a five backup rotation will be created, with the Slot name translating to:

1.show1.simple_job (Monday)

2.show1.simple_job (Tuesday)

3.show1.simple_job (Wednesday)

4.show1.simple_job (Thursday) 5.show1.simple_job (Friday)

Because of these definitions, during each successive week the backup of the same name on Monday will be erased before the next backup is started, The same will happen every day, essentially creating a rotation of 5 nightly backups.

You can change the Slot Name to any combination of variables or text. For instance, the Slot name %d.Accounting would create an archive labeled 23.Accounting if the schedule were

run on the 23rd day of the month. It is easy to modify Slot names for maximum flexibility.

%n: machine hostname

(no domain name is included) %w: day of the week(0 is Sunday, 6 is Saturday)

%N: name of scheduled job %d: day of the month (01..31)

%S: second %j: day of the year (000..365)

%M: minute (00-59) %m: month of the year (01..12)

%H: hour (00-23) %Y: year (CCYY)

%y: year (YY)

+ Edit Backup Schedule ---+ | Schedule Name: simple_job | | Time: [23:00 ] (22:00:00) Enabled: [X] | | Sequence: show1:esequence/onsite_system | | Backup Domain: show1:edomain/system | | Primary Resource: [Change] show1:aws!aws0 | | | | Day Enable? Slot Name | | Sunday [ ] [%w.%n.%N ] | | Monday [X] [%w.%n.%N ] | | Tuesday [X] [%w.%n.%N ] | | Wednesday [X] [%w.%n.%N ] | | Thursday [X] [%w.%n.%N ] | | Friday [X] [%w.%n.%N ] | | Saturday [ ] [%w.%n.%N ] | | | | Notify / Advanced: [Change] | | Mail Summary To: NONE Print Summary To: NONE | | Mail Failures To: NONE Print Failures To: NONE | | | |[Save] [Cancel]| +---+