You can create user defined backup sets to group a set of selected data that you
need to backup. A user-defined backup set will contain its own default subclient.
On Demand backups allow content to be specified as an external input at the time of initiating
a backup. Whereas traditional backups are performed using subclients,
which contain fixed content configured prior to performing the operation, On Demand
backups allow you to specify content each time you perform a backup.
Content for On Demand backups is defined through two entities:
a Content File, which is a text file that defines the location of
the data that you want to protect. Each Content File contains the fully qualified paths from the root directory to files, links, and
devices to be backed up.
a Directive File, which is a text file that defines where each
Content File is located. The Directive File contains the fully qualified
paths from the root directory to one or more Content Files. Only one Directive File is needed for a single On Demand backup.
Once these entities are defined, an On Demand Backup Set is then created.
Backups run from this Backup Set will provide the facility to select the Content
and Directive Files to be included.
Formatting Content and Directive Files
Content File entries should be in the following format with no filters,
wildcards, or regular expressions included:
\\client1\shares\ondemand_content\test1.txt
/usr/datafile
/usr/textfile
/etc/docfile
Similarly, Directive File entries should be in the
following format with no filters, wildcards, regular expressions, or blank
lines:
/usr/ContentFile1
Configuring On Demand Backup Sets
Create one or more Content Files defining the content to be backed up.
From the CommCell Browser, navigate to Client Computers | <Client>.
Right-click the File System, point to All Tasks and then click
New On Demand Backup Set.
In the New Backup Set Name box, type a name (up to 32
characters).
Click OK.
Create a Directive File defining the locations of each Content File.
Once an On Demand Backup Set has been created, it cannot be changed into a traditional backup set.
Adding Files and Folders with Unicode Characters to Content Files
If the path or the filename contains Unicode characters, the Content File
must be converted to a format that can be used by the data protection operation. The
Unicode Conversion utility must be used to convert the Content File to a format
that can be provided as input.
Using a text editor, create a file that contains a list of files/folders
with Unicode characters. Make sure to save the file as a Unicode text file.
From the Command Line, navigate to the <software install folder>/base
folder and type the following:
cvconvertunicode
<source file> <destination file>
Where:
<source file> is the full path
and name of the file created in Step 1.
<destination file> is the full
path and name of the destination file. The file will automatically be created
by the utility.
Use the destination file as the content file to perform an
On-Demand backup.
Preventing Duplicate Backups of Files
On-Demand Backups explicitly backs up the files listed in the Content File. If the
Content file has two entries for the file, the file can be backed up twice.
For
example, consider a Content File that lists the following entries:
/usr/
/usr/textfile
In this scenario, a backup operation will back up the contents of all data residing
in the textfile folder twice as the Content File already has the entry for the parent
folder to be backed up.
It is recommended that Content Files do not include such duplicate entries. If
you are not able to avoid duplicate entries, use the following steps to prevent
the duplication of data.
Configuring Content File to Exclude Duplicate Entries
From the CommCell Browser, navigate to Client Computers.
Right-click the <Client> in which you want to add
the registry key, and then click Properties.
You can create user-defined subclients to protect specific portions of the client
data. For example, you may need to frequently backup a specific directory or a set
of directories. You can create a subclient for such directories and schedule frequent
backups for that subclient.
By default, the content of the Default Subclient contains
the entire file system.
When you create a user-defined Subclient, the
contents of the user-defined Subclient will be excluded from the Default
Subclient.
A symbolic link is a file that points to another file. By default, the
symbolic link file will be included in the subclient content. However, use the
following procedure to expand and backup the path in the symbolic link.
From the CommCell Browser, navigate to Client Computers |
<Client> | File System.
Right-click the Backup Set, point to All Tasks and
then click New Subclient.
In the Subclient Name box, type a name.
Click the Storage Device tab.
In the Storage Policy list, click a storage policy name.
Click the Content tab.
Select the Expand symbolic links of subclient content
check box and then click Discover.
The data paths to which the symbolic links in the data contents
are pointing will be displayed in contents of subclient.
Click OK.
Enabling backup of symbolic link contents on a Subclient
Backup of content pointed by the symbolic links can be enabled at the
subclient level.
Use the following steps to follow the symbolic links under a subclient and
include the content pointed by these links for backup:
From the CommCell Browser, navigate to Client Computers |
<Client> | File System | Backup Set.
Right-click the <Subclient> and
then click Properties.
Click the Content tab.
Click Browse.
Select the directory or file to be backed up and click Add.
Repeat this step to include all the files and directories to be
backed up.
Click Close.
Select the Expand symbolic links of subclient content
check box and then click Discover.
The data paths to which the symbolic links in the data contents
are pointing will be displayed in contents of subclient.
Symbolic links are backed up by default when they are part of subclient
content. In addition to symbolic links, you can enable back up of data pointed
by symbolic links that are present under the subclient content path but reside
outside the content path.
For example, consider a subclient with content as
/home/user having symbolic links under this directory:
When you enable the option, symbolic links as well as the data they are
pointing to will be backed up, i.e., the data content of the directories,
/user/lib and /etc/commonProfile.rc
is backed up.
Note that data will be backed up unless there is another subclient with
content covering the path the symbolic link is pointing to; if the other
subclient is not scheduled for backup, loss of data due to user error will
occur.
Use the following steps to enable backup of data pointed by symbolic links:
From the CommCell Console, navigate to Client Computers.
Data can be linked to two or more files using hard links. By default, the
hard links are backed up twice. Use the following steps to prevent duplicate
backups of hard links.
From the CommCell Browser, navigate to Client Computers.
Right-click the <Client>, and then click Properties.
By default, NFS mounted file systems are not included in the default subclient.
You can include NFS mounted file systems to an existing subclient using the following
steps:
From the CommCell Browser, navigate to Client Computers
| <Client> | File System | BackupSet.
Right-click the <Subclient> in the right pane, and
then click Properties.
Click the Content tab.
Click Browse.
Select the NFS mount point to be included in the backup.
Files with advisory locks are backed up by default. However, files with mandatory
locks are skipped during backups. Use the following methods to configure the backups
of files with mandatory locks.
By default, the File System iDataAgent
backs up Macintosh files on a shared mount point. During these backups, if the
data on the Macintosh file system share are Apple Double formatted files, they are backed up as two
separate files.
Use the following steps to backup the Apple Double formatted Macintosh files as
a single file:
From the CommCell Browser, navigate to Client Computers |<Client>
| File System | Backup Set.
Right-click the <Subclient> in the right pane and click Properties.
To backup and restore files containing non-ASCII (international) characters
appropriate locale has to be configured in the server. Once configured, these
settings enable you to:
Back up files with names containing non-ASCII characters.
Restore file names containing non-ASCII characters without distortion.
Properly display files with non-ASCII characters when browsing subclient
content or backup data
The following steps use the example of KOI-8R character encoding scheme to
store the files with Russian names.
1.
Logon to the client as root and stop the Services.
Calypso stop
2.
Run the locale command (with no options) to determine
which locale is currently set on the server. A sample output is
shown in the example.
Example:
LANG=en_US.iso885915
LC_CTYPE="en_US.iso885915"
LC_NUMERIC="en_US.iso885915"
LC_TIME="en_US.iso885915"
LC_COLLATE="en_US.iso885915"
LC_MONETARY="en_US.iso885915"
LC_MESSAGES="en_US.iso885915"
LC_ALL=
This output shows that the en_US.iso885915
locale for the LANG environment
variable is currently set.
3.
Use the LC_CTYPE environment
variable to set the desired locale.
Example:
LC_CTYPE=ru.koi8-r
4.
Export the locale.
export LC_CTYPE
5.
Run the locale command. A
sample output is shown in the example.
Example:
LANG= en_US.iso885915
LC_CTYPE="ru.koi8-r"
LC_NUMERIC="ru.koi8-r"
LC_TIME="ru.koi8-r"
LC_COLLATE="ru.koi8-r"
LC_MONETARY="ru.koi8-r"
LC_MESSAGES="ru.koi8-r"
LC_ALL=
6.
Start the Services
Calypso start
A properly configured system will have the correct locale set in one of
the operating system startup scripts (e.g., /etc/profile). In case you do not want to change the locale for
the entire system, you may make the changes to the
Calypso startup scripts by editing the
/opt/calypso/galaxy_vm file
Example:
LC_CTYPE=ru.koi8-r
export LC_CTYPE
To update the CRC consistency checking, include the following command as
root from the Base directory:
/updatecrc32 galaxy/Base/Galaxy
Restart the server to allow the iDataAgent
to start with the correct locale settings.