RDP Server

IBM Information Protection Services
Remote Data Protection for Servers: Installation and Restore Guide

V ersion 4.0
Note Before using this information and the product it supports, read the information in Notices on page 63.
December 2008 This edition applies to version 4, release 0, of IBM Information Protection Services - remote data protection and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright International Business Machines Corporation 2008. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Introduction . . . . . . . . . . . . . v Chapter 9. MS SQL agent . . . . . . . 39
System requirements . Installing . . . . . Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 . 40 . 40
Part 1. Installation and Upgrade Guide . . . . . . . . . . . . . . . 1

Chapter 1. AIX client . . . . . . . . . 3
System requirements. Installing . . . . Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 . 3 . 5
Part 2. Command-line Interface (CLI) Guide . . . . . . . . . . . . 43

Chapter 10. Overview . . . . . . . . 45
Operating system information . Required information . . . . . . . . . . . . . . . . . 45 . 45
Chapter 2. HP-UX client . . . . . . . . 9

System requirements. . . . . . . . . . . . 9 Installing . . . . . . . . . . . . . . . 10 Upgrading . . . . . . . . . . . . . . . 11
Chapter 11. Examples . . . . . . . . 47
Chapter 3. Linux client . . . . . . . . 13

Part 3. Windows Web Restore Guide . . . . . . . . . . . . . . . 49

Chapter 12. Overview . . . . . . . . 51
Backup features . . . . . . . . . . . . . 51
Chapter 4. Mac OS client . . . . . . . 17

System requirements . . . . Installing . . . . . . . . Special firewall considerations Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17 18 18
Chapter 13. Getting started . . . . . . 53

Activate the backup client View recent backup history Check for your client path Backup schedule. . . . Backup retention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 53 53 53 54
Chapter 5. Solaris client . . . . . . . 21

Chapter 14. Restoring files using Web restore . . . . . . . . . . . . . . . 55

Logging in. . . . . . . Procedure for restoring files . Provider-initiated restores . . . . . . . . . . . . . . . . . . . . . . 55 . 55 . 56
Chapter 6. Windows client . . . . . . 27

System requirements . . . . Installing . . . . . . . . Special firewall considerations Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 28 29 29
Chapter 15. Other features . . . . . . 57

View . Actions . Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 . 58 . 59
Chapter 7. MS Exchange Information Store agent . . . . . . . . . . . . . 31

Chapter 16. Troubleshooting and known limitations . . . . . . . . . . 61 Notices . . . . . . . . . . . . . . 63
Chapter 8. MS Exchange agent . . . . 35

System requirements . . . . . . . . . . . 35 Configuring the MS Exchange Server mailbox level agent . . . . . . . . . . . . . . . . 36 Upgrading the MS Exchange Server mailbox level agent . . . . . . . . . . . . . . . . 38
Trademarks. . . . . . . . . . . . . 67
Copyright IBM Corp. 2008
iii
iv
Remote Data Protection for Servers
Introduction
This document is designed to help guide you through the installation and use of IBM Information Protection Services - remote data protection, a fully managed remote data protection service for servers. This document consists of three main sections: v Part 1, Installation and Upgrade Guide, on page 1. This section describes how to install and upgrade the product on supported operating systems. v Part 2, Command-line Interface (CLI) Guide, on page 43. This section contains examples on how to use the CLI. v Part 3, Windows Web Restore Guide, on page 49. This section contains information on how to get started and use the Web restore features of the product.
vi
Part 1. Installation and Upgrade Guide

The installation and upgrade section contains operating system specific information for installing the Remote data protection client and information for installing the database agents. This section contains the following chapters: v Chapter 1, AIX client, on page 3. v Chapter 2, HP-UX client, on page 9. v Chapter 3, Linux client, on page 13. v Chapter 4, Mac OS client, on page 17. v v v v v Chapter 5, Chapter 6, Chapter 7, Chapter 8, Chapter 9, Solaris client, on page 21. Windows client, on page 27. MS Exchange Information Store agent, on page 31. MS Exchange agent, on page 35. MS SQL agent, on page 39.
Chapter 1. AIX client

This section contains the following information for the AIX client: v System requirements. v Installing. v Upgrading on page 5. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 5. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the AIX client.
Table 1. Minimum hardware and software requirements for the AIX client Hardware and software Operating systems Requirements v AIX 5.3, 5.2, and 5.1 (32-bit and 64-bit) v AIX 6.1 (64-bit) File systems RAM Hard drive space v JFS A minimum of 96 MB. A minimum of 200 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files. Network interface 10baseT or higher, configured with the latest drivers for your platform, is required.
Installing
The following steps are for downloading and installing the AIX client. If you are installing an upgrade, but not a full installation, see Upgrading on page 5. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download.
3. From the location where you saved the software, issue the following command as root:
geninstall d AvamarClient-4.0.3-xxx.aix5.bff all +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------AVMRclnt 4.0.3.xxx << End of Success Section >> FILESET STATISTICS -----------------1 Selected to be installed, of which: 1 Passed pre-installation verification ---1 Total to be installed +-----------------------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------------------+ installp: APPLYING software for: AVMRclnt 4.0.3.xxx . . . . . << Copyright notice for AVMRclnt >> . . . . . . . This software is copyright EMC Corporation, 2001-2007. Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. . . . . . << End of copyright notice for AVMRclnt >>. . . . Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 16344 avagent.d Info: Client Agent started. Finished processing all filesets. (Total time: 20 secs). +-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------------------AVMRclnt 4.0.3.xxx USR APPLY SUCCESS
# Avamar Axion client 4.0.3-xxx..
4. Issue the following command to register your client with the backup server:
/usr/local/avamar/bin/avregister
=== Client Registration and Activation This script will register and activate the client with the Administrator server. Enter the Administrator server address (DNS text name, not numeric IP address): <CALL THE IBM INFORMATION PROTECTION SERVICES SUPPORT LINE AT 1-866-237-9677 TO RECEIVE YOUR ADMIN SERVER ADDRESS> Enter the Axion server domain [clients]: <enter to accept default> avagent.d Info: Stopping Axion Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent.d Info: Client activated successfully. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 17640 avagent.d Info: Client Agent started. Registration Complete.
After successful completion, inform your service provider that installation and activation of the client is complete.
Upgrading
The following steps are for installing an upgrade of your current AIX client: 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. Copy the following agent configuration files to the /tmp directory using the following commands: a. cp /var/avamar/avagent.cfg /tmp b. cp /var/avamar/p_cache.dat /tmp c. cp /var/avamar/f_cache.dat /tmp 4. Uninstall the old version by running the following commands: a. /etc/rc.d/init.d/avagent stop b. /etc/rc.d/init.d/avagent unactivate c. geninstall u AVMRclnt
+-----------------------------------------------------------------------------+ Pre-deinstall Verification... +-----------------------------------------------------------------------------+ Verifying selections...avagent.d Info: Client Agent not running. done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-deinstall verification and will be removed. Selected Filesets ----------------AVMRclnt 3.7.1.100 << End of Success Section >> FILESET STATISTICS -----------------Chapter 1. AIX client
# Avamar Axion client 3.7.1-100...
Selected to be deinstalled, of which: 1 Passed pre-deinstall verification
---1 Total to be deinstalled +-----------------------------------------------------------------------------+ Deinstalling Software... +-----------------------------------------------------------------------------+ installp: DEINSTALLING software for: AVMRclnt 3.7.1.100 Finished processing all filesets. (Total time: 4 secs).
+-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------------------AVMRclnt 3.7.1.100 USR DEINSTALL SUCCESS
5. Move the configuration files back to the original locations using the following commands: a. mv /tmp/avagent.cfg /usr/local/avamar/var b. mv /tmp/p_cache.dat /usr/local/avamar/var c. mv /tmp/f_cache.dat /usr/local/avamar/var 6. Install the new client by running the following command as root from the location where you saved the software:
geninstall d AvamarClient-4.0.3-xxx.aix5.bff all +-----------------------------------------------------------------------------+ Pre-installation Verification... +-----------------------------------------------------------------------------+ Verifying selections...done Verifying requisites...done Results... SUCCESSES --------Filesets listed in this section passed pre-installation verification and will be installed. Selected Filesets ----------------AVMRclnt 4.0.3.xxx << End of Success Section >> FILESET STATISTICS -----------------1 Selected to be installed, of which: 1 Passed pre-installation verification ---1 Total to be installed +-----------------------------------------------------------------------------+ Installing Software... +-----------------------------------------------------------------------------+ installp: APPLYING software for: AVMRclnt 4.0.3.xxx
# Avamar Axion client 4.0.3-xxx..
. . . . . << Copyright notice for AVMRclnt >> . . . . . . . This software is copyright EMC Corporation, 2001-2007. Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. . . . . . << End of copyright notice for AVMRclnt >>. . . . Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 16344 avagent.d Info: Client Agent started. Finished processing all filesets. (Total time: 20 secs). +-----------------------------------------------------------------------------+ Summaries: +-----------------------------------------------------------------------------+ Installation Summary -------------------Name Level Part Event Result ------------------------------------------------------------------------------AVMRclnt 4.0.3.xxx USR APPLY SUCCESS
The upgrade is now complete, and your regularly scheduled backups will continue to run.
Chapter 1. AIX client
Chapter 2. HP-UX client

