To have BackupEDGE backup to an NFS Resource you must:
1 Configure an AF Resource to mount and unmount the NFS Server on demand.
2 Configure an FSP Resource to read and write to a particular directory on the NFS Server and associate it with the proper AF Resource for mounting / unmounting.
3 Initialize the FSP Resource.
4 Select the FSP Resource from EDGEMENU or within a Schedule.
Initializing the FSP Backup Resource does NOT erase any data. If there are no current files in the backup directory, BackupEDGE will create a control file (named CTL) indicating that it is ready
to accept BackupEDGE archives. If BackupEDGE detects a control file, it will scan the directory
+ Edit Backup Schedule ---+ | Schedule Name: simple_job | | Time: [23:00 ] (14:58:46) Enabled: [X] | | Sequence: myserver.microlite.com:esequence/onsite | | Backup Domain: system | | Primary Resource: [Change] myserver.microlite.com:fsp!fsp0 | | | | +---+ January 2015 | | | Every Sunday of the week (None) | Su Mo Tu We Th Fr Sa | | | Every Monday of the week Master | M M 3 | | | Every Tuesday of the week Master | 4 M M M M M 10 | | | Every Wednesday of the week Master | 11 M M M M M 17 | | | Every Thursday of the week Master | 18 M M M M M 24 | | | Every Friday of the week Master | 25 M M M M M 31 | | | Every Saturday of the week (None) | | | +---+ | | | | Notify / Advanced: [Change] [Reset Dates] | | Mail Summary To: root Print Summary To: NONE | | Mail Failures To: NONE Print Failures To: NONE | |[Save] [Cancel]| +---+
for any current archives and re-build its index of available archives and their sizes. FSP Backups cannot commence until the FSP Resource has been initialized one time.
Preparing the NFS Server
NFS Servers generally have permissions setting that must be configured to allow other servers to
attach to them. This is called “exporting” a file system or directory. This is usually done by changing the exports file via GUI or from the command line.
Setting Up an Attached Filesystem Resources for NFS
The AF (Attached Filesystem) Resource is a special Resource handling the remote NFS Server. It is responsible for management and concurrence. It knows how to mount and unmount it, etc. and understands when more than one local schedule is accessing the remote server. A backup cannot be written directly to the AF Resource.
Setting up the AF Resource requires using edgemenu:Admin->Define Resources. Select
‘[NEW]’, then select ‘Attached Filesystem (AF)’. Change the resource name to something
suitable if desired. (the default is ‘af0’ and is fine).
Unedited AF Resource.
Usually, the only fields you must modify for NFS mounting are the Mount Device Node, the Mount Command, and the Exclude Node. The other fields, Mount Dir and Unmount Command,
will work without modification. The default mount directory is in a BackupEDGE directory that gets automatically excluded from backups, and should not be changed.
The Mount Device Node is the directory you’ve created on the remote server as the root
directory of all backups, such as ‘remote_server:/backupedge’. You may use the format IP_address:/mountpoint or hostname:/mountpoint as desired. It may be desirable to use an
IP address to ensure valid connections even if name services aren’t working.
The Exclude Node is the device node that will be excluded by RecoverEDGE during disk
preparation for disaster recovery. Please use “/dev/null” in this field.
The Mount Command must be modified for the particular NFS mount command for the operating
system you are using. Here are some examples...
NOTE: Never place any other (non-BackupEDGE-created) files in the BackupEDGE directory on the FSP Resource. Never manually remove any BackupEDGE files. The only way to
manipulate these files other than from within EDGEMENU without corrupting the control file database is by using the edge.segadm command. See “EDGE.SEGADM” on page 317 for more
information on using this program.
+ BackupEDGE Resource Information ---+ ¦- General Resource Information ---¦ ¦Resource Type Attached Filesystem ¦ ¦Resource Name [af0 ] Change as appropriate ¦ ¦Description [Attached Filesystem Resource] ¦ ¦Changer Assoc [Standalone Device] ¦ ¦Interface [Other ] ¦ ¦ ¦ ¦- Attached Filesystem Information ---¦ ¦Mount Dir [/usr/lib/edge/system/mnt/af0 ] ¦ ¦Mount Device Node [/dev/null ] ¦ ¦Mount Command [/etc/mount %m %M ] ¦ ¦Unmount Command [/etc/umount %M ] ¦ ¦Exclude Node [ ] ¦ ¦ ¦ ¦[Next] [Prev] [Cancel]¦ +---+
NFS Mount Commands for different Operating Systems
Linux
/etc/mount %m $M -o nolock
Xinuos / SCO OpenServer 5
/etc/mount -f NFS %m $M
Xinuos / SCO OpenServer 6
/etc/mount -f nfs -o vers=2 %m $M
Xinuos / SCO UnixWare 7.1.4
/etc/mount -f nfs -o vers=2 %m $M
The Exclude Node is the device node that will be excluded by RecoverEDGE during disk
preparation for disaster recovery. Please use “/dev/null” in this field.
Completed AF Resource Example (Linux).
Press [Next] to save the AF resource.
Setting Up a FileSystem Partition Resource for NFS
After you have saved the AF resource, you must create one or more Filesystem Partition (FSP) resources to write to it. Essentially these are simply directories created under the master mount point defined by the AF Resource.
Setting up an FSP resource is very simple. Use edgemenu:Admin->Define Resources to create a
Resource. Select ‘[NEW]’ and then select Directoy (fsp). Change the resource name to
something suitable if desired. (the default is ‘fsp0’ and is fine).
All of the fields in the “General Resource Information” section of this form have excellent
defaults except “AF Association”. Press [Enter] on this field and select the AF Resource that + BackupEDGE Resource Information ---+ ¦- General Resource Information ---¦ ¦Resource Type Attached Filesystem ¦ ¦Resource Name [af0 ] Change as appropriate ¦ ¦Description [Attached Filesystem Resource] ¦ ¦Changer Assoc [Standalone Device] ¦ ¦Interface [Other ] ¦ ¦ ¦ ¦- Attached Filesystem Information ---¦ ¦Mount Dir [/usr/lib/edge/system/mnt/af0 ] ¦ ¦Mount Device Node [192.168.100.114:/backupedge ] ¦ ¦Mount Command [/etc/mount %m %M -o nolock ] ¦ ¦Unmount Command [/etc/umount %M ] ¦ ¦Exclude Node [/dev/null ] ¦ ¦ ¦ ¦[Next] [Prev] [Cancel]¦ +---+
NOTE: OpenServer 6 and UnixWare 7 NFS Resources are not compatible with RecoverEDGE. You must use another Resource type, such as FTP/FTPS backups, to be able to perform remote backups with bare metal recovery on these operating systems.
will be handling the mounting and un-mounting of the filesystem. This tells BackupEDGE to make sure that the remote filesystem is mounted before trying to access the FSP.
‘Dir Suffix’ is the subdirectory under the remote mount point defined in the AF Resource
where the backups will be saved. This value can be altered to reflect the host name or schedule name of the server that is being backed up if desired.
‘Segment Size’, controls the maximum file size that BackupEDGE will create. The default is
slightly less than 1GB. Note that this does not limit the maximum archive size; BackupEDGE will automatically split the archive up into multiple files (segments) if needed. Generally, the user will not know (or care) about this, as it will be handled for you automatically. The
‘Segment Size’ field does not need to be altered in most cases.
‘Lazy Reclmation’ controls the behavior of space reclamation (deleting archives) on the FSP
media. See “Space Reclamation” on page 153 for additional information. The default behaviour is
Enabled.
Do not confuse ‘Segment Size’ with ‘Quota’. ‘Quota’ limits the total space consumed by all BackupEDGE archives on this resource. If the ‘Quota’ is 100GB, then no more than 100GB will be
written by BackupEDGE to this FSP until something is erased, or a new medium is loaded. The [S]oftware compression level from 1 to 9, or choose [N]one for no compression. Do not attempt to set compression to [H]ardware.
Initialize the FSP Resource
When you press [Next] to save the FSP Resource, you will be asked if you want to ‘Initialize’ the Resource. You must let BackupEDGE initialize the Resource before use. This mounts the remote
filesystem, creates the subdirectory and adds a control file named CTL in the destination
directory. To initialize at a later time, use edgemenu:Admin->Initialize Medium. while the Primary Resource is set to the correct FSP. Note that initializing the Resource will not erase
any existing backups. If existing backups exits, the CTL file, which contains information about the
individual archive segments, will be re-calculated.
9.7 - Backup Granularity
Be creative. Remote backups to NFS Servers with a lot of space provide the opportunity to increase backup frequency. One possible use is doing Master Backups each night, and
Differential Backups at midday.
+ BackupEDGE Resource Information ---+ ¦- General Resource Information ---¦ ¦Resource Type FS Partition ¦ ¦Resource Name [fsp0 ] Change as appropriate ¦ ¦Description [Directory Resource ] ¦ ¦AF Association [myserver:af0] ¦ ¦Interface [Other ] ¦ ¦ ¦ ¦- FS Partition Information ---¦ ¦Dir Suffix [/myserver ] ¦ ¦Segment Size (K) [1048544 ] [X] Lazy Reclamation ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦ ¦- Default Backup Properties ---¦ ¦Quota [120G ] [S] Compression Level [5] ¦ ¦Edge Block Size [64 ] [Y] Double Buffering ¦ ¦[Next] [Prev] [Cancel]¦ +---+
NOTE: BackupEDGE handles concurrent access multiple FSPs that share one AF correctly.
As an example, the “Sample NFS Backup Schedule” on page 97 will perform a nightly backup of the default Domain (system) through the default Sequence (onsite). Enable the advanced
scheduler, then create a new Schedule called midday_backups. When prompted, have the new Schedule use the same Domain and Sequence as the default Schedule. The user may also have to
choose whether or not to include a MySQL backup. Set the time to noon or so.
When completed, there will be a very fast midday backup and the reliability of the data will be increased.
Midday Backup Example
This will create 5 separate Differential Backups. If there is only a need to save the latest one, simply set the Retention Time to [1 Days] in the Notify / Advanced screen. This would
allow at least one Differential Backup to remain current at all times. Expired ones would be erased only if the Scheduler needs to reclaim the space.
The scheduler provides great flexibility. Extending the above example, it is possible to create hourly Differential Backups or Incremental Backups every day, providing an even greater safety margin by increasing backup frequency.
Deleting archives manually is discussed in “Deleting Backups” on page 246.
9.8 - RecoverEDGE Reminders
After adding a new Resource to BackupEDGE and creating at least one successful backup, always remember to re-create your RecoverEDGE media and / or images so that they will understand how to use the Resource. Test them to make sure you can read from the Resource if necessary.
To boot RecoverEDGE media and initialize it at a different IP address, for testing or cloning, remember to make sure that the NFS Server’s exports file has had the new IP address added. Otherwise you won’t be able to mount the remote server from the new IP address.
+ Edit Backup Schedule ---+ | Schedule Name: [midday_backup] | | Time: [12:01 ] (14:28:24) Enabled: [X] | | Sequence: [Change] myserver.microlite.com:esequence/onsite | | Backup Domain: [Change] system | | Primary Resource: [Change] myserver.microlite.com:fsp!fsp0 | | | | +---+ January 2015 | | | Every Sunday of the week (None) | Su Mo Tu We Th Fr Sa | | | Every Monday of the week Differ | D D 3 | | | Every Tuesday of the week Differ | 4 D D D D D 10 | | | Every Wednesday of the week Differ | 11 D D D D D 17 | | | Every Thursday of the week Differ | 18 D D D D D 24 | | | Every Friday of the week Differ | 25 D D D D D 31 | | | Every Saturday of the week (None) | | | +---+ | | | | Notify / Advanced: [Change] [Reset Dates] | | Mail Summary To: root Print Summary To: NONE | | Mail Failures To: NONE Print Failures To: NONE | |[Next] [Back To Select] [Cancel]| +---+ |+Local Machine: myserver.microlite.com Administering: myserver.microlite.com+|
NOTE: OpenServer 6 and UnixWare 7 NFS Resources are NOT compatible with RecoverEDGE. A different Resource type must be used, such as FTP/FTPS Backups, to be able to perform remote backups with bare metal recovery on these operating systems.
s - Linux
10 - Configuring CIFS (SMB) Backups - Linux
10.1 - General Concepts
CIFS Backups are backups where the storage Resource is a remotely mounted server or NAS using the Common Internet FileSystem (CIFS). CIFS has in the past been known as SMB or Samba. CIFS Backups are similar to D2D Backups, except that the mount command used mounts a directory on a CIFS Server instead of a filesystem on a local hard drive. Two Resources combine to make CIFS Backups function:
• FSP Resource, or FileSystem Partition Resource, defines and controls the directory on remote 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 remote filesystem containing the FSP Resource. No other user or process should mount and unmount the remote filesystem.
10.2 - Multiple Archives Per Medium
BackupEDGE supports performing multiple backups using CIFS Backups. The quota for CIFS Backups is defined by the user during setup. This is the general behaviour: