• No results found

Adding Amazon Web Services to an Existing Amazon Account

In document User Guide - Release (Page 145-152)

If you have not signed up for Amazon Web Services within your Amazon account, here is an example walk-through of what you’ll see when you log in to the special BackupEDGE AWS URL:

Complete the form, check to indicate that you agree to the terms of the Amazon Web Services

Next, you’ll need to add the information for the credit card that will be billed for the service. Fill out the form appropriately and click [Continue].

Next, there is an identity verification procedure. Complete the procedure with the appropriate phone number as show in the screen below.

Amazon will call the number you specify and display a PIN number. Type the PIN number into the phone, verification will complete, and you’ll see the acknowledgement as shown below.

Next, you’ll be asked to select an AWS Support Plan.

You are now configured for Amazon Web Services.

You may add multi-factor authentication or other service levels if you choose. These do not affect the fundamental operation of BackupEDGE with AWS. At this time, close the browser and go back to the Amazon Web Services login screen Amazon through the Microlite administration page using this URL: http://www.microlite.com/s3_devpay/s3admin.html.

s

13 - Configuring Legacy Disk-to-Disk Backups

13.1 - General Concepts

Most users will want to configure and use SharpDrive Media as described in “Configuring SharpDrive Backups” on page 77. This section is for OpenServer 5 users or those with a vested interest, such as combining them with URL backups for a various backup-restore combinations. Disk-to-Disk Backups are also known as D2D Backups or Directory Backups.) These are backups using a (preferably removable) hard disk or flash storage device. Two Resources combine to make Disk-to-Disk backups function:

• FSP Resource, or FileSystem Partition Resource, defines and controls the directory on the filesystem where archives are stored. No other files may be in this directory except those created by BackupEDGE.

• AF Resource, or Attached FileSystem Resource, defines the commands BackupEDGE must use to mount and unmount the device / filesystem containing the FSP Resource. No other user or process should mount and unmount the filesystem.

13.2 - Multiple Archives Per Medium

BackupEDGE supports performing multiple backups onto FSP Resources. The quota for an FSP Resource is defined by the user during setup. This is the general behaviour.:

13.3 - Compatibility Matrix.

YES - Compatible with BackupEDGE and RecoverEDGE.

PART - Compatible with BackupEDGE but not RecoverEDGE.May be used for fast, temporary backups.

Medium Archive Behaviour

FSP

The process will attempt to create a new archive. If starting a new segment would cause the quota to be reached, the oldest expired archive will be erased in its entirety (all segments). If starting a new segment would exceed the quota and no more expired archives exist, the backup will FAIL.

Operating System

Linux UW7 OSR 6 OSR 5.0.7 Medium

SATA Quantum GoVault YES YES YES NOa

a. The OpenServer 5 IDE/ATAPI driver is incompatible with these SATA devices.

SATA RDX/RD1000 YES YES YES NOa

USB Quantum GoVault YES YES YES YES

USB RDX/RD1000 YES YES YES YES

USB Standard Hard Drive / Flash Drive YES NOb

b. USB hard drives / flash drives which are hot plugged may not be used with these operating systems safely.

NOb YES

CIFS / Samba Network Mounted Filesystems PART NO NO NO

NFS Network Mounted Filesystems PART PART PART PART

NO - Not compatible with BackupEDGE or RecoverEDGE, generally because of an operating system limitation.

Removable Disk Cartridge Systems

Removable disk cartridge systems such as the IBM / Quantum GoVault and the RDX / RD1000 are easy to use and compatible with BackupEDGE and RecoverEDGE when the operating system is marked YES above. Drive cartridges must be pre-formatted with the proper filesystem type for your operating system.

Removable Hard Drives / Flash Drives

Removable hard drives, including USB hard drives, flash drives, etc. make excellent D2D devices and are completely compatible with BackupEDGE and RecoverEDGE. Flash drives are treated exactly as hard drives and, like hard drives, must be pre-configured with the proper filesystem type for your operating system.

Network Mounted Filesystems

Network mounts, such as NFS and CIFS/Samba, are excellent storage resources, but are NOT compatible with RecoverEDGE. They are useful for quick storage, targeted backups, and data migration, but RecoverEDGE boot media does not have the ability to mount and restore from them. For this reason FTP Backups are the preferred method for performing network backups. See “Configuring FTP/FTPS Backups” on page 87 for more information.

Local Filesystem / Directory Backups

Mounting a local (permanently attached) hard drive or filesystem as a directory can be very useful for making fast data copies, but is not recommended for anything else. Its data is very likely to be lost if the server has a catastrophic event (fire/flood/earthquake etc.). The potential for either loss or accidental erasure during a disaster recovery is very high. Microlite never recommends the use of archive devices or media that cannot be taken off-site on a periodic basis.

In document User Guide - Release (Page 145-152)