This section contains the following information for the HP-UX client: v System requirements. v Installing on page 10. v Upgrading on page 11. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 11. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the HP-UX client.
Table 2. Minimum hardware and software requirements for the HP-UX client Hardware and software Operating systems Requirements v HP-UX 11i v3 v HP-UX 11i v2 v HP-UX 11i v1 (patch PHSS_28871 is required) v HP-UX 11.0 (patch PHSS_24303 is required) CPU v PA-RISC v Itanium (only for HP-UX 11i v3 and HP-UX 11i v2) File systems v HFS v VxFS RAM Hard drive space A minimum of 96 MB. A minimum of 200 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files. Network interface Web browsers Adobe Acrobat Reader 10baseT or higher, configured with the latest drivers for your platform, is required. Optional. Required in order to use Web Access download and restore features. 5.0 or higher. Available from www.adobe.com. Optional. Required in order to view online documentation.
Installing
The following steps are for downloading and installing the HP-UX client. If you are installing an upgrade, but not a full installation, see Upgrading on page 11. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. From the location where you saved the software, issue the following command as root:
# swinstall s /tmp/AvamarClient-4.0.3-xxx.hpux11.parisc.depot ======= 10/29/07 07:54:52 PST (non-interactive) BEGIN swinstall SESSION
* Session started for user "root@hpux1". * Beginning Selection * Target connection succeeded for "hpux1:/". * Source: /tmp/AvamarClient-4.0.3-100.hpux11.parisc.depot * Targets: hpux1:/ * Software selections: hpuxclnt.hpuxclnt-exec,r=4.0.3-100,a=HP-UX_B.11.00_32/64 * Selection succeeded. * Beginning Analysis * Session selections have been saved in the file "/.sw/sessions/swinstall.last". * The analysis phase succeeded for "hpux1:/". * Analysis succeeded. * Beginning Execution * The execution phase succeeded for "hpux1:/". * Execution succeeded. NOTE: ======= # More information may be found in the agent logfile (location is hpux1:/var/adm/sw/swagent.log). 10/29/07 07:55:24 PST END swinstall SESSION (non-interactive)
/opt/AVMRclnt/bin/avregister
=== Client Registration and Activation This script will register and activate the client with the Administrator server. Enter the base directory of the AvamarClient installation [/opt/AVMRclnt]: <enter to accept default> using BASEDIR=/opt/AVMRclnt Enter the Administrator server address (DNS text name, not numeric IP address): <REPLACE_SERVER> Enter the Axion server domain [clients]: <enter to accept default> avagent.d Info: Stopping Axion Client Agent (avagent)...
10
avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to ///opt/AVMRclnt//var/avagent.log avagent.d Info: Client activated successfully. avagent Info <5241>: Logging to ///opt/AVMRclnt//var/avagent.log avagent Info <5417>: daemonized as process id 28456 avagent.d Info: Client Agent started. Registration Complete.
After successful completion, inform your service provider that installation and activation of the client are complete.
Upgrading
The following steps are for installing an upgrade of your current HP-UX client: 1. Link to the following document file containing the downloads to the client software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. Copy the following agent configuration files to the /tmp directory using the following commands: a. cp /var/avamar/avagent.cfg /tmp b. cp /var/avamar/p_cache.dat /tmp c. cp /var/avamar/f_cache.dat /tmp 4. Uninstall the old version by running the following commands: a. /sbin/init.d/avagent stop b. /sbin/init.d/avagent unactivate c. swremove hpuxclnt
======= 10/29/07 07:38:50 PST (non-interactive) BEGIN swremove SESSION
* Session started for user "root@hpux1". * Beginning Selection * Target connection succeeded for "hpux1:/". * Software selections: hpuxclnt.hpuxclnt-exec,l=/opt/AVMRclnt,r=3.7.1-100,a=HP-UX_B.11.00_32/64 * Selection succeeded. * Beginning Analysis * Session selections have been saved in the file "/.sw/sessions/swremove.last". * The analysis phase succeeded for "hpux1:/". * Analysis succeeded. * Beginning Execution * The execution phase succeeded for "hpux:/". * Execution succeeded. NOTE: More information may be found in the agent logfile (location
Chapter 2. HP-UX client
11
is hpux1:/var/adm/sw/swagent.log). ======= 10/29/07 07:39:07 PST END swremove SESSION (non-interactive)
5. Move the configuration files back to the original locations using the following commands: a. mv /tmp/avagent.cfg /var/avamar b. mv /tmp/p_cache.dat /var/avamar c. mv /tmp/f_cache.dat /var/avamar 6. Install the new client by running the following command as root, but substitute the path to the installer if it is different:
# swinstall s /tmp/AvamarClient-4.0.3-xxx.hpux11.parisc.depot \* ======= 10/29/07 07:48:17 PST (non-interactive) BEGIN swinstall SESSION
* Session started for user "root@hpux1". * Beginning Selection * Target connection succeeded for "hpux1:/". * Source: /tmp/AvamarClient-4.0.3-100.hpux11.parisc.depot * Targets: hpux1:/ * Software selections: hpuxclnt.hpuxclnt-exec,r=4.0.3-100,a=HP-UX_B.11.00_32/64 * Selection succeeded. * Beginning Analysis * Session selections have been saved in the file "/.sw/sessions/swinstall.last". * The analysis phase succeeded for "hpux1:/". * Analysis succeeded. * Beginning Execution * The execution phase succeeded for "hpux1:/". * Execution succeeded. NOTE: ======= More information may be found in the agent logfile (location is hpux1:/var/adm/sw/swagent.log). 10/29/07 07:48:53 PST END swinstall SESSION (non-interactive)
12
Chapter 3. Linux client

