Arkeia Network Backup Version 9.1 Quick Start Guide - Deutsch
From Arkeia Documentation
Introduction to Network Backup Version 9.1
Arkeia Network Backup version 9.1 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, Two Phase Backups and the Arkeia Environment Dashboard.
Arkeia Dashboard
The Arkeia Network Backup Dashboard provides a high level overview of the backup servers environment and allows for customization of objects and views to meet the Backup Administrators specific needs.
- Refer to the English Documentation Dashboard Guide for more details.
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
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 on a "DEDICATED Backup Server" for data deduplication operations.
- (64 Bit) Linux Operating System
- 4 (64 bit) CPU Cores
- 16 GB of Available Memory
None 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 dedicated 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.
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
Shared Memory is automatically allocated by the Arkeia Data Deduplication engine and distributed evenly across dedupe block pools.
75% of free memory is allocated by default.
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
- Refer to the English Documentation How To: udev Persistent Device Paths for more details.
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 or configure your environment to allow TCP ports 617 and 1024 thru 1030.
- Refer to the English Documentation Arkeia Ports Guide for more details.
/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
- Refer to the English Documentation "Software Installation Guides" for tar.gz installations on Linux, Solaris and Unix.
Internet Browsers
Supported Browsers
Arkeia Network Backup v9.1 supports the following Internet Browsers.
- Firefox 3 and higher
- Internet Explorer 7
- Internet Explorer 8
- Internet Explorer 9
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 Arkeia default user "root" with no password.
Arkeia Dashboard
The Arkeia Network Backup Dashboard provides a high level overview of the existing state of a backup servers environment.
The Dashboard allows customization of objects and views to meet the Backup Administrators specific needs.
- Refer to the English Documentation Dashboard Guide for more details.
Arkeia Software Configuration
Help menus are provided throughout the Web Interface by clicking on 
at any menu screen.
Create A Savepack
A Savepack is a collection of the clients and or directory paths of data to be backed up.
IMPORTANT DATA 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 Savepack"
Enter "Null" for the name of the Savepack Set the Compression/Deduplication Type to "Deduplication at the target"
Click "Next"
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 "Next"
Make no modifications to the default Savepack Tree options at this screen
Click "Create"
View the created Savepack
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 Null Tapes and Null Tape Pool
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.
- Refer to the English Documentation Tape Media Guide for more details.
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 > Tape Storage > Tapes
Click "Add A Backup Tape"
Enter "Null-" for the name of the tape Select the Tape Type "NULL" from the drop down menu
Click on the "Show More Options" box to select it
Set the value "Number of Tapes" to "5" in the Create Multiple tapes section Leave the value "Starting Number" set to "0"
Click "Next"
Make no modifications to the default Tape Pool at this screen
Click "Validate"
View the Tape and Tape Pool created
Create Null Tape Drive and Null Tape Drivepack
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.
- Refer to the English Documentation Tape Drive Guide for more details.
A Tape 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 Drive"
Click the "Manual Creation" button
Enter "Null" for the name of the drive Select the Drive Type to "NULL" from the drop down menu Ensure the Media Server option is set to the hostname of the backup server Set the Rewind Device path to /dev/null
Click "Next"
Make no modifications to the default Tape Drive Drivepack at this screen
Click "Validate"
View the Tape Drive and Drivepack created
Start an Immediate Backup To Null Devices
Backup > When To Backup > Immediate Backup To Tape
Set the Savepack, Drivepack and Pool parameters using the drop down menu
Click "Start Backup"
Starting the backup job will default to viewing the Active backup job in the Active Jobs screen.
Monitor The Backup Job To Null Devices
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 Configuration
A 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.
A 1 TB Disk Storage License is included by default.
- Refer to the English Documentation Disk Storage Guide for more details.
A Disk Drivepack is a logical grouping of one or more physical 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 Storage"
Dedupe Enabled Disk Storage (default)
IMPORTANT NOTE
A Dedupe Disk Storage is configured by enabling the Dedupe Option. (Enabled = Default)
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.
Enter "Disk Storage 1" for the name of the Disk Storage Set the Capacity to the desired size (default = 1 TB) Set the Path to the desired location on disk such as "/vol0/diskstorage1"
Click "Next"
Make no modifications to the Disk Storage Drivepack at this screen
Click "Validate"
View the created None Deduplication Enabled Disk Storage
None Dedupe Disk Storage
IMPORTANT NOTE
A "non dedupe" enabled Disk Storage can be configured by enabling the Deduplication Option at a later time.
Once a Disk Storage Deduplication has been enabled, it CANNOT be disabled. The Disk Storage must be fully deleted and recreated to remove the Deduplication configuration.
Enter "Disk Storage 1" for the name of the Disk Storage Set the Capacity to the desired size (default = 1 TB) Set the Path to the desired location on disk such as "/vol0/diskstorage1"
Check the "Show More Options" Box
Un Check the "Enable Deduplication" Box (default = Checked) Leave all other options set to their defaults
Click "Next"
Make no modifications to the Disk Storage Drivepack at this screen
Click "Validate"
View the created None Deduplication Enabled Disk Storage
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
Set the Savepack and Disk Drivepack parameters using the drop down menu
Click "Start Backup"
Starting the backup job will default to viewing the Active backup job in the Active Jobs screen.
Stand-Alone Tape Drive Configuration
Create Tapes and Tape Pool
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.
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 > TapeStorage > Tapes
Click "Add A Backup Tape"
Enter "Backup Tape" for the name of the tape Select the Tape Type "LTO Ultrium 1600 GB" from the drop down menu or choose your appropriate tape type.
Click on the "Show More Options" box to select it
Set the value "Number of Tapes" to "5" in the Create Multiple tapes section Leave the value "Starting Number" set to "0"
Click "Next"
Select the "Add Tape(s) To A New Tape Pool" Option
Click "Validate"
View the Tape(s) and Tape Pool created
Create Tape Drive and Tape Drivepack
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.
- Refer to the English Documentation Tape Drive Guide for more details.
A Tape 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 Drive"
Automatic Creation (default)
The "Launch Detection" feature of the WebUI is capable of automatically detecting most Tape Drives.
If you tape Drive is not automatically detected, please use the "Manual Creation" option.
Enter "Tape Drive" for the name of the drive Ensure the Media Server option is set to the hostname of the backup server
Click the "Launch Detection" option next to the name of the Media Server
Select the detected tape drive
Click "Next"
Select the "Add A New Drivepack Option"
Click "Validate"
View the Tape Drive and Tape Drivepack created
Manual Creation
Click the "Manual Creation Option"
Enter "Tape Drive" for the name of the drive Select the Tape Type from the drop down menu Ensure the Media Server option is set to the hostname of the backup server Set the rewind device to "/dev/st0" which is normally the 1st tape drive on Linux
Click "Next"
Select the "Add A New Drivepack Option"
Click "Validate"
View the Tape Drive and Tape Drivepack created
Start an Immediate Backup To Drive
Backup > When To Backup > Immediate Backup To Tape
Set the Savepack, Drivepack and Pool parameters using the drop down menu
Click "Start Backup"
Starting the backup job will default to viewing the Active backup job in the Active Jobs screen.
Tape Library 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.
- 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.
Create A Tape Library
Auto Detect and Create
- Refer to the English Documentation Hardware Detection Guide for more information about the Auto Detection feature of Arkeia.
Manual Library Creation
Create The Library
Backup > Where To Backup > Tape Storage > Tape Libraries
Click "Add A Library"
Enter "Tape Library" for the name of the Tape Library Enter the Control Device of your tape library such as "/dev/sg1" Select the Media Server from the drop down menu (default is backup server) Select the Form Factor for your tape drive type such as "LTO" (the type of drive in your library) Enter the Number Of Slots supported by your Tape Library (the quantity of slots in your library) Enter the Number Of Tape Drives being used in your Tape Library (the quantity of tape drives in your library)
Click "Create"
View the created Tape Library
Verify Slot Inventory
After the Picker Arm has processed all tape slots and drives. Click the "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.
Click the "Slot Usage" Tab
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.
Attach the Tape Drive
Attaching the Tape Drive to the Tape Library logically associates the physical devices to allow control of these devices.
Click "Manage Drives"
Highlight Drive Bay 1 and Drive #1 (ex. Tape Drive)
Click "<<" to attach the drive to the library
Verify the Tape Drive is attached to the Tape Library
Setting Tapes
Setting the tapes in the library logically associates the physical tapes to the logical tapes created in Arkeia.
Click "Manage Slots"
Highlight the quantity of that slots that say "Unknown Tape" which corresponds to the number of tapes you wish to set
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 Tape Barcode 2 Standard Name of Your Tape Tape Barcode 3 Standard Name of Your Tape Tape Barcode 4 Standard Name of Your Tape Tape Barcode etc...
Start an Immediate Backup To Tape Library
Backup > When To Backup > Immediate Backup To Tape
Set the Savepack, Drivepack and Pool parameters using the drop down menu
Click "Start Backup"
Starting the backup job will default to viewing the Active backup job in the Active Jobs screen.
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.
Replicate > Where to Replicate > When to Replicate > Immediate Replicate > Tape Storage
Select a backup job to copy from the drown down list Select a Drivepack from the drop down list Select a tape pool from the drop down list Select a tape policy from the drop down list Set the retention policy for the job being copied to tape
Click "Start Tape Storage Replication"
The Tape Storage Replicaton job can be viewed in the Active Jobs screen.
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"
The Restore job can be viewed in the Active Jobs screen.
Restore Verification
Verify the success of the restore job in the Arkeia Restore Reports and the file system.
Restore Reports
Reports > Restore
Summary View
Click the "Word Document Icon"(Detailed View) next to the "Magnifying Glass" (Summary View) to see the restore job detailed information
Detailed View
Click the "Magnifying Glass" (Summary View) next to the "Word Document Icon"(Detailed 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 opt]# ls -la / |grep etc drwxr-xr-x 112 root root 12288 Jan 29 04:08 etc drwxr-xr-x 112 root root 12288 Jan 29 04:08 etc-TEST [root@backups opt]#
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.
