White Paper (English)

Backup iFolder on SLES 10 SP1

Gracon Services Inc. — Wed, 25 Feb 2009 18:11:12 -0700

Backup iFolder on SLES 10 SP1

Contents:

About this document
Requirements
Install/Upgrade
Configuration
Additional Resources

About this document

This guide explains the process of implementing Novell iFolder backup support in Sesam. This scenario applies to Sesam backup client for iFolder running on Linux and Sesam server running on Linux. Instructions for the installation and/or upgrade of Sesam server/client are provided using command line instructions. Instructions for the command line should be carried out using “root” user. All operating systems should already be installed, registered, and updated. Sesam server should already be installed and configured on SuSE Linux Enterprise Server 10 to use the backup equipment. iFolder server should already be installed on a SuSE Linux Enterprise Server 10 with Open Enterprise Server 2 system.

Requirements

iFolder backup client:

This is for the computer with the iFolder installation that you would like to back up. The following packages are required on this computer:

SuSE Linux Enterprise Server 10 (SLES10) Service Pack 1 with Open Enterprise Server 2 (OES2)

Available for download at: http://download.novell.com/index.jsp

SEP Sesam version 3.4.1.52 client

Available for download at: http://download.sep.de/linux/SuSE/

sesam_cli-3.4.1-25.sles10.i586.rpm (32 bit client)

sesam_cli-3.4.1-52.sles10.x86_64.rpm (64 bit client)

Novell iFolder 3.6.0.7263.1-2 server

Installed with Novell Open Enterprise Server (OES2).

See http://www.novell.com/documentation/ifolder3/ for help with iFolder installation and configuration.

Sesam backup server:

This is the computer which is running the Sesam backup server software.

SuSE Linux Enterprise Server 10 (SLES10) Service Pack 1

Available for download at: http://download.novell.com/index.jsp

SEP sesam version 3.4.1.52

Available for download at: http://download.sep.de/linux/SuSE/

sesam-novell-client-3.4.1-52.SuSE

sesam_srv-3.4.1-52.sles10.i586.rpm (32 bit server)

Install/Upgrade

Check your installed version of Sesam

Upgrade your installed version of Sesam

New Sesam installation

Check your installed version of iFolder

Check your installed version of Sesam

If you already have Sesam server or client installed on a host, check to see which version you have. Compare the results of the following command with the requirements for backing up iFolder with Sesam. Upgrade instructions are provided next if your installed version of Sesam is less than 3.4.1.52.

To check your installed version:

rpm -qa | grep sesam

Upgrade your installed version of Sesam

When upgrading Sesam, be sure to have the appropriate package for the computer you are upgrading. See Requirements section of this document to determine the correct package.

If you need to upgrade your Sesam server or client, change to the directory where the RPM package is located and upgrade it using:

rpm -Uvh <sesam rpm file>

For example: rpm -Uvh /install/sesam_srv-3.4.1-52.sles10.i586.rpm

New Sesam installation

If you need to install the Sesam server as well, see http://wiki.sepsoftware.com/wiki/index.php/Main_Page or http://sepusa.com/en/documentation for help with the server software installation and configuration.

If you do not have Sesam installed on the iFolder backup client, change to the directory where the RPM package is located on the iFolder backup client and install it using:

rpm -ivh <sesam rpm file>

For example: rpm -ivh /install/sesam_srv-3.4.1-52.sles10.i586.rpm

Check your installed version of iFolder server

iFolder server is provided by Novell OES2 but may not be up-to-date. iFolder updates are made available by registering your SLES10 with OES2 installation on the iFolder server and running YaST Online Updates. For help with registering your installation of SLES10 with OES2 and updating it, refer to http://www.novell.com/documentation/suse.html.

To check your installed version of iFolder:

rpm -qa | grep ifolder3-enterprise

The results displayed will show the version of the package that is installed. This needs to be version 3.6.0.7263.1-2. If your version of iFolder server is older than 3.6.0.7263.1-2, an update will be needed. See documentation provided at http://www.novell.com/documentation/suse.html for more information.

Configuration

Configure the iFolder tsaif

Create a new backup client in Sesam for iFolder

Create the iFolder backup task in Sesam

Configure the iFolder tsaif

Sesam uses the Novell iFolder Target Service Agent (TSA) called “tsaif” to back up the iFolder data. Novell SMDR must be configured to load tsaif automatically when smdrd starts. Follow these steps to make sure tsaif is configured to load automatically when SMDR service starts:

Open /etc/opt/novell/sms/smdrd.conf with a text editor such as vi.

Example: vi /etc/opt/novell/sms/smdrd.conf

(for help with vi, see man vi)

Add “autostart: tsaif” (no quotes) on a line by itself into smdrd.conf and save the changes. Now if the system is rebooted or SMDR is restarted, the tsaif will be loaded.