This section contains the following information for the Linux client: v System requirements. v Installing on page 14. v Upgrading on page 15. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 15. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Linux client.
Table 3. Minimum hardware and software requirements for the Linux client Hardware and software Operating systems Requirements v Red Hat Enterprise Linux AS/ES/WS Release 5, 4, and 3 (32-bit and 64-bit) v Red Hat Enterprise Linux AS/ES/WS Release 2.1 (32-bit) v Red Hat 9.0 and 8.0 (32-bit) v SuSE Linux Enterprise Server 10, 9, and 8 (32-bit and 64-bit) CPU File systems v x86 v ext2 v ext3 v JFS v ReiserFS RAM Hard drive space A minimum of 64 MB. A minimum of 100 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files. Network interface Web browsers 10baseT or higher, configured with the latest drivers for your platform, is required. Optional. Required in order to use Web Access download and restore features.
13
Table 3. Minimum hardware and software requirements for the Linux client (continued) Hardware and software Adobe Acrobat Reader Requirements 5.0 or higher. Available from www.adobe.com. Optional. Required in order to view online documentation.
Installing
The following steps are for downloading and installing the Linux client. If you are installing an upgrade, but not a full installation, see Upgrading on page 15. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. From the location where you saved the software, issue the following command as root:
[root@linux-server root]# rpm -ivh AvamarClient-4.0.3-xxx.rhel3.i386.rpm Preparing... ########################################### [100%] 1:AvamarClient ########################################### [100%] Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 3363 avagent.d Info: Client Agent started.
[root@rhel-test root]# /usr/local/avamar/bin/avregister === Client Registration and Activation This script will register and activate the client with the Administrator server. Enter Administrator server address (DNS name, not numeric IP): Replace_Hostname Enter the Axion server domain [clients]: <Press enter to accept default> avagent.d Info: Stopping Axion Client Agent (avagent)... avagent.d Info: Client Agent stopped. [ OK ] avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent.d Info: Client activated successfully. [ OK ] avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 3393 avagent.d Info: Client Agent started. [ OK ] Registration Complete.
Note: If you do not have your Administrator server address, contact the service support line at 1-866-237-9677 to receive it. After successful completion, inform your service provider that installation and activation of the client is complete.
14
Upgrading
The following steps are for installing an upgrade of your Linux client. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. Copy the following agent configuration files to the /tmp directory using the following commands: a. cp /usr/local/Avamar/var/avagent.cfg /tmp b. cp /usr/local/Avamar/var/p_cache.dat /tmp c. cp /usr/local/Avamar/var/f_cache.dat /tmp 4. Uninstall the old version by running the following commands: a. /etc/init.d/avagent stop b. /etc/init.d/avagent unactivate c. rpm -qa | grep AvamarClient d. rpm -e AvamarClient-X.X.X-XXX Where X.X.X-XXX is the version returned in the prior command. 5. Move the configuration files back to the original locations using the following commands: a. mv /tmp/avagent.cfg /usr/local/avamar/var b. mv /tmp/p_cache.dat /usr/local/avamar/var c. mv /tmp/f_cache.dat /usr/local/avamar/var 6. Install the new client by running the following command as root from the location where you saved the software:
# rpm ivh /tmp/AvamarClient-4.0.3-xxx.rhel3.i386.rpm
Substitute with the name of the rpm package you downloaded in Step 2. For example:
rpm -ivh AvamarClient-4.0.3-xxx.rhel3.i386.rpm Preparing... ########################################### [100%] 1:AvamarClient ########################################### [100%] Installation complete You may run /usr/local/avamar/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log avagent Info <5417>: daemonized as process id 3714 avagent.d Info: Client Agent started.
Chapter 3. Linux client
15
16
Chapter 4. Mac OS client

This section contains the following information for the Apple Mac OS client: v System requirements. v Installing. Special firewall considerations on page 18. v Upgrading on page 18. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 18. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Mac client.
Table 4. Minimum hardware and software requirements Hardware and Software Operating systems Requirements v Apple Mac OS X v10.5 Leopard v Apple Mac OS X v10.4 Tiger Hard drive space A minimum of 200 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. The hard drive space is used for local cache files. Network interface Web browsers Adobe Acrobat Reader 10baseT or higher, configured with the latest drivers for your platform, is required. Optional. Required in order to use Web Access download and restore features. 5.0 or higher. Available from www.adobe.com. Optional. Required in order to view online documentation.
Installing
The following steps are for downloading and installing the client. If you are performing an upgrade, but not a full installation, see Upgrading on page 18. 1. Link to the following document file containing the downloads to the client software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc
17
When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. To launch the setup program, double-click the file you have saved to your machine and then follow the step-by-step instructions of the installer program. Note: Select the standard installation directory when prompted in the installer program. 4. After the the setup program completes, perform the following actions: a. Open a terminal window:Finder > Applications > Utilities > Terminal b. In the terminal window, enter the following commands: 1) sudo su (provide the password for the administrator user) 2) cd /usr/local/avamar/bin 3) ./avregister <press enter> 5. When prompted, enter the following information: a. Administrator Server Address: REPLACE_HOSTNAME Note: If you do not have your administrator server address, contact the service support line at 1-866-237-9677 to receive it. b. Client Domain: clients After successful completion, inform your service provider that installation and activation of the client is complete.
Special firewall considerations

If you are running firewall software on a client computer (for example, ZoneAlarm, Norton, or McAfee), you must configure the firewall application to allow bi-directional communication between your Mac client and the backup server. This is normally accomplished by adding the Client Agent to an allowed or exceptions list.
Upgrading
The following steps are for installing an upgrade of your current Mac client: 1. Link to the following document file containing the downloads to the client software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. Open a terminal window and enter the following commands: a. sudo su (provide password for administrator account) b. cd /usr/local/avamar/bin c. ./avunistall.sh , then press enter. 4. Follow the installation instructions in the Installing on page 17 section.
18
Chapter 4. Mac OS client
19
20
Chapter 5. Solaris client

