Blog Archives

Installing and configuring ArcServe 16.1 agent on Fedora 20

A quick note about CA ArcServe Universal Agent 16.1 installation of Fedora 20 (x64):

$ sudo mount -o loop  ArcServe16SP1.iso /mnt/dvd
$ cd /mnt/dvd/ArcServe16SP1/DataMoverandAgent/Linux
$ sudo ./install

You’ll be greeted with:

Cannot identify your Linux distribution or it is not yet supported.

Important! You are installing UNIX and Linux Data Mover on a system that is 
running an operating system that is not currently supported by ARCserve. 
To check the latest list of supported operating systems, go to ca.com/support. 
If you continue, be aware that unexpected results could occur.

Do you want to continue? (YES/NO):(default: NO) YES

...
Read the license terms
...

ENTER YES (Y) TO ACCEPT THE TERMS AND CONDITIONS OF THIS AGREEMENT AS SET 
FORTH ABOVE AND PROCEED WITH THE INSTALLATION PROCESS.

ENTER NO (N) TO HALT THE INSTALLATION PROCESS.

Please enter your choice:[Y|N] (default: N) Y


Do you want to view the installation notes? (y/n):(default: y) n

Preparing for the installation, please wait...| 

The following products are available to install:


#####################################################################
#       ARCserve Installation Options
#####################################################################
#  1. CA ARCserve Backup for Linux Data Mover                               (ABdatmov)
#  2. CA ARCserve Backup for Linux Client Agent                             (ABagntux) 
#  3. CA ARCserve Backup for Linux Agent for Oracle                         (ABora)
#  4. CA ARCserve Backup for Linux Enterprise Option for SAP R/3 for Oracle (ABsap)
#                                                                       
#  0. Quit                                                              
#####################################################################

Note: Client Agent will be installed automatically if Data Mover is selected.
Please enter your selection separated by "," For example: 1,2. Press Enter to select the default components (E.g. Data Mover, Client Agent)...

Your choices are: 2

lease specify the installation path of Client Agent for Linux                   (default: /opt/CA): <ENTER>

The following program will be installed:

  . Install Client Agent for Linux                     (ABagntux)      ==> [ /opt/CA/ABuagent ]

Are you sure? (y)es/(n)o/(q)uit: y


All CA ARCserve Backup agents can be configured for automatic startup 
and shutdown as part of your operating system startup and shutdown.
Do you want to enable automatic startup and shutdown of all backup agents? [y|n]:(default: y) y

Checking available space in /opt/CA                           ==> [ OK ]


Installation log file is                           ==> [ /tmp/ARCserveInstall123113-0938.log ]

    Common Agent Module                      (ABcmagt)       ==> [ INSTALL SUCCESSFUL ]
    Client Agent for Linux                   (ABagntux)      ==> [ INSTALL SUCCESSFUL ]

###########################################################################

    Installation log file is                      ==> [ /tmp/ARCserveInstall123113-0938.log ]
###########################################################################

Do you want to view the readme? [y|n]:(default: y) n

Configuration:

[alesk@fedora20 CA]$ ls -al /opt/CA
total 8
drwxr-xr-x  4 root root   35 Dec 31 09:42 .
drwxr-xr-x. 6 root root   62 Dec 31 09:42 ..
drwxr-xr-x  4 root root 4096 Dec 31 09:42 ABcmagt
drwxr-xr-x  4 root root 4096 Dec 31 09:42 ABuagent


$ sudo nano /opt/CA/ABcmagt/agent.cfg

[0]
#[LinuxAgent]
NAME      LinuxAgent
VERSION   16.0
HOME      /opt/CA/ABuagent
#ENV      CA_ENV_DEBUG_LEVEL=4
ENV       AB_OS_TYPE=FEDORAPROJECT_X86_64
ENV       UAGENT_HOME=/opt/CA/ABuagent
#ENV       LD_ASSUME_KERNEL=2.4.18
ENV       LD_LIBRARY_PATH=/opt/CA/ABcmagt:$LD_LIBRARY_PATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
ENV       SHLIB_PATH=/opt/CA/ABcmagt:$SHLIB_PATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
ENV       LIBPATH=/opt/CA/ABcmagt:$LIBPATH:/SharedComponents/lib:/opt/CA/ABuagent/lib
BROWSER   cabr
AGENT     uagentd
MERGE     umrgd
VERIFY    umrgd
NOPASSWORD                      <<< ADDED
CAUSER  A:alesk N:root          <<< ADDED

[36] DISABLED
#[ABcmagt]
NAME      ABcmagt               
HOME      /opt/CA/ABcmagt
NO_HOSTS_EQUIV=1                <<< ADDED
#TCP_PORT  6051
#UDP_PORT  6051
#UDP_BCAST_PORT  41524
#DOS_MAXITEMS    1000
#DOS_DEFAULTTIMEOUT   30

As you can see all that I did was a couple of changes in agent.cfg file:

NOPASSWORD .... enable single user mode wihch is needed for ACLs
CAUSER     .... Access Control List (A=Allow access, N=Deny access)
NO_HOSTS_EQUIV=1   ... disable UNIX/Linux host equiv. authentication