Load tsaif manually so you do not have to restart the SMDR service itself.

/opt/novell/sms/bin/smsconfig -l tsaif

Verify that tsaif is currently loaded using:

/opt/novell/sms/bin/smsconfig -t

(See man smsconfig for details on using smsconfig)

Create a new backup client in Sesam for iFolder

You may already have created a backup client in Sesam for the server where iFolder is being hosted. The backup client in Sesam for iFolder can be used to back up the iFolder store as well as the SLES10 file system. However, it cannot also be used to backup eDirectory on the iFolder server. A separate backup client should be created in Sesam if you would like to back up eDirectory on the iFolder server.

To create a new backup client in Sesam for iFolder:

From the Sesam server command line, start the Sesam graphical interface:

/opt/sesam/bin/gui/sesam_gui

In the Sesam graphical interface, under Components > Topology > <Your location>, highlight LOCAL and click New Client to create a new client for the iFolder backup.

A window will appear with tabs across the top of it. On the Client tab, complete the following fields:

Name

This is a descriptive name for the backup client that you may choose.

Operating System

This will be “OES Linux” for your iFolder backup client.

Interfaces

This will be completed for you and is based on the name you type in the “Name” field.

Go to the Novell SMS tab to fill in the authentication fields. The iFolder backup client will need to use the user “root” credentials on the Sesam backup server.

Account

This should be “root”.

NetWare Password

This should be root's password on the Sesam backup server. Type it twice to confirm the password.

Data Mover

From the drop-down menu, choose the Sesam backup server.

After completing the process, click OK. You will now see the new backup client you just created in the list of clients under “LOCAL”.

Configure the iFolder backup task in Sesam

This is where you select the iFolder resources to backup from the new backup client you created in the previous step.

In the Sesam graphical interface, go to Tasks > by Clients > <Your location>, LOCAL > highlight your iFolder backup client and click New backup task to create a new backup task for the iFolder backup client.

A window will appear with tabs across the top of it. On the Task tab, complete the following:

Task Name

Type a descriptive name for the backup task. This name should not be identical to the names of any of the other backup tasks or backup clients in Sesam.

Backup Type

Choose “iFolder” from the drop-down menu.

Client

This will already be populated for you. If it is not, set it to the backup client you created for iFolder.

Source

Type “/” (no quotes) to select the entire iFolder store for this backup task.

*Note: If you click the drop-down menu for “Source” and use the graphical interface to select the root directory of iFolder store, the selection will appear as “all” when applied. This will not work. You must type “/” in the “Source” field if you want the entire iFolder store backed up.

Exclude list

If you'd like to make exclusions from your source selection, either type the full paths in this field (comma separated), or click the drop-down menu to make exclusion selections using the graphical interface. The drop-down menu will open a window similar to the following. You can then browse to your desired exclusions and “Apply” them to make them excluded from the backup selection.

Done

Now you are ready to back up the iFolder resource on a SLES10 OES2 server using a SLES10 Sesam backup server. You can include the task created for iFolder in your backup schedule just as you would any other backup task. For more information on scheduling and other functions, please refer to SEP Sesam documentation available at http://wiki.sepsoftware.com/wiki/index.php/Main_Page and http://sepusa.com/en/documentation.

Additional Resources

http://www.sep.de

SEP homepage

http://download.sep.de/linux/SuSE/

SEP download page for Linux

http://wiki.sepsoftware.com/wiki/index.php/Main_Page

SEP Wiki documentation page

http://sepusa.com/en/documentation

SEP documentation page

http://download.novell.com/index.jsp

Novell's download page

http://www.novell.com/documentation/ifolder3/

Novell's iFolder documentation page

http://www.novell.com/documentation/suse.html

Novell's SuSE documentation page

IBM Tivoli Storage Manager Functionality and Features in comparison to SEP sesam

Tim Wagner — Wed, 25 Feb 2009 17:57:36 -0700

IBM Tivoli Storage Manager Functionality and Features Comparison to SEP sesam

Relational Database
Functionally IBM Tivoli Storage Manager differentiates itself from many competing products due to its integrated, relational database, which houses both the backed up data as well as the definitions and system settings. This allows a fast reconstruction of desired data, especially when dealing with individual items and small files.

SEP sesam
Like TSM SEP sesam stores information for scheduled tasks in a relational database. In so doing it provides the customer with a useful SQL database, either PostgreSQL or SQlite, providing the basis for customer optimized queries to the database. The compilation and dissemination of data and log files using a standard, common language (Command Line) is made possible with this solution. It also serves as the basis to store the position data from the saved files in a corresponding ASCII file. A fast restore of data in the SEP sesam environment is possible.