This section contains the following information for the Solaris client: v System requirements. v Installing. v Upgrading on page 23. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 23. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Solaris client.
Table 5. Minimum hardware and software requirements for the Solaris client Hardware and software Operating systems CPU Requirements v Solaris 10, 9, 8, 7, and 2.6 (32-bit and 64-bit) v SPARC v x86 (Solaris 10 only) File systems v UFS v VxFS RAM Hard drive space A minimum of 64 MB. A minimum of 200 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files. Network interface Web browsers Adobe Acrobat Reader 10baseT or higher, configured with the latest drivers for your platform, is required. Optional. Required in order to use Web Access download and restore features. 5.0 or higher. Available from www.adobe.com. Optional. Required in order to view online documentation.
Installing
The following steps are for downloading and installing the Solaris client. If you are installing an upgrade, but not a full installation, see Upgrading on page 23.
21
1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. From the location where you saved the software, issue the following command as root:
[root@solaris-server root]# pkgadd -d ./AvamarClient-4.0.3-xxx.Solaris8.pkg The following packages are available: 1 AVMRclnt Avamar Client (sparc) 4.0.3-xxx Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: <enter to accept default> Processing package instance <AVMRclnt> from /tmp/AvamarClient-4.0.3xxx.Solaris8.pkg> Avamar Client (sparc) 4.0.3-xxx This software is copyright EMC Corporation, 2001-2007. Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. Relocate install from /opt/AVMRclnt? [n] <enter to accept default> Directory to locate cache & log files [/var/avamar]: <enter to accept default> ## Executing checkinstall script. Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <AVMRclnt> [y,n,?] y Installing Avamar Client as <AVMRclnt> ## Executing preinstall script. ## Installing part 1 of 1. /opt/AVMRclnt/AvamarClient-License.txt /opt/AVMRclnt/bin/avagent.bin /opt/AVMRclnt/bin/avregister /opt/AVMRclnt/bin/avrunner /opt/AVMRclnt/bin/avscc /opt/AVMRclnt/bin/avtar /opt/AVMRclnt/bin/avtar.bin /opt/AVMRclnt/bin/unix.pin /opt/AVMRclnt/etc/AvamarClient-UpdateReplace.sh /opt/AVMRclnt/etc/avagent.d [ verifying class <apps> ]
22
/opt/AVMRclnt/lib/libstdc++.so.2.10.0 [ verifying class <libs> ] ## Executing postinstall script. Installation complete You may run /opt/AVMRclnt/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /opt/AVMRclnt/var/avagent.log avagent Info <5417>: daemonized as process id 23599 avagent.d Info: Client Agent started. Installation of <AVMRclnt> was successful.
[root@solaris-test root]# /opt/AVMRclnt/bin/avregister === Client Registration and Activation This script will register and activate the client with the Administrator server. Enter Administrator server address (DNS name,not numeric IP): Replace_Hostname Enter the Axion server domain [clients]: <Press enter to accept default> avagent.d Info: Stopping Axion Client Agent (avagent)... avagent.d Info: Client Agent stopped. avagent Info <5241>: Logging to /opt/AVMRclnt/var/avagent.log avagent.d Info: Client activated successfully. avagent Info <5241>: Logging to /opt/AVMRclnt/var/avagent.log avagent Info <5417>: daemonized as process id 23655 avagent.d Info: Client Agent started. Registration Complete.
Note: If you do not have your Administrator server address, contact the service support line at 1-866-237-9677 to receive it. After successful completion, inform your service provider that installation and activation of the client is complete.
Upgrading
The following steps are for installing an upgrade of your current Solaris client. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. Copy the following agent configuration files to the /tmp directory using the following commands: a. cp /var/avamar/avagent.cfg /tmp b. cp /var/avamar/p_cache.dat /tmp c. cp /var/avamar/f_cache.dat /tmp 4. Uninstall the old version by running the following commands: a. /etc/init.d/avagent stop b. /etc/init.d/avagent unactivate c. pkgrm AVMRclnt
23
The following package is currently installed: AVMRclnt Avamar Client (sparc) 3.7.1-100 Do you want to remove this package? y ## Removing installed package instance <AVMRclnt> This package contains scripts which will be executed with super-user permission during the process of removing this package. Do you want to continue with the removal of this package [y,n,?,q] y ## Verifying package dependencies. ## Processing package information. ## Executing preremove script. avagent.d Info: Client Agent not running. ## Removing pathnames in class <syms> ## Removing pathnames in class <dirs> ## Removing pathnames in class <mans> ## Removing pathnames in class <libs> /opt/AVMRclnt/lib/libstdc++.so.2.10.0 /opt/AVMRclnt/lib ## Removing pathnames in class <etcs> ## Removing pathnames in class <apps> /opt/AVMRclnt/etc/avagent.d /opt/AVMRclnt/etc/AvamarClient-UpdateReplace.sh /opt/AVMRclnt/etc /opt/AVMRclnt/bin/unix.pin /opt/AVMRclnt/bin/avtar.bin /opt/AVMRclnt/bin/avtar /opt/AVMRclnt/bin/avscc /opt/AVMRclnt/bin/avrunner /opt/AVMRclnt/bin/avregister /opt/AVMRclnt/bin/avagent.bin /opt/AVMRclnt/bin /opt/AVMRclnt/AvamarClient-License.txt /opt/AVMRclnt ## Removing pathnames in class <none> ## Updating system information. Removal of <AVMRclnt> was successful.
5. Move the configuration files back to the original locations using the following command: a. mv /tmp/avagent.cfg /var/avamar b. mv /tmp/p_cache.dat /var/avamar c. mv /tmp/f_cache.dat /var/avamar 6. Install the new client by running the following command as root from the location where you saved the software:
pkgadd -d ./AvamarClient-4.0.3-xxx.Solaris8.pkg The following packages are available: 1 AVMRclnt Avamar Client (sparc) 4.0.3-xxx Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: <enter to accept default> Processing package instance <AVMRclnt> from </tmp/AvamarClient-4.0.3-xxx.Solaris8.pkg> Avamar Client (sparc) 4.0.3-xxx This software is copyright EMC Corporation, 2001-2007.
24
Please read and agree to the End User License Agreement which will be placed in the base directory of the install as a file named AvamarClient-License.txt. Relocate install from /opt/AVMRclnt? [n] <enter to accept default> Directory to locate cache & log files [/var/avamar]: <enter to accept default> WARNING! Directory "/var/avamar" already exists! Confirm '/var/avamar' is the desired location. [n] y ## Executing checkinstall script. Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <AVMRclnt> [y,n,?] y Installing Avamar Client as <AVMRclnt> ## Executing preinstall script. ## Installing part 1 of 1. /opt/AVMRclnt/AvamarClient-License.txt /opt/AVMRclnt/bin/avagent.bin /opt/AVMRclnt/bin/avregister /opt/AVMRclnt/bin/avrunner /opt/AVMRclnt/bin/avscc /opt/AVMRclnt/bin/avtar /opt/AVMRclnt/bin/avtar.bin /opt/AVMRclnt/bin/unix.pin /opt/AVMRclnt/etc/AvamarClient-UpdateReplace.sh /opt/AVMRclnt/etc/avagent.d [ verifying class <apps> ] /opt/AVMRclnt/lib/libstdc++.so.2.10.0 [ verifying class <libs> ] ## Executing postinstall script. Installation complete You may run /opt/AVMRclnt/bin/avregister to register and activate this client with the Administrator server. avagent Info <5241>: Logging to /opt/AVMRclnt/var/avagent.log avagent Info <5417>: daemonized as process id 24180 avagent.d Info: Client Agent started. Installation of <AVMRclnt> was successful.
25
26
Chapter 6. Windows client

This section contains the following information for the Windows client: v System requirements. v Installing on page 28. Special firewall considerations on page 29. v Upgrading on page 29. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 29. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Windows client.
Table 6. Minimum hardware and software requirements Hardware and Software Operating systems Requirements v Microsoft Windows Vista Home basic v Microsoft Windows Vista Premium v Microsoft Windows Vista Enterprise 32bit v Microsoft Windows Vista Enterprise 64bit v Microsoft Windows XP Professional v Microsoft Windows Server 2003 v Microsoft Windows Server 2003 x64 Edition v Microsoft Windows Server 2000 (Service Pack 3) v Microsoft Windows Server 2000 v Microsoft Windows Server NT 4.0 (Service Pack 6a) IMPORTANT: The Avamar clients for Windows NT 4.0 and Windows 2000 rely on Columbia Data Products Open Transaction Manager (OTM) to backup open files. To avoid compatibility problems (particularly on Windows XP Professional, SP2), the OTM version included with the Avamar client for Windows should be used. File systems v FAT16 v FAT32 v NTFS RAM A minimum of 64 MB.
27
Table 6. Minimum hardware and software requirements (continued) Hardware and Software Hard drive space Requirements A minimum of 100 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. The hard drive space is used for local cache files. Open Transaction Manager (OTM) also allocates buffers equal to 1% of existing data on the C drive. Network interface Web browsers Adobe Acrobat Reader 10baseT or higher, configured with the latest drivers for your platform, is required. Optional. Required in order to use Web Access download and restore features. 5.0 or higher. Available from www.adobe.com. Optional. Required in order to view online documentation.
Installing
The following steps are for downloading and installing the Windows client. If you are performing an upgrade, but not a full installation, see Upgrading on page 29. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. To launch the setup program, double-click the .exe file after you have saved it to your machine, and then follow the step-by-step instructions through the installation wizard. IMPORTANT: v If you are installing the client on a Windows Vista OS, click Yes to any Vista security questions when installing the client. v When you reach the Avamar Client install complete wizard panel, do the following: For Windows XP or Windows 2003 systems, do not select any check boxes. For Windows NT or Windows 2000 systems, select only Install Open File Agent. v When you reach the InstallShield Wizard Complete panel, select the option to restart your system and then click Finish. (Your backups will not be able to protect open files until your system reboots.) 4. After completing all of the steps in the installation wizard and allowing your system to reboot, perform the following steps:
28
a. Right-click the new Remote data protection (Avamar) icon in your system tray and select Activate. b. Enter the following information in the Activate Client Setup window that displays: v Administrator Server Address: REPLACE_HOSTNAME If you do not have this address, call the services support line at 1-866-237-9677 to receive your Administrator Server Address. v Client Domain: clients c. Click Activate. When the process is complete, you will receive a message that activation was successful. After successful completion, inform your service provider that installation and activation of the client is complete.
Special firewall considerations