Commands to start/stop CA agent:

$ sudo /etc/init.d/bab_agent start
$ sudo /etc/init.d/bab_agent stop
Advertisements

ArcServe 16 – enabling cabatch capability for DBA

We’re planning to replace our aging backup server running CA ArcServe 11.5 with the latest and bloodiest greatest ArcServe 16.0. My role in this migration is to ensure that our existing scripts that rely on cabatch command line tool works as expected.
Our test env. configuration consists of:

  • ArcServe 16 standalone server installed on Windows 2008 R2 x64 (let’s call it WINBACKUPSRV)
  • Windows 7 (x64) workstation that backup Operator uses to send backup jobs to ArcServe backup server (let’s call it WIN7BACKUP)

All backup scripts (.asx files) are prepared on backup server by a DBA. Backup operator must be able to submit backup jobs (*.asx files) to ArcServe, which means we need to create caroot equivalence for him/her.

1) SERVER SIDE


Installation of ArcSerce 16 is not covered here, it’s enough to summarize options that were installed on WINBACKUPSRV:

CA-ArcServe-last-warning

and the build version:

CA-Arcserve-about

In my case ArcServe 16 was installed under local Administrator account and this local account is automatically granted “ArcServe Administrator” role. Note that Roles were introduced with ArcServe 12.


Note: “User profiles Manager” is shown only if you loged on to ArcServe with caroot account!!


You should keep your caroot account information secret, don’t allow a bunch of administrators to use this account for day to day job activities on backup server. You should either grant appropriate role to Windows authenticated user or create internal (ArcServe specific) account. For example, I want to create internal account for myself with command line tool ca_auth:

Let’s display short help for ca_auth:

C:\Program Files (x86)\CA\ARCserve Backup>ca_auth -user

Usage :
        ca_auth [-cahost host] -user     add username [passwd] [-assignrole [rolelist]]
        ca_auth [-cahost host] -user     delete username
        ca_auth [-cahost host] -user     chgpasswd username [passwd]
        ca_auth [-cahost host] -user     chgrole username [rolelist]
        ca_auth [-cahost host] -user     validate username [passwd]
        ca_auth [-cahost host] -user     group username
        ca_auth [-cahost host] -user     getall

C:\Program Files (x86)\CA\ARCserve Backup>ca_auth -user add alesk mysecretpwd


Current Available Role List:
=====================================

1) Backup Operator
2) Restore Operator
3) Device Operator
4) Tape Operator
5) Security Administrator
6) Report Operator
7) Monitor Operator
8) ARCserve Administrator
9) Ownership Checking Exemption Privilege

=====================================


Please assgin roles for this user, you can assign more than one role at a time and 
should seperate the selection with comma: 8

If we want to list all existing accounts (internal as well as Windows authenticated):

C:\Program Files (x86)\CA\ARCserve Backup>ca_auth -user getall

User names:

        caroot
        WINBACKUPSRV\administrator
        alesk

Note that in my case I have among ArcServe users two internal accounts (caroot and previously created alesk) 
and one windows authenticated that was created by default during ArcServe installation. 

I’ll be using internal account (alesk) to prepare backup scripts (*.asx), but I would like to delegate execution of those scripts to some backup operator via cabatch command line utility. All I want is to give backup operator (Joe) a possibility to submit backup jobs (asx) to ArcServe with command line tool cabatch from his workstation (WIN7BACKUP). To allow Joe to submit backup jobs to server we must create caroot equivalence for him.

Let’s display short help for -equiv:

C:\Program Files (x86)\CA\ARCserve Backup>ca_auth -equiv

Usage :
        ca_auth [-cahost host] -equiv    add domainname\ntuser hostName ARCserveBackupUser [caroot_username] [caroot_password]
        ca_auth [-cahost host] -equiv    getequiv [domainname\ntuser hostName]
        ca_auth [-cahost host] -equiv    delete domainname\ntuser hostName [caroot_username] [caroot_password]
        ca_auth                         -equiv    whoami

If Joe is logging on his workstation (WIN7BACKUP) with his domain account ACME\joe then the command would be:

cmd>ca_auth -equiv add ACME\joe WIN7BACKUP caroot caroot carootsecretpwd

To check if equivalence exists:

cmd>ca_auth -equiv getequiv ACME\joe WIN7BACKUP
Equivalent ARCserve user for ACME\joe@WIN7BACKUP : caroot

Note: username, domain and hostname are case sensitive!


2) WORKSTATION FOR OPERATOR


In ArcSercve 11.x it was enough if we simply copied cabatch.exe with necessary libraries to operator workstation.
For cabatch to work in ArcServe 16, we need to install ArcServe Manager to Joe workstation (WIN7BACKUP).
After installation of ArcServe 16 Manager, I tried to execute some test backup with:

cmd> cabatch /H=WINBACKUPSRV /S=BackupTest.asx

and received strange error:

*** Can't find out the primary server of WIN7BACKUP