Fast Restores
TSM is especially noted for fast restores from both disk and tape. Due the design and mode of operation of TSM there exists only one version of every backed up file. TSM's relational database has recorded the exact location of the data on the tape, it can spool to the data on the tape and then perform the required restore. The restore of individual data from tape, depending on the tape technology, occurs within approximately one or two minutes and from disk almost instantly.
SEP sesam
For reasons of reliability additional data regarding position data are created and stored in corresponding files from the database are also stored in ASCII files. A rapid recovery of selected data is assured since a long and time-consuming search for the positioning data is not required.

By capturing the position data using segment marks on the tape media SEP sesam spools to the known segment and can begin the restore, also in a short amount of time. Restore tasks start within a few minutes from tape, again depending on the tape technology in use.

Progressive Incremental Backups

For this backup TSM uses an operation referred to as Progressive Incremental or respectively "Incremental Forever". After an initial full backup, e.g. of a File Server, it is thenceforth possible to only backup the changes from the last backup incrementally.
SEP sesam
The described method is provided as a standard within the SEP sesam product set. It is permissible to create any length of full plus incremental backups. SEP does, however, recommend a routine Full Backup of the data sets. This is to avoid the possible loss of data due to a defective or missing tape containing the necessary incremental backups. Further doing a full backup allows the inclusion of a Data Security plan for off-site storage of important data.

Journal Based Backup
The Progressive Incremental solution can be further enhanced with journaling (Windows und AIX).
The log file changes are recorded and this allows changes to be found easily and negates the need to spend valuable time using file scans to look for files. This shortens the backup window significantly.
SEP sesam
SEP sesam has not implemented this functionality.

Subfile Backup
The technique "Adaptive Differential" makes it possible to transfer larger data files especially using limited bandwidth on a sub-file backup level for data and files. This will require an initial full backup of the main directories then subsequent Differential backups (only the files that were altered) will be performed and kept at the ready in the event a restore is required. This allows the transfer of only the altered, updated or new date to be transferred over the LAN/WAN connection.
SEP sesam
This method is a basis for SEP sesam, Full, Differential and Incremental are integral parts of the software. Therefore, the limited connections available will not be unduly overtaxed. The practical solution is to perform full backups on a limited monthly, quarterly basis appropriate.

Backup over WAN
The Progressive Incremental technology used together with a Subfile Backup makes it possible to backup remote clients via a WAN connection. This methodology is used for IBM employees where the data is backed up to a Centralized TSM server located, for example, in New York or Boulder, Colorado.
SEP sesam
SEP sesam allows for multiple backup strategies for remote servers, workstations or laptops. They are possible in the same manner that is described for Tivoli above. The possibility exists that a client-initiated backup may be started by a registered computer (employee) when he/she is at his home office, for example, or at a hotel with sufficient bandwidth (also relevant permissions) and sufficient time to complete the data transfer. In addition a Remote Server can be backed up to the central server when connected.

Tape Reclamation und Collocation
Tape reclamation is a function for defragmenting tape media. The TSM relational database monitors continually the allotment of valid or current backed up data on the tape media. When the value of this data falls below a pre-determined threshold the data is selected for transfer to other media. The original media can now again be used as a scratch volume for new backup or backup task. The functional collocation suppresses the possibility that data from individual clients is distributed across multiple media and avoids the necessity to load several tapes for a single restore.
SEP sesam
Tape reclamation and collocation place higher demands on hardware and the time required to perform such tasks. It is always the possibility that when such a conversion or migration task is being performed on a tape drive, that the tape drive is not available for its primary function - that of online backup. Further, in the event a restore is required the tape drive is likewise unavailable. A much higher hardware unavailability must be calculated into the over backup and archival strategy, whether on tape or virtual media. Together with the its storage pool design for media and backups SEP sesam delivers an automatic method to fine tune the cycle required for stored data. SEP sesam recognizes dependencies from storage requirements FULL-DIFF-INC automatically and implements the needed time increase for media retention.

Retention
The length of time client data is retained depends upon the policy set during initial installation as well as the class of data established during the same process. The retention period is not dependent upon the tape media. The last backup performed on a valid file can remain in the backup sequence without restriction or expiration date so long as the assigned backup file space is not reassigned to another task or deleted.
SEP sesam
The SEP sesam retention concept is reliant upon the point 'reclamation' and is dependent upon the Media Pool and Media level selected. The storage design allows for the sorting and selective retention of short and long-term data storage. Using our Media Pool design structure a comprehensive preservation of data depending on legal requirements or company philosophy can be set up to fill almost any needs. In so using the flexibility of SEP sesam the storage team can, along with management input, decide which data will be sent off-site and which data will be stored to to comply with legal and regulatory requirements and which may be deleted.