If you are running firewall software on a client computer (for example, Windows Firewall, ZoneAlarm, Norton, or McAfee), you must configure the firewall application to allow bi-directional communication between your Windows client and the backup server. This is normally accomplished by adding the Client Agent to an allowed or exceptions list. By default, the client programs are installed at C:\Program Files\avs\bin\ avagent.exe and C:\Program Files\avs\bin\avtar.exe.
Upgrading
The following steps are for installing an upgrade of your current Windows client. 1. Link to the following document file containing the downloads to the client software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5FileDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the downloads listed, click the ftp link associated to your operating system. When prompted, click Save in order to save the client software download. 3. To launch the setup program, double-click the .exe file after you have saved it to your machine, and then follow the step-by-step instructions through the installation wizard. IMPORTANT: For the following wizard panels, make sure to enter these specific options: v In the first wizard panel, select Upgrade current installation to the latest version. Do not select the option to remove current installed version. v In the Avamar Client install complete wizard panel, do not select any check boxes. (Do not select to install the Open File Agent.) Click Finish to complete the upgrade. The upgrade is now complete, and your regularly scheduled backups will continue to run.
Chapter 6. Windows client
29
30
Chapter 7. MS Exchange Information Store agent

This section contains the following information for the Microsoft Exchange Information Store: v System requirements. v Installing on page 32. v Upgrading on page 32. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 32. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Exchange Information store.
Table 7. Minimum hardware and software requirements for the Exchange Information Store Hardware and software Operating systems Requirements v Microsoft Windows Server 2003 64-bit Service Pack 1, or higher v Microsoft Windows Server 2000 Service Pack 2, or higher Service Pack 3, required for Exchange Server 2003 File systems v v v RAM Hard drive space FAT16 (not compatible with Exchange Server 2003) FAT32 (not compatible with Exchange Server 2003) NTFS
A minimum of 64 MB. A minimum of 100 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The Exchange Server client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files.
Network interface Web browser
10baseT or higher, configured with the latest drivers for your platform, is required. Supported browsers: v Internet Explorer 6.0 v Netscape 6.3.0 Optional. Required for use of Web access download and restore features.
31
Table 7. Minimum hardware and software requirements for the Exchange Information Store (continued) Hardware and software Adobe Acrobat Reader Requirements 5.0 or higher; available from www.adobe.com Optional. Required for viewing online documentation. Other software Supported Microsoft Exchange Servers: v Exchange Server 2007 (Service Pack 1, or higher) v Exchange Server 2003 v Exchange Server 2000
Installing
IMPORTANT: The Windows File system client must be installed before installing the Exchange agent. The following steps are for installing the Exchange Information Store client. 1. Log on to the Exchange Server with a Domain Administration account and open a browser in order to link to the following document file containing the list of downloads for the agent software. ftp://ftp.arsenaldigital.com/Avamar/RDP2.5DatabaseAgentDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the list of Exchange agent downloads, click the ftp link associated to your operating system. When prompted, click Save in order to save the software download to a temporary directory. 3. To launch the setup, double-click the software download (.exe file) that you saved from the previous step, and follow instructions from the installation wizard. After successful installation, inform your service provider that the Exchange agent is installed.
Upgrading
IMPORTANT: The Windows File System client must be upgraded prior to upgrading the Exchange agent. The following instruction steps are for upgrading your current version of Exchange Information Store. 1. Log on to the Exchange Server and open a browser in order to link to the following document file containing the list of downloads for the agent software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5DatabaseAgentDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the list of Exchange agent downloads, click the ftp link associated to your operating system.
32
When prompted, click Save in order to save the software download to a temporary directory. 3. To launch the setup, double-click the software download (.exe file) that you saved from the previous step, and follow instructions from the installation wizard to Upgrade your current installation. Ensure that you select Upgrade when using the installation wizard. After the upgrade is complete, your regularly scheduled backups will continue to run.
Chapter 7. MS Exchange Information Store agent
33
34
Chapter 8. MS Exchange agent

This section contains the following information: v System requirements. v Configuring the MS Exchange Server mailbox level agent on page 36. v Upgrading the MS Exchange Server mailbox level agent on page 38. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading the MS Exchange Server mailbox level agent on page 38. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the Microsoft Exchange agent.
Table 8. Minimum hardware and software requirements for the Microsoft Exchange agent Hardware and software Operating systems Requirements v Microsoft Windows Server 2003, 64-bit Service Pack 1, or higher v Microsoft Windows Server 2000 Service Pack 2, or higher Service Pack 3, required for Exchange Server 2003 File systems v v v RAM Hard drive space FAT16 (not compatible with Exchange Server 2003) FAT32 (not compatible with Exchange Server 2003) NTFS
A minimum of 64 MB. A minimum of 100 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The Exchange client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files.
35
Table 8. Minimum hardware and software requirements for the Microsoft Exchange agent (continued) Hardware and software Adobe Acrobat Reader Requirements 5.0 or higher; available from www.adobe.com Optional. Required for viewing online documentation. Other software Supported Microsoft Exchange Servers: v Exchange Server 2007 (Service Pack 1, or higher) v Exchange Server 2003 v Exchange Server 2000
Configuring the MS Exchange Server mailbox level agent

