How to hard code file and directory exclusions in Ralus.cfg

Article:TECH39362  |  Created: 2005-01-20  |  Updated: 2013-11-20  |  Article URL http://www.symantec.com/docs/TECH39362
Article Type
Technical Solution

Product(s)

Issue



How to hard code file and directory exclusions in Ralus.cfg


Solution



Installation of the Remote Agent for Linux and Unix Servers (RALUS) agent creates a ralus.cfg file in the /etc/VRTSralus directory.

What are the components of the Ralus.cfg file?

In order to be backed up by a Backup Exec (tm) media server, UNIX hosts must communicate with a Backup Exec media server. To establish communications, RALUS refers to the ralus.cfg file to identify Backup Exec servers. Ralus.cfg contains a list of Backup Exec media servers that are used to back up that specific UNIX host. Since the same UNIX host can be backed up by multiple Backup Exec media servers, there is no limit to the number of Backup Exec servers that can be listed in the ralus.cfg file.

Backup Exec media server entries in the ralus.cfg file are entered using either the media server name from a naming service such as DNS, NIS, or by an IP address.

The ralus.cfg format includes three components. These components are labeled A, B, and C in Figure 1.

Figure 1
 

A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = Required DNS name or IP address

The first component (A) is a required string that must be entered exactly as follows:
 
SOFTWARE\VERITAS\Backup Exec\Agents\Agent Directory List

The second component (B) is a required and unique identifier, followed by an equal sign (=).  A unique identifier can consist of sequential numbers, letters or alpha-numeric characters. For example:
 
1, 2, 3
A, B, C
AA, BB, CC
A1, A2, B1, B2
 
Whatever unique identifier that is used must be unique if more than one Backup Exec media server is listed in the ralus.cfg file.

The third component (C) showed in Figure 1 is the actual Backup Exec media server IP address or its naming-service accessible name. (For example, a DNS name, hosts file name, or NIS name). When entering this information, do not use spaces.

How to hard code file and directory exclusions in Ralus.cfg
 
If there are files and/or directories on the UNIX host that should be excluded from every backup job, these can be entered in the ralus.cfg file. Making these additions to the ralus.cfg file eliminates the need to manually deselect the files and/or directories in backup selections. After the information is added, the files and/or directories are ignored and will not be backed up.
To add exclusions to Ralus.cfg, use the same format as described above. However, replace component C with the file or directory to be excluded (see Figure 2).

Figure 2
 

A = Required string
B = Required and unique identifier (the order or appearance is irrelevant)
C = File or directory to be excluded

Editing a ralus.cfg file can be done using the UNIX text editor, nano (or vi). However, any basic text editor can be used for editing purposes.
 

A special note should be seen for the selections part of the backup, the excluded directory will still be available to be seen on the creation of the backup but when the backup is run it will be excluded on the backup.  So when you look into the restore selections the excluded folder will not be vi sable for restore. Another way to confirm that it has been excluded on the backup is turning on debugging during the backup.  In the debug you should seen an entry of: 

969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\etc\) when loading hard coded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\mnt\nss\.pools\) when loading hard coded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\_admin\*.*) when loading hard coded exclusion files
969df710 Wed Mar 21 15:56:03 2012 : Adding any excluded filesystems
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type devpts
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type proc
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type sysfs
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type rpc_pipefs
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type tmpfs
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type ftp
969df710 Wed Mar 21 15:56:03 2012 : Excluding filesystem type opt
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\dev\pts\*.*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\proc\*.*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\sys\*.*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\dev\shm\*.*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 : Status 536935943 loading FilesNotToBackup exclude files when enumerating exclude files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\dev\*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 :      used default formatting ([ROOT]\xfn\*) when loading hardcoded exclusion files
969df710 Wed Mar 21 15:56:03 2012 : VX_EnumExcludedFiles: FilesNotToBackup and Hardcoded exclusion files:
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\etc\ /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\mnt\nss\.pools\ /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\_admin\*.* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\dev\pts\*.* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\proc\*.* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\sys\*.* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\dev\shm\*.* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\dev\* /s
969df710 Wed Mar 21 15:56:03 2012 :   [ROOT]\xfn\* /s

 

 



Legacy ID



277508


Article URL http://www.symantec.com/docs/TECH39362


Terms of use for this information are found in Legal Notices