Data Archival
In addition to its primary design function to provide backup and restore services, TSM is especially suited for long term archival of data The length of time data will be held in safekeeping depends on the policy established in the software's retention setup files. It is always possible to migrate data from older to new tape technology. In this way there is no continued need to rely upon older hardware used to originally backup and archive data.
SEP sesam
SEP sesam delivers a comprehensive and automatic migration concept for the long-term storage of data for archival purposes, which is not dependent upon the media originally used for backup. The design allows for disk-to-disk-tape, tape-to-disk or tape-to-disk-to-tape assuring availability of data for a required restore or eventual conversion to a new tape technology when required.

Hierarchical Storage Management (HSM)
HSM is a technology that offers the possibility to move data without impacting the user to more in-expensive media such as tape. The data remains visible to the user as sub-files with a changed or new Icon. In the event a user requests the data using the Icon the data is restored quickly. Using this method there is a slight increase in data recovery but a significant overall savings in media required for storage.
SEP sesam
SEP sesam does not offer HSM technology. The function is often performed by other operating systems (Novell OES2, GroupWise) and the use of Storage Pools allows for the transfer of less used data to be transferred to inexpensive media.

Media Administration
TSM has a well-designed Media Management element. Tivoli can manage tape media as well as the TSM server where a Tape Library Share has been established. When there is a tape-removal from the tape library they are monitored from the TSM server using a console alert.
SEP sesam
SEP sesam maintains a catalog of tapes that have been removed from the tape drives, autoloaders and libraries. This allows quick access to the data stored on any media within the software storage pool. The comprehensive and flexible pool concept used by SEP sesam, using disk and tape, fulfills almost every possibility for customer requirements. Automatic rotation cycles and manual, in some cases partial manual operation including the control of single tape drives on dedicated computer systems (Databases) is easily ascertainable, easy to set up for automatic operation, without further operator action. The media control is possible throughout the SEP sesam software in all backup setup and control using central administration for unlimited control and possibilities, and is also available in LAN and SAN.

Capacity Usage of Tape Media
TSM normally utilizes the entire tape media while performing backups. The reclamation process within TSM allows, after a specified timeframe, to consolidate the current, relevant information from each tape. The technology allows for an average higher usage of all tape media.
SEP sesam
SEP sesam can write the storage on disk or tape to 100% by using the existing compression technology from the drives' manufacturer and can also use special algorithms in SEP sesam when backing up to disk. A migration of data to disk for a storage consolidation is not required and saves a great deal of effort and time.

Migration from disk to tape
Within the TSM data can be migrated easily between disk and tape media. Called 'staging' in TSM this can be controlled by data size, administrative schedules or by user command line input.
SEP sesam
SEP sesam allows the system administrator to create an automatic migration philosophy or concept for the storage and migration of data. This allows the data to be moved from primary to secondary storage simply and easily. Migration of savesets from disk to tape and from tape back to disk is easily accomplished.

Administration
The administration of the TSM Server is possible using a web-browser or Command Line Interface (CLI).
SEP sesam
The SEP sesam Server can be administered from practically any Java enabled desktop via a user optimized graphical user interface (GUI). Access to the server can be set by the system administrator which some or all functionality to be available to specific users. The complete administration of the SEP sesam Server is also available via the Command Line Interface, including the Microsoft version.

Administrative Schedules
A basis concept of the TSM Servers is to make the backup, restore and archival functionality as automatic as possible. Administrative schedules allows complex database, data migration are other housekeeping chores to be performed at the discretion of the administrator.
SEP sesam
SEP sesam allows the free configuration by the administrator of all tasks for backups, restores and migration using the integrated full calendar in addition to event guided immediate performance of desired tasks.

Server Backup
For backing up Client servers and their restoration native GUI's, web interfaces and Command Line Interfaces are available. Typically, backups are performed at night and are performed based on predetermined schedules and restores set up using a GUI.
SEP sesam
The central concept for SEP sesam relies upon the planned control of all backup and restore tasks to use all storage facilities as efficiently as possible. A client-side ersatz or complimentary task definition and activation is herewith made possible. These activities, however, are only allowed insofar as permitted by the system administrator during initial setup or later determination. Activities not allowed by the system design or architecture are not permitted, however. Data Restore is allowed via the SEP sesam Restore Wizard, and controls for unauthorized access to data are in place to protect valuable data.

