Arkeia Network Backup Version 9.0 Quick Start Guide - English
From Arkeia Documentation
Introduction to Network Backup Version 9.0
Arkeia Network Backup version 9.0 delivers features to shorten backup-windows, and to reduce storage and networking costs for protecting your data.
This major release employs patented Progressive Deduplication, Source and Target Side Data Deduplication, 256 AES Encryption and Two Phase Backups among other features.
Menu and Terminology Changes
The Arkeia Web User Interface and menu items and some terminology has changed in version 9.0.
The main changes are:
Data Deduplication
Progressive Deduplication is an improvement over first-generation deduplication technologies like fixed-block or variable-block deduplication. “Progressive Deduplication” is named for the second of the two underlying technologies used. First, a sliding-window is used to scan all possible blocks of a given size in a file, advancing one byte at a time. Second, progressive-matching uses a light-weight algorithm to identify those blocks that are probable matches to known blocks, followed by a heavy-weight algorithm which scrutinizes probable matches with a hashing algorithm to confirm the match.
Arkeia’s progressive-matching is ideal for source-side deployment, but administrators can specify that certain backups be deduplicated at the target (the media server) or not at all. For backups, source-side deduplication is preferable because the deduplication compresses data before it travels over the network, shortening backup windows.
Because the size of the deduplication block is set by the sliding window, and because this window can be adjusted, Arkeia uses different block sizes for files of different types. A text file, a database file, a virtual machine image, and an application file will be deduplicated with blocks of different sizes.
Arkeia’s deduplication is “in-line”, eliminating the overhead of moving the data more than once. In-line deduplication is a natural complement to source-side deduplication because the data are compressed before they leave the source computer to travel over the network.
- Read Arkeia's Data Deduplication FAQ
- Learn more about Arkeia's patented Progressive Data Deduplication technology
- Learn more about Source Side Data Deduplication
AES 256 Encryption
Client-side support of AES-256 encryption improves data privacy both while stored and while in transit over the network.
Deduplication is completed before data is encrypted
Two Phase Backup
Two-phase backups are ideal for environments with large numbers of small files, where the time to move the files is much less than the time required to update the catalog. The advantage of this approach is that the backup window can be reduced dramatically, being limited by the time to move the files over the network. However, it is not possible to restore files from the catalog until the index update is complete. The files are safe, but temporarily inaccessible.
- Please refer to the How To: Enable Two Phase Backups Guide for more information on how to implement this feature.
Pre-Installation Configuration
CPU and Memory
Data Dedupe Environments
Unlike a standard backup, Data Deduplication requires more memory and central processing power to obtain the best performance possible.
Arkeia recommends the following minimum hardware specifications for a data deduplication operations.
- (64 Bit) Linux Operating System
- 4 (64 bit) CPU Cores
- 16 GB of Available Memory
Source Side Dedupe clients require a minimum of 3 GB of memory for dedupe operations.
Clients with less memory must have their dedupe.prf file adjusted for the lower amount of memory.
Please refer to the How To: Data Dedupe With Small CPU And Memory Guide for more details how you can modify the dedupe engine for smaller CPU and Memory environments.
Non Data Dedupe Environments
The minimum server requirements are 512 MB Memory and a 1.0 GHz processor for non data deduplication environments
Although Arkeia can be hosted on the minimum hardware environment, the best performance will be obtained by deploying a backup server based on your total backup data size. The following descriptions are "suggested" comparable configurations for selective class backup environments that should provide the best performance.
The information below should be used as a basic guideline for backup server hardware.
Each backup environment is different. The type, structure, retention policy and overall backup policy should dictate the level of hardware required for your production environment. Your backup deployment may require more or less CPU, Memory and Disk Space so plan accordingly.
File Locking
"File Locking" is a mechanism that restricts access to a computer file by allowing only one user or process access at any specific time.
The UBP (unique block pool) is locked while the dedupe engine is running, which occurs during backups, replications and restore operations.
Arkeia uses the OS level file locking call which works only on block devices such as local or iSCSI mounts.
NFS (Networked File System) is currently not supported and should not be used to host the Block Pools.
IPC Parameters
Message Queues
Increase the IPC parameters of the Linux kernel as superuser.
su - # on traditional Linux distributions or sudo -s # on Debian/Ubuntu like distributions
vi /etc/sysctl.conf # Sets maximum number of message queues # to 200 (by default it is 16) kernel.msgmni = 200 # Sets maximum size of message queue to 65536 # (by default the size of the message queue is 16348 since the kernel 2.2.14) kernel.msgmnb = 65536
Activate the changes using the following commands.
/sbin/sysctl -p /usr/bin/ipcs -l
Shared Memory
The SHMMAX parameter is used to define the maximum size (in bytes) for a shared memory segment.
If SHMMAX is set incorrectly (too low), the backup and data dedupe process will fail with the message "cannot allocate memory".
You can determine the value of SHMMAX by performing the following command:
cat /proc/sys/kernel/shmmax 33554432
As you can see from the output above, the default value for SHMMAX is 32MB on some distribution.
This is often too small to perform data deduplication backups.
Arkeia suggest to set shmmax to 4 GB mimimum for your initial backup testing.
If 4 GB is not sufficient for your environment, then increase the value as needed for best performance.
Temporary Setting
Use the "echo" command to temporarily increase the value of shmmax.
The setting will be replaced by the default if the system is rebooted or powered off/on.
echo 4294967295 > /proc/sys/kernel/shmmax
Permanent Setting
Adding the value to the sysctl.conf file will permanently alter the setting.
vi /etc/sysctl.conf
# Controls the maximum shared segment size, in bytes kernel.shmmax = 4294967295
Activate the changes using the following commands.
/sbin/sysctl -p /usr/bin/ipcs -l
Tape Device Validation
Kernel SCSI Modules
st and sg
Check dmesg to determine if "scsi tape (st)" and "generic scsi" (sg type 8) modules are loaded and associated to your tape backup hardware.
Tape Drive(s) sg (generic scsi) path cannot be used to access the tape drive for backup operations. Arkeia must use the st (scsi tape) path. dmesg | grep tape st 6:0:2:0: Attached scsi tape st0 st 6:0:3:0: Attached scsi tape st1
Tape Library type 8 devices are library robotics and control arms. dmesg | grep "type 8" sg 6:0:1:0: Attached scsi generic sg1 type 8
udev Persistent Device Paths
Persistent device paths can also be used within the Arkeia environment when multiple tape drives and or libraries are used.
The "nst" (none rewind device) paths are not supported.
ls -la /dev/tape/by-id/* lrwxrwxrwx 1 root root 10 Mar 1 11:05 /dev/tape/by-id/scsi-DELL_TL4000_000002305301 -> ../../sg1 lrwxrwxrwx 1 root root 10 Feb 28 07:02 /dev/tape/by-id/scsi-3500e09e00012378f-nst -> ../../nst0 lrwxrwxrwx 1 root root 9 Feb 28 07:02 /dev/tape/by-id/scsi-3500e09e00012378f-st -> ../../st0 lrwxrwxrwx 1 root root 10 Feb 28 07:02 /dev/tape/by-id/scsi-3500e09e00012378e-nst -> ../../nst1 lrwxrwxrwx 1 root root 9 Feb 28 07:02 /dev/tape/by-id/scsi-3500e09e00012378e-st -> ../../st1
- Read the How To: udev Persistent Device Paths KB article, if you do not have persistent device paths.
Tape Drive Validation
Use the standard Linux "mt" and "tar" commands to validate the tape drive before usage.
Insert a Tape into the drive.
Issue the following "mt" command to verify the devices is online:
mt -f /dev/st0 status or mt -f /dev/tape/by-id/scsi-3500e09e00012378f-st status
Issue the following "tar -cvf" command to write to the media:
tar -cvf /dev/st0 /etc or tar -cvf /dev/tape/by-id/scsi-3500e09e00012378f-st /etc
Issue the following "tar -tvf" command to read from the media:
tar -tvf /dev/st0 or tar -tvf /dev/tape/by-id/scsi-3500e09e00012378f-st
Library Validation
Ensure the library is in Random or SCSI Mode and not Sequential Mode at the library control screen.
Use the standard "mtx" command to validate the library before usage.
/usr/sbin/mtx -f /dev/sg1 status /usr/sbin/mtx -f /dev/sg1 inventory or /usr/sbin/mtx -f /dev/tape/by-id/scsi-DELL_TL4000_000002305301 status /usr/sbin/mtx -f /dev/tape/by-id/scsi-DELL_TL4000_000002305301 inventory
Host Name Verification
Verify the hostname on the backup server.
/bin/hostname backups.us.arkeia.com
Ensure the /etc/hosts file is set to the proper syntax with the hostname of the backup server as a separate entry and not on the same line as the localhost address.
The ipv4 address must be placed "ABOVE or BEFORE" the ipv6 address.
vi /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.5.211 backups.us.arkeia.com backups
Firewall and SE Linux
If your system does not have "iptables" (Firewall) or "setenforce" (SELinux) installed, the following commands will result in the message (No Such File or Directory) being returned by the system.
Disable the Linux Firewall before installing Arkeia.
/etc/init.d/iptables stop
Set SELinux to passive mode before installing Arkeia.
/usr/sbin/setenforce 0
Arkeia Software Installation
Go to Arkeia Downloads and download the Arkeia packages
- arkeia_master (Backup Server)
- arkeia_arkwui (Web User Interface)
Install Arkeia as super user (root), su or via sudo.
.rpm Installation
rpm -Uvh arkeia.x.x.x_master_linux.x.rpm
rpm -Uvh arkeia.x.x.x_arkwui_linux.x.rpm
.deb Installation
sudo dpkg -i arkeia.x.x.x_master_linux.x.deb
sudo dpkg -i arkeia.x.x.x_arkwui_linux.x.deb
- Please refer to other "Software Installation Guides" for tar.gz installations on Linux, Solaris and Unix.
Internet Browsers
Supported Browsers
Arkeia Network Backup supports the following Internet Browsers.
- Firefox 3.x, 4, 5 and higher
- Internet Explorer 7, 8 and 9
NOTE: Firefox 4, 5, 6 and higher, Internet Explorer 9 are supported on version 9.0.3 and higher.
Unsupported Browsers
The following browsers are not supported.
- Firefox 2
- Safari
- Opera
- Chrome
- all others
Access the Web Interface
Open your browser to access the Arkeia Network Backup Web Interface on port 20617 by hostname, IP or localhost.
The default user login is "root" with no password.
http://localhost:20617 http://backups.us.arkeia.com:20617 Your machine's Hostname may be different http://192.168.5.211:20617 Your machine's IP address may be different
Login using the default user "root" with no password.
Arkeia Software Configuration
Help menus are provided throughout the Web Interface by clicking on 
at any menu screen.
Software Validation (Null Media Backup)
Backups to Null Devices are only used for testing and generating benchmarks as the data is written to the Linux path of /dev/null and are not restorable.
Backups to Null do not update the Arkeia Index by default.
Create a Savepack
A Savepack is a collection of the clients and or directory paths of data to be backed up.
Set the Compression/Deduplication Type to "Deduplication at the target".
IMPORTANT DEDUPLICATION NOTE:
The Savepack Parameter "Compression/Deduplication Type" determines local compression, data dedupe at the source or the target.
Setting "Deduplication at the target" will dedupe data when written to a Data Deduplication enabled Disk Storage.
Data Deduplication will not occur when backing up to Null Media or a non Dedupe enabled Disk Storage, however the backup will be done using Arkeia Client Side Compression.
- Refer to the English Documentation Savepack Guide for more details.
Backup > What To Backup
Click "Add a new Savepack"
Name = Null Compression/Deduplication Type = Deduplication at the target
Click "Create"
Populate the Savepack
Backup > What To Backup
Click "Browse Trees for Null"
Click on the backup servers hostname to expand the browser until you reach the backup servers !file path.
Check the box next to the !file object to backup the entire file system.
Click "Update"
Create a Null Drive
Arkeia uses Tape Drives to read and write backup data.
There must be a logical Arkeia Tape Drive for every physical tape drive attached to your backup or media server.
A Null Drive sends data to /dev/null for testing purposes.
Data written to /dev/null does not update the Arkeia index and cannot be restored.
Backup > Where To Backup > Tape Storage > Tape Drives
Click "Manage Drives"
Click "Add a Tape Drive"
Name = Null Type = NULL (select from drop down list) Media Server = backups.us.arkeia.com (default is backup server) Rewind Device = /dev/null
Click "Create"
Create a Null Drivepack
A Drivepack is a logical grouping of one or more physical Tape Drive(s) or Disk Storage and defines the destination media for the backup job data.
- Refer to the English Documentation Drivepack Guide for more details.
Backup > Where To Backup > Backup To Tape > Tape Storage
Click "Tape Drives"
Click "Add a Tape Drivepack"
Name = Null Number of Drives = All
Select the "NULL" Tape Drive
Click "Create"
Create a Null Tape Pool
Tape Pools are groups of tapes that are created to perform a well-defined backup/restore policy.
- Refer to the English Documentation Tape Pool Guide for more details.
Backup > Where To Backup > Backup To Tape > Tapes
Click "Add A Pool"
Name = Null
Click "Create"
Create Null Tapes
Tapes are created in Arkeia to link the logical names used by tape pools and the physical tapes in the devices. A tape label and unique tape ID is written at the beginning of the tape to allow the identification and management of the tape by Arkeia. Null tapes are only used for testing and are not restorable.
Using the First # and Last # feature will create X number of tapes in sequential order. (ex. Null-1 to Null-5)
Backup > Where To Backup > TapeStorage > Tapes
Click "Create Tapes"
Backup or Cleaning Tape = Backup Tape Tape Name = Null- Type = NULL (select from drop down list) Pool = Null First# = 1 Last# = 5
Click "Create"
Start an Immediate Backup To Tape
Backup > When To Backup > Immediate Backup To Tape
Savepack = Null Drivepack = Null Pool = Null
Click "Start Backup"
Monitor the Backup Job
Starting the job will open the Running Jobs screen but you can also monitor the backup job by navigating the "Monitor" Menu selection.
- Refer to the English Documentation Job Monitoring Screen for more details.
Monitor > Active Jobs
Select the active job
Click "Monitor Job"
Disk Storage Backup Validation
Disk Storage is a logical Arkeia object representing on-disk storage space dedicated to backups.
This object must be used as a target to disk-to-disk backups which can be none dedupe or dedupe enabled.
- Refer to the English Documentation Disk Storage Guide for more details.
None Dedupe Disk Storage
Create None Dedupe Disk Storage
Backup > Where To Backup > Disk Storage
Click "Manage Disk Storage"
Click "Add a Disk Storage"
Name = Disk Storage 1 Capacity = 500 GB (1 TB license included) Media Server = backups.us.arkeia.com (backup server is default) Path = /opt/disk-storage-1 Concurrent Access = 4 (default = 4) Automatic Tape Storage Replication = NO Enable Deduplication = UNCHECKED
Click "Create"
IMPORTANT NOTE
A "non dedupe" enabled Disk Storage can be configured by enabling the Dedupe Option.
Once a Disk Storage Dedupe has been enabled, it CANNOT be disabled. The Disk Storage must be fully deleted and recreated to remove the dedupe configuration.
Create a Disk Storage Drivepack
A Drivepack is a logical grouping of one or more physical Tape Drive(s) or Disk Storage and defines the destination media for the backup job data.
- Refer to the English Documentation Drivepack Guide for more details.
Backup > Where To Backup > Disk Storage
Click "Add a Disk Drivepack"
Name = Disk Storage 1
From the “List of Disk Storage”, select Disk Storage 1
Click "Create"
Dedupe Enabled Disk Storage
Create Dedupe Enabled Disk Storage
Backup > Where To Backup > Disk Storage
Click "Manage Disk Storage"
Click "Add a Disk Storage"
Name = Dedupe Disk Storage Capacity = 500 GB (1 TB license included) Media Server = backups.us.arkeia.com (backup server is default) Path = /opt/dedupe-disk-storage Concurrent Access = 4 (default = 4) Automatic Tape Storage Replication = NO Enable Deduplication = CHECKED Deduplication Path = Same as Disk Storage (location of dedupe block pools such as /opt/dedupe-disk-storage/dedupe)
IMPORTANT NOTE
A Deupe Disk Storage is configured by enabling the Dedupe Option.
Once a Disk Storage Dedupe has been enabled, it CANNOT be disabled. The Disk Storage must be fully deleted and recreated to remove the dedupe configuration.
Click "Create"
Create a Disk Storage Drivepack
A Drivepack is a logical grouping of one or more physical Tape Drive(s) or Disk Storage and defines the destination media for the backup job data.
- Refer to the English Documentation Drivepack Guide for more details.
Backup > Where To Backup > Disk Storage
Click "Add a Disk Drivepack"
Name = Dedupe Disk Storage
From the “List of Disk Storage”, select Dedupe Disk Storage
Click "Create"
Start an Immediate Backup To Disk
Dedupe Backup
The Null Savepack was created with the Compression/Deduplication Type set to "Deduplication at the target".
If the backup is done to the dedupe enabled Disk Storage, then data will be deduplicated.
None Dedupe Backup
The Null Savepack was created with the Compression/Deduplication Type set to "Deduplication at the target".
If the backup is done to the none dedupe enabled Disk Storage, then data will not be deduplicated.
Backup > When To Backup > Immediate Backup To Disk
Save Pack = Null Drive Pack = Dedupe Disk Storage
Click "Start Backup"
Monitor the Backup Job
Starting the job will open the Running Jobs screen but you can also monitor the backup job by navigating the "Monitor" Menu selection.
- Refer to the English Documentation Job Monitoring Screen for more details.
Monitor > Active Jobs
Select the active job
Click "Monitor Job"
Stand-Alone Tape Drive Configuration
Arkeia uses Tape Drives to read and write backup data.
There must be a logical Arkeia Tape Drive for every physical tape drive attached to your backup or media server.
Manual Drive Creation
Backup > Where To Backup > TapeStorage > Tape Drives
Click "Manage Drives"
Click "Add A Tape Drive"
Name = Tape Drive Type = LTO4 (select from drop down list) Media Server = backups.us.arkeia.com (default is the backup server) Rewind Device = /dev/st0
Click "Create"
Auto Detect and Create
- Refer to the English Documentation Hardware Detection Guide for more information about the Auto Detection feature of Arkeia.
Create a Drivepack
A Drivepack is a logical grouping of one or more physical Tape Drive(s) or Disk Storage and defines the destination media for the backup job data.
- Refer to the English Documentation Drivepack Guide for more details.
Backup > Where To Backup > Tape Storage > Tape Drives
Click "Add a Tape Drivepack"
Name = Tape Drive Number of Drives = All
Select the user defined tape drive (ex. Tape Drive)
Click "Create"
Create a Tape Pool
Tape pools are groups of tapes that are created to perform a well-defined backup/restore policy.
Backup > Where To Backup > Tape Storage > Tapes
Click "Add A Pool"
Name = Backup Tapes
Click "Create"
Create Tapes
Tapes are created in Arkeia to link the logical names used by tape pools and the physical tapes in the devices.
A tape label and unique tape ID is written at the beginning of the tape to allow the identification and management of the tape by Arkeia.
- Refer to the English Documentation Tape Media Guide for more details on Tape Creation and How To Create Tapes using bar-coded names.
Using the First # and Last # feature will create X number of tapes in sequential order. (ex. LTO4-1 to LTO4-5)
Backup > Where To Backup > Tape Storage > Tapes
Click "Create Tape"
Backup or Cleaning Tape = Backup Tape Tape Name = LTO4- Type = LTO Ultrium 800GB (select from drop down list) Pool = Backup Tapes First# = 1 Last# = 5 (or the number of tapes you have)
Click "Create"
Library and Tape Drive Configuration
Arkeia uses Tape Libraries to to automate the backup process. There must be a logical Arkeia Tape Library for every physical Tape Library attached to your backup or media server.
Create a Tape Library
- Refer to the English Documentation Tape Library Guide for more details on how to create and manage a tape libraries.
- Refer to the English Documentation Form Factor for your tape drive type.
Manual Library Creation
Backup > Where To Backup > Tape Storage > Tape Libraries
Click "Add a Library"
Name = Tape Library Control Device = /dev/sg1 Media Server = backups.us.arkeia.com (default is backup server) Form Factor = LTO (the type of drive in your library) Number of Slots = 10 (the quantity of slots in your library) Number of Drives = 1 (the quantity of tape drives in your library)
Click "Create"
Auto Detect and Create
- Refer to the English Documentation Hardware Detection Guide for more information about the Auto Detection feature of Arkeia.
Attach the Tape Drive
Attaching the tape drive created in Arkeia to the library created in Arkeia logically associates the physical devices to allow control of these devices.
Backup > Where To Backup > Tape Storage > Tape Libraries
Click "Manage Drives"
Highlight Drive Bay 1 and Drive #1 (ex. Tape Drive)
Click "<<" to attach the drive to the library
Repeat for all tape drives as required
Library Validation
Backup > Where To Backup > TapeStorage > Tape Libraries
Click "View Slots"
After the Picker Arm has processed all tape slots and drives. Click “Slot Usage” and you should see "No Tape" or “Unknown Tape” for all slots listed.
If you see "Unknown Contents" then the Library is not configured properly or the Inventory has not completed.
GOOD INVENTORY 1 Standard No Tape 2 Standard No Tape 3 Standard Unknown Tape 4 Standard Unknown Tape
BAD INVENTORY 1 Standard Unknown Contents 2 Standard Unknown Contents 3 Standard Unknown Contents 4 Standard Unknown Contents
NO BAR CODES:
When the Library does not use a bar code, each tape within the library slots must be loaded into the drive and placed back into the slot in-order for the inventory to be taken.
BAR CODES:
When bar codes are used, the Inventory is done in a matter of 1 - 2 minutes using the bar code scanner on the library mechanism.
Setting Tapes
Setting the tapes in the library logically associates the physical tapes to the logical tapes created in Arkeia.
Backup > Where To Backup > Tape Storage > Tape Libraries
Click "Manage Slots"
Highlight one or all of the slots that say "Unknown Tape"
Select the tapes to be set
Click "<<" to assign tapes to the slots
After setting tapes, you should now see...
1 Standard Name of Your Tape 2 Standard Name of Your Tape 3 Standard Name of Your Tape 4 Standard Name of Your Tape
LTO3/4/5 Tape Labeling
LTO3, LTO4 and LTO5 Tapes should be pre-labeled before use because Arkeia sets the tape and buffer size
different from the manufacturers default specifications.
Arkeia suggests to label 1 to 4 tapes
at a time for the best results.
Backup > Where To Backup > Tape Storage > Tape Libraries
Click "Manage Slots"
Select the tape(s) to labeled
Click "Write Label"
Monitor the Messages Screen for the label write process
Tape Backup Validation
Start an Immediate Backup To Tape
Backup > When To Backup > Immediate Backup To Tape
Savepack = Null Drivepack = Tape Drive Pool = Backup Tapes
Click "Start Backup"
Monitor the Backup Job
Starting the job will open the Running Jobs screen but you can also monitor the backup job by navigating the "Monitor" Menu selection.
- Refer to the English Documentation Job Monitoring Screen for more details.
Monitor > Active Jobs > Monitor Job
Select the active job
Click "Monitor Job"
Tape Storage Replication
An Immediate Tape Storage Replication job replicates a backup set stored on Disk Storage in a media server's HDD, to physical tapes written in a tape drive attached to the same media server.
Start an Immediate Tape Storage Replication
Replicate > When To Replicate > Immediate Replication > TapeStorage
Backup to copy = select a backup job to copy from the drown down list Drivepack = select a Drivepack from the drop down list Pool = select a tape pool from the drop down list Tape policy = select a tape policy from the drop down list Valid for = set the retention policy for the job being copied to tape Reporting = enable or disable email notification
Click "Start TapeStorage Replication"
Restoration Validation
Arkeia Software suggest to test both a restoration from Tape and Disk Storage if both media's are deployed in your environment.
The purpose of this Quick Start Guide is to provide a basic restore for testing purposes, please review the Restoration User Guide for more details.
- Refer to the English Documentation Restoration Guide for more details.
Data Selection
Navigate to the Restoration Screen.
Restore
Select "Restore files, system info, databases and applications"
Click "Next"
Use the From: and To: drop down menu's to select the Savepack and backup job to restore from.
Select the file or directory that you wish to restore for your testing.
Redirection Restore
A redirected restore is used to prevent overwriting exiting or data that is currently in use.
Click the "Redirection Tab"
Source and Destination Paths
Use the drop down menu to populate the Source and Destination Path
Leave the source path as is and modify the destination path
Start a Restore
Click "Start Restoration"
Restore Verification
Verify the success of the restore job in the Arkeia Restore Reports and the file system.
Restore Reports
Reports > Restore
Click the "Word Document Icon"(Detailed View) next to the "Magnifying Glass" (Summary View to see the restore job detailed information
File System
Check the local file system by logging into the backup server and execute the "ls -la / | grep etc" command listed below.
[root@backups ]# ls -la / | grep etc drwxr-xr-x 108 root root 12288 Mar 19 08:57 etc drwxr-xr-x 2 root root 4096 Mar 19 08:57 etc-TEST
Adding A Client
- Refer to English Documentation How To Add A Client to start registering clients to the backup server.
Scheduled Backup Jobs
- Refer to the English Documentation Scheduled Job Guide on how to configure Scheduled backup jobs.