IMPORTANT: Before configuring the mailbox level backups, you must install and configure the following on your system: v Windows File System client. v Exchange Information Store agent. Note: Even if you do not intend to perform Information Store backups, you must install the Exchange Information Store agent before configuring the Exchange Server mailbox level agent. The following are steps for configuring the Exchange Server mailbox level agent: 1. Create a user called AvamarBackupUser in the domain where the Exchange Server is located. Provide this user with the following Member Of privileges. v Domain Users. v Domain Admin. v Exchange Domain Servers. v Backup Operators. v Exchange Organization Administrators. (This only applies to Exchange Server 2007.) v Exchange Install Domain Servers (This only applies to Exchange Server 2007.) Note: Exchange Server 2007 only requires the items identified in the list. 2. Set the following parameters for user account AvamarBackupUser: v User cannot change password. v Password never expires. v Select to create an Exchange mailbox for this user account. v Add FullAccess permission to the AvamarBackupUser account using the Exchange Management Shell by entering the following command on a single line:
Get-Mailbox -server SERVERNAME | Add-MailboxPermission -User AvamarBackupUser -AccessRights FullAccess | Format-List
3. Log on to the Exchange Server using the AvamarBackupUser account. 4. Configure the Remote data protection (Avamar) Client Agent service to be run by the AvamarBackupUser.
36
a. Open the Computer Management window: Click Start, then right-click My Computer and select Manage. The Computer Management window displays. b. Stop the Remote data protection (Avamar) Client Agent service: On the right pane of the Computer Management window, click Services and Applications > Services > Avamar Client Agent, then click Stop. c. After the service has stopped, right-click Avamar Client Agent service, then select Properties. d. From the Avamar Client Agent Properties window, select the Log On tab. Configure the Log On entry fields. 1) This account: <DOMAIN>\AvamarBackupUser. 2) Password: <Password_that_was_created_for_this_user>. 3) Click Apply. e. Restart the Remote data protection (Avamar) service from the Avamar Client Agent Properties window. 1) Select the General tab. 2) Click Start. 3) Click OK. 5. Create an AvamarBackupProfile MAPI profile in order to perform mailbox level backups. a. For Exchange Server 2007 only: The MAPI libraries are not provided with Exchange Server 2007 and must be downloaded prior to completing the remaining steps. Use the following URL to obtain and install the MAPI Libraries: http://www.microsoft.com/downloads/ details.aspx?FamilyID=E17E7F31-079A-43A9-BFF2-0A110307611E &displaylang=en b. Log into the Exchange Server using the new AvamarBackupUser account. c. Open a command prompt and perform the following commands: 1) Change the directory to the bin directory: cd C:\Program Files\avs\bin 2) Run the following utility: profman.exe The MAPI Profile Manager window displays. d. In the MAPI Profile Manager window, perform the following actions: 1) Click New Profile. 2) Enter AxionBackupProfile in the Profile Name field. 3) Click OK. e. In the MAPI Profile Manager, perform the following actions: 1) Highlight the newly created profile and then click Add Service. 2) Select the MSEMS (Microsoft Exchange Server) from the list and then click OK. 3) Enter the name of your Exchange server in the Microsoft Exchange server field and then click OK. f. To close the MAPI Profile Manager window, select File > Exit from the menu bar. 6. Activate the mailbox for the user you have created by using one of the following methods: v Access the AvamarBackupUser account via Outlook. v Send the AvamarBackupUser account an email.
Chapter 8. MS Exchange agent
37
After successfully completing these configuration steps, the client is available for the initial backup of the Exchange Mailboxes. Complete the following final steps for providing Remote data protection service to your Exchange Mailboxes. 1. Inform your service provider that you have successfully configured the agent for Exchange Mailboxes. 2. Provide your service provider with a list of the mailboxes you want to back up. This list will be used to set up your policies. Your provider will notify you after your client has successfully completed its initial Exchange Mailbox backup. Backups will begin to occur according to your backup schedule, and your Exchange Mailboxes will be protected.
Upgrading the MS Exchange Server mailbox level agent

IMPORTANT: The Windows File System client must be upgraded prior to upgrading the Exchange plug-in. Upgrading the Exchange Information Store agent will automatically upgrade the Mailbox level agent. Refer to the Information Store (Upgrading on page 32) for these steps. No further steps are required for the Mailbox level agent.
38
Chapter 9. MS SQL agent

This section contains the following information for the Microsoft SQL agent: v System requirements. v Installing on page 40. v Upgrading on page 40. After reviewing System requirements, if you are performing an upgrade, but not a full installation, see Upgrading on page 40. Note: For this section, the client version is referenced as 4.0.3-xxx. This version might vary from your version, but the installation steps will be the same.
System requirements
The following table contains the requirements for installing and upgrading the MS SQL agent.
Table 9. Minimum hardware and software requirements for the MS SQL agent Hardware and software Operating systems Requirements v Microsoft Windows Server 2003, 64-bit Service Pack 1, or higher v Microsoft Windows Server 2003, 32-bit v Microsoft Windows Server 2000 Service Pack 2, or higher v Microsoft Windows NT 4.0 Service Pack 6a, or higher File systems v v v RAM Hard drive space FAT16 FAT32 NTFS
A minimum of 64 MB. A minimum of 100 MB permanent hard drive space is required for software installation. However, 1 GB is recommended. The Avamar SQL Server client software also requires an additional 12 MB of permanent hard drive space for each 64 MB of physical RAM. This space is used for local cache files.
39
Table 9. Minimum hardware and software requirements for the MS SQL agent (continued) Hardware and software Adobe Acrobat Reader Requirements 5.0 or higher; available from www.adobe.com Optional. Required for viewing online documentation. Other software v Microsoft SQL Server 2005, 32-bit (on Windows Server 2003, 32-bit) v Microsoft SQL Server 2005, 64-bit (on Windows Server 2003 x64 SP1) v Microsoft SQL Server 2000 v Microsoft SQL Server 7.0
Installing
IMPORTANT: The Windows File system client must be installed before installing the SQL agent. The following steps are for installing the MS SQL backup agent: 1. Log on to the SQL server and open a browser in order to link to the following document file containing the list of downloads for the agent software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5DatabaseAgentDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the list of SQL agent downloads, click the ftp link associated to your operating system. When prompted, click Save in order to save the software download to a temporary directory. 3. To launch the setup, double-click the software download (.exe file) that you saved from the previous step, and follow instructions from the installation wizard. After successful installation, inform your service provider that the SQL agent is installed.
Upgrading
IMPORTANT: The Windows File System client must be upgraded prior to upgrading the SQL plug-in. The following instruction steps are for upgrading your current version of the SQL agent. 1. Log on to the SQL server and open a browser in order to link to the following document file containing the list of downloads for the agent software: ftp://ftp.arsenaldigital.com/Avamar/RDP2.5DatabaseAgentDownloadList.doc When prompted, click Open to view the document file (which contains the download list). 2. From the list of SQL agent downloads, click the ftp link associated to your operating system.
40
When prompted, click Save in order to save the software download to a temporary directory. 3. To launch the setup, double-click the software download (.exe file) that you saved from the previous step, and follow instructions from the installation wizard to Upgrade your current installation. Ensure that you select Upgrade when using the installation wizard. After the upgrade is complete, your regularly scheduled backups will continue to run.
Chapter 9. MS SQL agent
41
42
Part 2. Command-line Interface (CLI) Guide

This section contains a summary of the CLI, including the following information: v Chapter 10, Overview, on page 45. Operating system information on page 45. Required information on page 45. v Chapter 11, Examples, on page 47.
43
44
Chapter 10. Overview

This section contains examples on how to restore files using the command-line interface (CLI) to the backup agent. The CLI instructions apply only to file-level restores. The CLI instructions do not apply when backups are performed with a hot agent because backups performed with a hot agent must be pushed to the agent. The CLI uses the avtar command to restore files. From a command prompt, enter avtar --help to view valid options for the avtar command.
Operating system information

The CLI instructions are OS independent. The syntax is the same for all supported operating systems. However, some options do not apply to all operating systems. The avtar executable is located in the following directories by default. v For AIX and Linux systems: /usr/local/avamar/bin/avtar. v For HP-UX and Solaris systems: /opt/AVMRclnt/bin/avtar. v For Windows systems: C:\Program Files\Avamar\bin\avtar.exe or C:\ProgramFiles\avs\bin\avtar.exe.
Required information
You need the following information before using the CLI to perform file restores. v Account restore user name. For example: myAccount. v Account client path. For example: /MyCompany/servers/myclient. v Account restore password. Contact your Service Provider if you do not have this information.
45
46
Chapter 11. Examples