Operational Reporting
TSM uses Operational Reporting for the daily control and monitoring of backups. Here there is a Snap-In in the Microsoft Management Console (MCC) for a Windows based computer. Important parameters of the TSM Servers, i.e. completed schedules and successful tape mounts are regularly cataloged and shown in HTML format. Using an SMTP server the graphical reports can be sent as needed.
SEP sesam
SEP sesam allows for different on and offline report interfaces to be accessed and controlled by the administrator and can be integrated fully into the backup design determined by the enterprise administrator to be forwarded via any method desired, e.g. mail, SMTP, etc. The SEP database structure allows the access to log files for individual analysis. In this way, for example, it can be determined which business units, in which time frame, what and how much data has been stored and where. This is especially useful for budgeting processes where department utilizes additional storage resources and can be billed and tracked internally. Graphical overviews can be created and provided to users and management for illustrative, billing or other purposes or can be provided in a text format for easy availabililty via a simple LAN connection.

Integrated Disaster Recovery Manager
An integrated Disaster Recovery Manager allows the outsourced storage of backed up data. In the event of a disaster, i.e. system failure, the administrator can utilize the recovery plan supported by the recovery manager. The restore of the IBM Tivoli Storage Manager Server is performed using the recovered copy of data and the internal TSM database.
SEP sesam
SEP sesam can utilize the backup utilities from various recovery requirements. The full recovery and restore of a SEP sesam backup server can be performed from CD or from tape. In addition to the basic server recovery SEP also offers Bare System Recovery for clients (Linux and Windows via CD).

Encryption
IBM Tivoli Storage Manager Client offers the possibility to encrypt using 128 Bit AES as well as the 56 Bit DES Algorithm.
SEP Sesam
SEP sesam offers open-source standard encryption using the Blowfish algorithm and allows the selection of AES 256 encryptions, as well.

NDMP Backup of NAS Appliances
Data from selected fileservers or appliances can be stored directly to tape using the NDMP protocol. Herewith a Table of Contents (TOC) is used to create a
Direct Access Restore (DAS) at file level. The NDMP backup procedure does not require a dedicated tape drive.
SEP sesam
SEP does not offer NDMP.

CRC Algorithm
Using a CRC algorithm allows for the control of data integrity. In the event of a hardware error or defect, e.g. in TCP/IP or in Fiber Channel network data can be damaged during transmission between the TSM client and TSM server, or during the read-write process. Implementation of the CRC methodology alerts the administrator of such problems and allows for their correction.
SEP sesam
The final and deciding data integrity determinant is the successful restore of backed up data. Using scheduled restores SEP sesam offers the
ability to restore either short or long term backups from tape or disk. As a test restore, for example, data can be scheduled for a six-month (or any period for that matter) to verify the accuracy of the data. The data is read from the data store and rewritten to the target client for automatic comparison to the original data. All transaction logs and the restored files are journaled. In addition, the tape is rewound and conserved for a longer storage period; herein the data can be further protected against over-writing and over use. Using the pre/post commands during the scheduled restore can be fully automated, performed and verified without any administrative interaction. The notations and records created by SEP sesam are a substantive legal record to verify the validity of backed up and stored data that if more and more often required by government regulation. A further enhancement of performance test methodology is already underway for the intention of providing even more data for evidential requirements.

Backup Sets
Backup sets are an optional method for writing backed up data for a secured client to tape media. This backup can then be resent to the client or carried via the tape media to the client location and restored to the client using the TSM server.
SEP sesam
SEP sesam offers several methods for the restore and recovery of client data. This is covered from authenticated data to Bare System Recovery in the event of a system disaster connection with the backup server (protection against unauthorized recovery) to silent methods using recovery from local tape to recovery without assistance from service personnel.

LANfree Backup
The backup can occur over a local network (LAN) or LANfree, over a Storage Area Network (SAN). This method is selected within the TSM Server attached storage components. A LANfree backup is especially useful for databases, groupware solutions and mySAP applications. For such applications there are some specialized backup agents available.
SEP sesam
The described TSM functionality is basically the way SEP sesam works. A combination of various backup solutions can be combined to work both on the LAN and LANfree using the SAN environment. SEP sesam offers multiple possibilities to backup data within the SAN.

Online Image Support
For Windows 2000 und 2003 TSM offers Online Image und Open File Support. With these tools data directories can be secured and restored online. This method is especially useful, for example, when a weekly extension to incremental backups is desired. In the event a data volume is lost a Point-in-Time Restore is made possible with this option.
SEP sesam
In SEP sesam all methods for a Windows system recovery is possible, also from CD-similar to imaging. The restore of basic system configuration, including a check of changes in hardware and drivers is possible using SEP BSR for windows.

Tape Library Sharing
The Tape Library Sharing option makes multiple TSM Server tape resources available for other TSM servers without requiring a partitioning of the tape library. One of the TSM serves in this example designated as the TSM Library Manager, and it manages the tape robotics, the drives and the tapes themselves. All other TSM servers act as TSM Library clients, that means that they are only allowed access to the drives. When a library client wants to write data a request is issued to the Library Manager to present a media for backup. Tape Library Sharing functions within heterogeneous environments so that TSM Server can be used for many different operating systems.
SEP sesam
The SEP sesam control concept allows all functions as described above. The management of the library hardware environment is also available within the SAN without direct access from the backup server. A multi O/S environment using Remote Device and Remote Device server is also possible.