I spent a couple of hours troubleshooting this error, from checks that all Arcserve services properly run on my workstation (WIN7BACKUP) to recreating caroot equivalence…until I realized that my $ARCSERVEHOME\config\discovery.cfg file is empty, without any information about my backup server (WINBACKUPSRV). I added the following two lines to discovery.cfg and backup submit worked:

# note that DOMAIN is ArcServe domain, not Windows domain!
DOMAIN  WINBACKUPSRV
PRIMARY WINBACKUPSRV

3 KNOWN ISSUES


So far, the only unexplained issue is a timeout from the time we hit enter on cabatch and the time backup appears on backup server. In 11.5 the timeout was really short (2-5 seconds), in 16.0 timeout is substantial (60-80 seconds). It’s not a show stopper but certainly something I’ll be paying attention for awhile.
Another issue that is actually not related to ArcServe is UAC control in Windows 7, however the issue is easily resolved (more on this in another post).

ArcServe agent 15 on OEL 6.1

Although ArcServe agent for Linux is not yet certified on Redhat 6.x (OEL 6.x) I decided to install and test the ArcServe agent v15.0 on my newly installed Oracle Enterprise Server 6.1 (x64, of course). Here is a mini how-to (I was installing from ArcServe 15 DVD):

# mount -t iso9660 /dev/cdrom /mnt/cdrom
# cd /mnt/cdrom/DataMoverandAgent/Linux
# ./install
Cannot identify your Linux distribution or it is not yet supported.

Important! You are installing UNIX and Linux Data Mover on a system that is running an operating system that is not currently supported by ARCserve. To check the latest list of supported operating systems, go to ca.com/support. If you continue, be aware that unexpected results could occur.
Do you want to continue? (YES/NO):(default: NO) YES

Simply select 2 (installig agent) and accept defaults, stop with the installation when you see the following warning:

The components you selected require this library file:
libstdc++-libc6.1-1.so.2.  Typically, Linux comes with this library
file. It is located in the /usr/lib path.  Before you rerun the
installation, install the file.

I already installed libstdc++-libc6.2-2.so.3 library on my OEL 6.1, hence all that is needed is a symbolic link that will hide the fact that newer libstdc++ library exists on the system:

$ sudo yum install compat-libstdc++-296.i686  // run in case if the proper "compat" library is not already installed on OEL6
$ cd /usr/lib
$ sudo ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2

Now, you can continue with the installation:

All CA ARCserve Backup agents can be configured for automatic startup 
and shutdown as part of your operating system startup and shutdown.
Do you want to enable automatic startup and shutdown of all backup agents? 
[y|n]:(default: y) y

Checking available space in /opt/CA                           ==> [ OK ]


Installation log file is                           ==> [ /tmp/ARCserveInstall070811-1055.log ]

    Common Agent Module                      (ABcmagt)       ==> [ INSTALL SUCCESSFUL ]
    Client Agent for Linux                   (ABagntux)      ==> [ INSTALL SUCCESSFUL ]

######################################################

    Installation log file is                      ==> [ /tmp/ARCserveInstall070811-1055.log ]
######################################################

Do you want to view the readme? [y|n]:(default: y) 

Critical bug in ArcServe Agent 9.0

If you still have ArcServe 9.0 (confirmed on Build 2050) Agents around the server farm, be very careful if you backup mounted volumes on Windows 2000/2003. This is usually the case on database servers to avoid the letters for the individual volumes.

Let’s say that you have the following mount points:

D:\ORADATA\ORADB\DATA01 —> pointing to VOLUME1
D:\ORADARA\ORADB\DATA02 —> pointing to VOLUME2

You prepare backup in ArcServe as usual, connecting to the Agent, selecting above directories, running the backup and everything seems kosher….until you try to do a restore. At that point you can find out that mount point D:\ORADATA\ORDB\DATA02 contains the files from some random volume. Yes, it means that backup is useless. No error, everything is working fine, it’s just that ArcServe Agent 9 gets somehow wrong information about the volume. For example out of 10 mounted volumes, nine of them will be backed up correctly and one will have unreasonable content – from another volume. One workaround is to add a drive letter with Disk Manager to the problematic mount point, then backup the drive by letter not by mount point.

I couldn’t find any official CA bug note, all I know is that this doesn’t happen with ArcServe 11.5 (SP3) agent.

The moral of this story is to test your restore procedures as much (or more) as you do the backup itself.

Regards,
Ales

ArcServe – how to reset forgotten caroot password

Another “lost” sticky note that I needed today :)

1) stop the ArcServe services with cstop utility:

cd C:\Program Files\CA\BrightStor ARCserve Backup

cmd> cstop

2) Find and rename directory with the SERVER NAME under directory named Discovery:

Rename directory:

?:\Program Files\CA\BrightStor ARCserve Backup\Data\discovery\SERVERNAME

to something like:

?:\Program Files\CA\BrightStor ARCserve Backup\Data\discovery\SERVERNAME.BAK

3) Start ArcServe services with cstart

4) Change caroot password:

cmd> authsetup /p newpwdforcaroot

That's it. From now on use the new password to authenticate as caroot.