This section contains examples using the command-line interface for restoring files and folders. Example 1: The file in /etc/hosts was modified incorrectly and needs to be restored as it existed on October 12, 2008. 1. Use the following command to list all the backups from which you can restore:
# avtar --backups --id=myAccount@/MyCompany/servers/myclient
where myAccount is the account restore user name, and /MyCompany/servers/ myclient is the account client path. 2. The system prompts you for the account password and lists the available backups that you can restore from. 3. The output in this example includes the following line for the backups performed on October 12:
2008-10-12 01:20:51 144 1am-ADSW-Lab-1192165201608 203753937K Unix /var/avamar
Note: The third field 144 represents the backup sequence number that identifies the specific backup to restore for 2008-10-12 (October 12th). 4. To perform the restore, enter the following command: Note: In this document, the command might appear on more than one line. However, the command should be issued on one line.
# avtar -x /etc/hosts --labelnumber=144 --target=/tmp id=myAccount@/MyCompany/servers/myclient
This command will restore the file that was backed up in the /etc/hosts directory on October 12th, and puts the file into the /tmp directory, which is specified in the --target option. 5. The command will prompt you to enter the account password before continuing with the restore. After the restore is complete, you can view the file in the /tmp directory to ensure the file is correct before replacing it in the /etc/hosts directory. Example 2: Several files were removed and modified incorrectly from the C:\apps directory. The following steps describe how to restore the entire folder and overwrite any existing files from the data in the backup, using the backups command: 1. Issue the command to list the available backups to restore from.
# avtar --backups --id=myAccount@/MyCompany/servers/myclient
2. Check the contents of C:\apps from the selected backup. For the following example, the backup sequence number that is selected is 20:
# avtar -t C:\apps --id=myAccount@/MyCompany/servers/myclient --labelnumber=20
3. To perform the restore, enter the following command: Note: In this document, the command might appear on more than one line. However, the command should be issued on one line.
47
# avtar -x C:\apps --labelnumber=20 --target=C:\apps --id=myAccount@/MyCompany/servers/myclient --existing-file-overwrite-option=modified
For this command, the following parameters are used: v -x : Process a restore operation. v C:\apps : Specifies the directory path of the files to restore from the backup. v --labelnumber : Option to specify which backup to restore from. v --target : Option to specify where to restore the files to. v --id : Specifies the restore ID and client path. v --existing-file-overwrite-option=modified : In this case, the option is to overwrite files if the file from the backup is different (modified). To view other valid options for the avtar command, enter avtar --help from a command prompt.
48
Part 3. Windows Web Restore Guide

This section contains the following information on how to use the Web restore function: v Chapter 12, Overview, on page 51. v Chapter 13, Getting started, on page 53. v Chapter 14, Restoring files using Web restore, on page 55. v Chapter 15, Other features, on page 57. v Chapter 16, Troubleshooting and known limitations, on page 61.
49
50
Chapter 12. Overview

The Remote data protection backup client enables your files to be transferred securely to IBM backup servers. If you have not done so already, you will need to activate the client to the backup server that was designated to you. IBM provides you with a user name, password, and client path for user-initiated restores. Keep this information in a secure place so that you can log in and restore your data when necessary.
Backup features
Your computer is backed up daily on a scheduled basis according to the backup window that you were assigned. The initial backup will capture all data within your file targets. Every day your backup captures only the parts of the data that have changed in those target directories and transmits them to the Remote data protection system. This proves to be more network-efficient than transferring the entire file if it changes. The following is a list of features that Remote data protection provides: v Daily backups for servers on your network to a secure and remote location. v Multiple Retention Points available for restore. v Secure, bandwidth efficient, network-based data protection service using your existing IP network. v Fully managed service that includes hardware, software, expert staffing, and 24/7 monitoring and management. v Usage-based monthly billing. v Windows open file support using Continuous Data Protection's (CDP's) OTM software. v Consistent, automated backups. v Instant customer self-service Web-based restores. v Online portal access to view your usage information. For supported operating systems, see Part 1, Installation and Upgrade Guide, on page 1.
51
52
Chapter 13. Getting started

Follow the procedures in this section for getting started.
Activate the backup client

The following are steps to activate the backup client: in the system tray 1. Right-click the Remote data protection (Avamar) icon and select Activate. The Activate Client Setup window opens. 2. In the Activate Client Setup window, enter the Administrator Server Address and Client Domain, which your service provider gave you. Then click Activate. After completing these steps, the remote backup client is installed and activated. It then automatically backs up the client machines target directories according to the designated schedule (usually daily). From the client program you can view your backup history, cancel a backup, and navigate to the Web restore page.
View recent backup history

Double-click the icon in the system tray for the backup agent. A window displays that contains a record of your recent backups. You can view when you had successful backups, the size of the backups, and the duration for the backups to complete. The most effective way to view your successful backup history is by using the method discussed in the Web restore section (Procedure for restoring files on page 55). This displays a calendar view of your retained successful backups.
Check for your client path

The client path is the location of your client on the backup server. The client path information is necessary when logging into the Web restore page. The following are steps to obtain the client path: in the system tray and select About. 1. Right-click the icon 2. View the value labeled Account Path to identify the client path.
Backup schedule
After your initial backup is complete, you will be notified of your backup schedule. Typically this will be a daily backup within a certain backup window. To have your backup scheduled for a different time, contact your service provider. If you are offline when your backup is scheduled to start, the remote backup system makes backup attempts until the end of your backup window schedule.
53
Backup retention
Your backups are kept according to the retention schedule that you purchase. For example, if your backup plan gives you 8 daily, 5 weekly, and 4 monthly backups, you can restore from any of those times. To change your retention, contact your service provider.
54
Chapter 14. Restoring files using Web restore

By utilizing the user-initiated restore feature, you can retrieve up to 1 GB of files at a time through a Web browser that can reach the remote backup system. Your service provider will supply you with your login information. IMPORTANT: To restore more than 1 GB of files, contact your service provider to request a restore or initiate multiple consecutive restores through the Web interface.
Logging in
After you activate your agent and contact your service provider, you are issued a Web restore account login. The user name, client path, and password are used to log into the Web restore page. Use the following steps to log into the Web restore pages: 1. Access the Web restore page. v To access the Web restore page from the machine with the backup agent, right-click the Remote data protection (Avamar) icon Then select Restore. in the system tray.
v To access the Web restore page from a different machine that can reach the Remote data protection backup server, open Internet Explorer and go to http://systemname.IBMdigital.com. (Substitute the server name provided for activation in the systemname portion of the URL.) 2. In the logon window, enter the following information: account user name, client path, and password. Then click Log In.
Procedure for restoring files

The following procedure contains the steps for restoring files from the backup data. 1. Navigate to the backup file. a. From the calendar display on the Web restore page, select the date of the backup that you want to restore. Days that are underlined have backups available for restore. b. If there is more than one backup on the date that you selected, then select which backup you want to restore for that date. c. To navigate to the file you want to restore, click the drive (for example, C:/) and drill down until the file is visible. 2. Preview files. To view the file that you want to restore in the browser window before icon next to the file. The file opens in the downloading it, click the browser if a viewer is available. (The file is downloaded to the local hosts temp folder when using the preview function.) 3. Download files. To download a file in .zip format, perform the following steps: icon next to the backup file you want to restore. a. Click the b. Select the location where you want to save the file.
55
c. Click Save. It may take several minutes for the server to compress the file into .zip format.
Provider-initiated restores
To restore a file that is greater than 1 GB in size, contact your service provider and request a provider (administrator) initiated restore. When requesting a restore, have the following information available when you call or email your service provider: v The date of the backup containing the file or files you want restored and the time of the backup if multiple backups occurred on that date. v The full path of the files and folders that you want restored. For example: C:\My\Documents\file.txt. v The location to restore the files on your machine.
56
Chapter 15. Other features