WORM Tapes
TSM can write to these tapes, although they are handled with a special routine.
SEP sesam
Supports both WORM Tapes and WORM Disk-selection during setup is optional.

Mixed Media Support
Within any Tape Library different hardware versions of any specific tape media technology can be supported. It only requires the user to specify device type when configuration is taking place.
SEP sesam
SEP sesam supports a wide range of user selectable media and disk drive types used by various OEM's within their product offerings. SEP sesam supports almost every type of storage and storage solution from every manufacturer by using straightforward logical standard protocols.

Server Recovery and Protection from Disaster and System Failure
SEP sesam makes it possible to provide reliable, efficient and fast backup for diverse and backup infrastructures and demanding requirements to provide data availability for company locations or network segments. A standby SEP sesam server can also, for example, be a Remote Device Server that acts as a secondary server in the event the primary server fails. It can take over the complete functionality of the SEP sesam backup server until the latter is re-installed or recovered. Once the SEP sesam server is back online the Remote Server transmits the data back to the primary server and falls back to its secondary or backup status. In normal use the Remote Device Server serves as a data mover.

An example of the SEP sesam's flexibility is the fact that data can be moved from a Windows server to a Linux server and vice-versa without losing any data integrity. The many strengths and advantages of SEP sesam is incomparable adaptability and configuration flexibility requiring only minimal administrative effort. A standard training effort to become familiar with the main functionality of SEP sesam takes between 1 and 3 days, after which a test and certification process leads to a SEP Certified Administrator status.

NORTH AMERICA | SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
REST OF THE WORLD | SEP AG, Zie g e l s t ra s s e 1 , 8 3 6 2 9 We ya rn , Ge rma n y, + 4 9 8 0 2 0 1 8 0 - 0
FOR FURTHER INFORMATION, VISIT www.sep.de / www.sepsoftware.com | Copyright SEP AG 2008

SEP sesam VMware - SUSE Enterprise Server - Backup Appliance White Paper

Tim Wagner — Tue, 24 Feb 2009 01:21:12 -0700

Whitepaper - SEP Appliance VMware

The SEP sesam SUSE Linux Enterprise Server Appliance (SEP App) is a pre-configured "out of the Box" solution for VMware environments. The implementation and evaluation of SEP sesam is made simply and easily using our new Appliance. All necessary files and system requirements have been pre-configured and are available to the user. Simply import the SEP sesam Virtual Appliance using the VMware Infrastructure Client Assistant and SEP sesam is ready to test and run. This solution allows for quick implementation and testing without requiring special system knowledge. It further reduces time and resources resulting in additional cost savings.

Our turnkey solution opens the way for a quick, easy and efficient implementation of an enterprise critical solution – reliable data backup and data availability. By using the SEP sesam Appliance, the installation and configuration of the operating system and of the SEP sesam Backup Servers, is no longer required. Using SUSE Linux Enterprise Server , an enterprise class Linux system offered by Novell, assures the support from all Enterprise Storage System manufacturers. In addition, around-theclock support is also assured both from SEP and from the hardware manufacturers. Relevant drivers for hardware, e.g. for the SEP sesam’s Virtual Tape Library (VTL), are also provided, in addition to a comprehensive „Out of the Box“ preconfiguration scenario to fit many situations. The SEP sesam Software Appliance is base on the technology of SUSE Linux Enterprise Server and VMware Studio.

SEP sesam is certified for a large number of operating systems and databases. The product portfolio also includes online backup capability and modules for all popular Open Source Collaboration Modules as well as Novell GroupWise and Microsoft Exchange. Database backup modules are available for uninterrupted workflow for Oracle, DB2 and SAP-DB including connection to SAP/R3. Many other popular database online modules are also available. Using our SEP sesam Backup Appliance you can implement a complete and reliable backup infrastructure within minutes to secure your entire infrastructure; from your data to your file systems. The backup infrastructure easily includes all your complex database structures. A complete, up-to-date list of supported operating systems and server technolgies as well as database versions and groupware modules can be found at:

http://wiki.sepsoftware.com/wiki/index.php/SEP_sesam_OS_and_database_support_matrix
A free 30-day trial can be downloaded from http://download.sep.de/