In previous sections, the following features of Remote data protection have been discussed: v Activation of the client agent software. v Initial backup of the system. v Restore capabilities. This section contains information on other features that the Remote data protection (Avamar) client also supports. To access these features, open the client window (Figure 1) using the following steps: 1. Right-click the Remote data protection (Avamar) icon 2. Then select Open. in the system tray.
Figure 1. Remote data protection (Avamar) client window
View
After opening the Remote data protection (Avamar) client window, click View and select from the following items in the menu: Work Order Status, Agent Log, Console Log, About, and Close. v Work Order Status Work Order Status displays the status of a backup in progress or the results of a prior backup. Work Order Status contains the following information. Work Order Info - Work Order ID: assigned by the backup service. - Plugin ID: identifies the operating system from which data has been saved. - Started: displays the date and time when the backup began. - Duration: the length of time for the backup to complete. Click Work Order Log to display a report of the details that occur during the backup sequence.
57
If there are errors during a backup, the Global Support Center might ask for a copy of this log to troubleshoot the cause of the error. Plugin Info - Status: displays the status of the backup. - Exit Message: identifies whether the backup operation succeeds or fails. v Agent Log The Agent Log reports the details of what occurs during the backup sequence from the Agent side, which is your side, of the connection. If there are any errors for a backup, the Global Support Center might ask for a copy of this log to troubleshoot the cause of the error. v Console Log The Console Log reports the details of what occurs during the backup sequence. If there are errors during a backup, the Global Support Center might ask for a copy of this log to troubleshoot the cause of the error. v About This view displays information about the software agent installed on the system you are backing up. It includes the agent release information such as the build and version numbers. It provides details around the backend service host name, account path TCP port information, the status of both the client agent and the Administrator. It also reports if there are warnings, errors, or fatal messages that have been logged to the Agent Log.
Actions
After opening the Remote data protection (Avamar) client window, click Actions and select from the following items in the menu: Snap Up Now (Backup Now), Restore, and Activate. v Snap Up Now (Backup Now) The Snap Up Now functionality is not supported. If a backup is required at a time outside of the standard schedule, contact your service provider. v Restore To restore a file, folder, or the complete system data, use the Restore function. 1. By selecting Restore, you are prompted to enter the following logon information provided to you by your service provider: Account, Client Path, and Password. 2. Click Log In to log on to the Online Restore Engine. 3. From the Online Restore Engine window, you can perform the following tasks: To restore the entire data set: a. Click the yellow Restore icon. b. Drill down to a file or folder, click the directory Names until you get to the folder that you want, then click the corresponding Download icon. To restore a file: a. Click the day on the calendar to view the data files backed up. b. Continue to drill down to the folder that contains the file you need to restore. c. After finding the file, you have two options: Click the icon to preview the file before downloading it.
58
Click the icon to download the file. v Activate Use the Activate function after the initial client agent install. Activate is the mechanism used to start the backup service. Your backup service provider activates the client software for you. In the rare instance that you need to re-activate, contact your backup service provider's Global Support Center for further instructions.
Options
After opening the Remote data protection (Avamar) client window, click Options and select from the following items in the menu: Display reminder if no snapups (backups) in 24 hours, Display progress bar, Display balloon messages, and Advanced. v Display reminder if no Snapups in 24 hours A check mark indicates that this option is selected. Once selected, a window panel displays to indicate if a snapup (backup) was missed within the previous 24 hour period. v Display progress bar A check mark indicates that this option is selected. Once selected, a window panel displays to indicate the progress of a backup. v Display balloon messages A check mark indicates that this option is selected. Once selected, a window panel displays to indicate that an automated backup has initiated. v Advanced Select either of the advanced options: Restart Client Agent During a troubleshooting exercise, if it is determined that the client agent must be restarted or reinitialized, click Restart Client Agent to stop and restart the client agent. Stop Client Agent During a troubleshooting exercise, if it is necessary to stop the client agent, then click Stop Client Agent.
Chapter 15. Other features
59
60
Chapter 16. Troubleshooting and known limitations

The following list contains troubleshooting information and known limitations when performing backups and restores. v Verify that your firewall is not blocking ports and verify DNS "lookup" capability With your system administrator, verify that the following ports (Table 10) are open and not blocked by your firewall.
Table 10. List of ports that must be open Port 443 Protocol TCP Incoming / Outgoing Outgoing Application Baseline Description HTTPS connection to secure web server. Client to server; proprietary communication. Client to Administrator server. Client to server (SSL).
27000
TCP
Outgoing
Baseline
28001
TCP
Outgoing
Baseline
29000
TCP
Outgoing
Baseline
Also, verify DNS lookup capability. If there is no DNS lookup capability, you must manually add two hostnames. v One operation per client limitation The client agent is able to execute only one operation at a time. For example, multiple simultaneous backups or restores for the same client are not possible. v 1 GB size limitation to user-initiated restores User-initiated restores through the Web interface should be 1 GB or less. If more than 1 GB of data must be restored, you can perform multiple restores or contact your service provider for an administrator-pushed restore with no file size limits. v Error occurs when handling directory with %2f and %3a in the file name When using Web restore, the client agent generates errors if a file or directory name that is being remotely browsed contains sequences such as: %2f or %3a. To resolve this problem, rename these files or directories if these files will be browsed remotely.
61
62
Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the users responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
63
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 3039 Cornwallis Road PO Box 12195 Research Triangle Park, NC 27709 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBMs suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not
64
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. If you are viewing this information softcopy, the photographs and color illustrations may not appear.
Notices
65
66
Trademarks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both: Adobe, Acrobat, Portable Document Format (PDF), PostScript, and all Adobe-based trademarks are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.
67
68
Program Number: 6948-84B
Printed in USA

RDP Server

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RDP Server

Uploaded by

Copyright:

Available Formats

IBM Information Protection Services

Remote Data Protection for Servers: Installation and Restore Guide

Part 1. Installation and Upgrade Guide . . . . . . . . . . . . . . . 1

Part 2. Command-line Interface (CLI) Guide . . . . . . . . . . . . 43

Chapter 2. HP-UX client . . . . . . . . 9

Chapter 11. Examples . . . . . . . . 47

Chapter 3. Linux client . . . . . . . . 13

Part 3. Windows Web Restore Guide . . . . . . . . . . . . . . . 49

Chapter 4. Mac OS client . . . . . . . 17

Chapter 13. Getting started . . . . . . 53

Chapter 5. Solaris client . . . . . . . 21

Chapter 14. Restoring files using Web restore . . . . . . . . . . . . . . . 55

Chapter 6. Windows client . . . . . . 27

Chapter 15. Other features . . . . . . 57

Chapter 7. MS Exchange Information Store agent . . . . . . . . . . . . . 31

Chapter 16. Troubleshooting and known limitations . . . . . . . . . . 61 Notices . . . . . . . . . . . . . . 63

Chapter 8. MS Exchange agent . . . . 35

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Part 1. Installation and Upgrade Guide

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Chapter 1. AIX client

Copyright IBM Corp. 2008

# Avamar Axion client 4.0.3-xxx..

Remote Data Protection for Servers

# Avamar Axion client 3.7.1-100...

Selected to be deinstalled, of which: 1 Passed pre-deinstall verification

# Avamar Axion client 4.0.3-xxx..

Remote Data Protection for Servers

Chapter 1. AIX client

Remote Data Protection for Servers

Chapter 2. HP-UX client

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Chapter 2. HP-UX client

is hpux1:/var/adm/sw/swagent.log). ======= 10/29/07 07:39:07 PST END swremove SESSION (non-interactive)

Remote Data Protection for Servers

Chapter 3. Linux client

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Chapter 3. Linux client

Remote Data Protection for Servers

Chapter 4. Mac OS client

Copyright IBM Corp. 2008

Special firewall considerations

Remote Data Protection for Servers

Chapter 4. Mac OS client

Remote Data Protection for Servers

Chapter 5. Solaris client

Remote Data Protection for Servers

Chapter 5. Solaris client

Remote Data Protection for Servers

Chapter 5. Solaris client

Remote Data Protection for Servers

Chapter 6. Windows client

Copyright IBM Corp. 2008

Remote Data Protection for Servers

Special firewall considerations

Chapter 6. Windows client