Our SEP sesam Backup Appliance has been installed in companies around the world and secures the IT infrastructure to assure data security and data availability for enterprises of any size. Illustration: Branch Office A specific installation of the SEP sesam Software is not required when the distribution (transmission or download) of the SEP sesam Appliance is transferred to the subsidiary. After starting the SEP sesam Appliance on the VMware ESX Server Platform, all services are available immediately. The final configuration for the locale takes place through the central administration from the IT organization using the remote access capability provided by the SEP sesam Master GUI. The SEP sesam Master GUI allows the centralized control of all system monitoring and configuration tasks. The well-designed and easy to use Java based GUI allows a single Point of Administration for all tasks and functions including backup, restore and disaster recovery using SEP BSR The system automatically generates Status and Error Logs and informs all necessary personnel when intervention or control functions need to be performed. The SEP sesam Backup Appliance for VMware can be enhanced by choosing among a variety of additional Service Level Agreements from multi-call to around-the-clock protection to fully meet any institution’s service requirements.

Further information can be obtained from: http://www.sep.de/home_de.php and http://wiki.sepsoftware.com/wiki/index.php/Main_Page

| SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
| SEP AG, Z ie g e l s t ra s s e 1 , 8 3 6 2 9 We y a r n , Ge rma n y, +4 9 8 0 2 0 1 8 0 - 0

White Paper - VMware ESX Online Module

Tim Wagner — Wed, 18 Feb 2009 09:48:56 -0700

Whitepaper
SEP sesam Online Backup for VMware ESX
This document describes the technique utilized by the SEP sesam VMware module to backup VMware
ESX environments and the relevant licenses required. SEP sesam supports VMware Consolidated
Backup (VCB). For enhanced understanding of our software we are providing a brief, technical
discussion for VMware ESX without VCB and a further discussion which includes VCB.
VMware ESX Backup without VCB
Conventional Backup Solution:
In VMware environments (also with ESX) all servers (guests) are currently backed up the same as
standard host based servers, or through a regular database backup solution. A backup agent for each
guest is required. Such a configuration creates a higher demand or CPU utilization of the target server
or VMware Host.
Another backup method is to completely copy the virtual disks using the VMware Service Console
within ESX. The disadvantage to this solution is the large amount of data from each backup and the
requisite data storage required as well as the manual labor that must be performed during such
operations. One of the main disadvantages is that a recovery is only possible for the entire system.
The restore of individual files or directories isn’t possible.
VMware ESX Backup with VCB Backup Proxy (VCB)
VMware Consolidated Backup is an access method from VMware and allows the backup of the virtual
machine from a central Backup Proxy, directly from a SAN, without diverting or directing data over the
LAN. The Proxy is a physical Server running Microsoft Windows Server 2003, and it must have access
to the same SAN where ESX is running. Ideally the server should be connected to and controlling its
own streaming drives or a Tape Library. The Proxy could also be connected to a remote backup
device, e.g. disk farm on a NAS.
However, VMware Consolidated Backup is not a backup program, it delivers only the access to the
virtual disk drives on the Windows guest. The actual backup process must be taken over and
completed by a backup solution.
SEP_ESX_Whitepaper_160708_EN.doc | 1/4
NORTH AMERICA | SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
REST OF THE WORLD | SEP AG, Zie g e l s t ra s s e 1 , 83 6 2 9 Weya rn , Ge rma n y, + 4 9 8 0 2 0 1 8 0 - 0
FOR FURTHER INFORMATION, VISIT www.sep.de / www.sepsoftware.com | Copyright SEP AG 2008
Whitepaper
A backup using VCB works on a Snapshot Basis and must use a custom Stop/Start scripted procedure
which also provides access to the working database to function and provide a consistent backup of the
guest systems. Using VMware Tools you gain access to the user specific scripts to work on the guest
virtual machine.
Since the Backup Proxy cannot write on the virtual disk of a running virtual machine the recreation or
restore of individual files onto the guest system always occurs via the LAN.
VMware ESX Backup with VCB and SEP sesam
The basic description for the backup is also the framework for a backup performed by SEP sesam.
The illustration below shows the SEP sesam Clients (Guest system on the ESX server) and the ESX
Server.
The SEP sesam Backup Server adjoins and complements via the ESX Client backup procedure. The
backup follows the processes allowed by VCB and the Snapshots from the Guest system on the ESX
Server are created and tendered for backup by SEP sesam. The location of the Snapshots also follows
the configuration of the ESX Server environment in SAN, NAS or locally on the VMware ESX Server!
The second step stores the generated data on the available storage space (disk or tape) and is
controlled by the SEP sesam Server. The data transfer runs from VMware ESX Server (SEP sesam
Client) over the LAN to the SEP sesam Backup Server.
With the additional installation of a SEP sesam SAN Remote Device (SRD) on the ESX Server it is
possible to store data within the guest snapshot on the SAN. The SAN Remote Device has access to
the Save Sets on the SAN connected devices. The timely and logical control of the backup is
performed via the SEP sesam server, the dataflow, however, stays completely within the SAN
(LANfree backup) and only travels on the ESX Server when using a physical Tape Device (Loader) or
a virtual Tape Library.
Independent of whether the backup proceeds as a LANfree Backup or over the LAN we recommend
the additional installation of SEP sesam Client Software on the Guest Systems. This combination of
regular and responsive backups of snapshots along with daily incremental backups of the LAN
environment for the Guest Systems offers optimal performance for strategic VMware environments.
Data volume will be greatly reduced and SEP sesam offers the added benefit of fast full backups.
Implementing this solution allows exact data restores of single or multiple files, without regard to the
Operating System running on the Guest .
SEP_ESX_Whitepaper_160708_EN.doc | 2/4
NORTH AMERICA | SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
REST OF THE WORLD | SEP AG, Zi e g el s t ra s s e 1 , 8 3 6 2 9 We ya rn , Ge rma n y , + 49 8 0 2 0 1 8 0 -0
FOR FURTHER INFORMATION, VISIT www.sep.de / www.sepsoftware.com | Copyright SEP AG 2008
Whitepaper
VMware ESX Backup with VCB Backup Proxy and SEP sesam
The utilization of a VMware Backup Proxy in an environment with SEP sesam is also possible. This
requires the installation of a SEP sesam Client on the Backup Proxy (Windows 2003 Server). The SEP
sesam Server is combined with the Backup Proxy of the guest system on the VMware ESX Server.
Data is requested from the Backup Proxy via a (Snapshot) and copied to the local disk. (SAN Device
ESX to Backup Proxy Disk). The Snapshot Data are then transported over the LAN to the backup
device and stored.
In a VMware ESX Server environment with Backup Proxy you can also use a SAN Remote Device
(SRD).
Installation and Licensing Requirements
Stand-Alone ESX Server
Installation: Licenses Required:
1x SEP Client on Guest and ESX Computer (5x) 4x Data backup clients (BC)
1x ESX Package (RPM) 1x ESX Server Client (5 Seat)
In this rather simple environment the data from the guest systems are combined as one Snapshot (on the ESX Server) and
completed as an incremental backup. The number of the guest systems is covered by the initial SEP sesam Backup Client for
ESX Server. The dataflow is completely directed through the LAN. Each SEP sesam Backup Client for ESX Server includes a
SEP sesam Backup Client. This simpler configuration does not require additional licenses.
SEP_ESX_Whitepaper_160708_EN.doc | 3/4
NORTH AMERICA | SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
REST OF THE WORLD | SEP AG, Zie g e l s t ra s s e 1 , 83 6 2 9 Weya rn , Ge rma n y, + 4 9 8 0 2 0 1 8 0 - 0
FOR FURTHER INFORMATION, VISIT www.sep.de / www.sepsoftware.com | Copyright SEP AG 2008
Whitepaper
ESX Server Combination (VMotion possible)
Installation: Licenses Required:
1x SEP Client on Guest and ESX Computer (13x) 11x Data backup clients (BC)
2x ESX Package (RPM) 2x ESX Server Client (5 Seat)
1x ESX 5 Seat Add-on
The environment with two VMware ESX Servers and a greater number of guest systems also stores all data via the LAN to the
backup device. Licensing of the Guest Servers (Seats) is handled by SEP sesam globally. Each SEP sesam Backup Client for
ESX Server includes a SEP sesam Backup Client and this configuration does not require additional licenses.
ESX Server Combination (VMotion possible) LANfree
Installation: Licenses Required:
1x SEP Client on Guest and ESX Computer (10x) 9x Data backup clients (BC)
1x ESX Package (RPM) 1x ESX Server Client (5 Seat)
1x Remote Device 1x SEP sesam SAN Remote Device
1x ESX 5 Seat Add-on
In this environment VMware ESX Server becomes an active backup component with the installation of SEP sesam Remote
Device. The data stream does not flow over the LAN to the SEP sesam backup server, but rather to the SAN Remote Device
Function and directly to SAN connected tape loader. In the event a tape library is connected to a SAN, a per-slot license (SEP
sesam Autoloader Support) is required.
Basic information for SEP sesam Options and Licenses can be found on
www.sep.de / www.sepsoftware.com.
SEP_ESX_Whitepaper_160708_EN.doc | 4/4
NORTH AMERICA | SEP Software LLC, 4845 East Pearl Circle, Suite 101, Boulder, CO 80301, USA, +1-303-417-6316
REST OF THE WORLD | SEP AG, Zi e g el s t ra s s e 1 , 8 3 6 2 9 We ya rn , Ge rma n y , + 49 8 0 2 0 1 8 0 -0
FOR FURTHER INFORMATION, VISIT www.sep.de / www.sepsoftware.com | Copyright SEP AG 2008