This section documents the Clients tab, which has the following subtabs:

  • Summary
  • Edit
  • VMware
  • Hyper-V
  • Shared File Sets
  • Software
  • Active Directory
  • Schedules
  • Usage

CFA defines a client as the configuration set of files and directories on a networked computer. This is not to be confused with the Agent that is installed on the networked machine itself. Each physical machine can have many sets of files and directories and therefore can be referred to by many client entries. While there are no hard limits to the number of clients that you can add to the system, there are practical limits to the number of clients.

info As a general rule, the capacity of your CFA should be approximately double the total amount of client hard disk space. Following this rule will ensure that you have reasonable space for newly modified data after each client has been completely backed up.

Summary subtab

When you click the Summary subtab, the screen displays a list of client configurations currently known to the CFA.

Each row represents a separate client configuration with various configuration fields shown in their respective columns. Any client can have one or more configuration entries, as long as every client configuration has a name (displayed in the Name column) uniquely identifying it from all other client configurations.

Having more than one configuration entry for a given client is useful if you want to have different sets of directories or files on the same machine backed up by different schedules. For example, if you have a server that contains users’ home directories and mail files, you may want to back up the mail files every day but back up the users’ home directories only once a week. The schedules of these backups should never overlap, as two clients running on one agent can cause errors and agent hang-ups. It is preferred to schedule the backups on separate days to minimize risk of overlap.

On a newly installed system, there will be one client configuration named Myself. This is a special configuration entry for the CFA itself. It provides housekeeping for backing up the catalog of files. This includes the configuration settings for clients, schedules, replication, etc. The Myself client will automatically be archived as a hidden file whenever archiving is performed.


Information

Information on the Summary subtab is presented in the table format with the following default columns:

Column name Description
Status A status key indicating the current state of the client. A client’s status key may change often during the initial configuration as the CFA may take a few moments to recognize and communicate with each new client.
Name The name of the client configuration. The name identifies each configuration entry uniquely from all other client configurations.
Version The agent version, found within square brackets, e.g. 2.4.4[X.X.X.X]
Address The address of the client specified by the client’s Internet name or IP address. This field defaults to the client configuration name. When the Name field is not the same as the client’s name, make sure that this field validly identifies the client by the client’s DNS name or IP address.
When the Address field does not properly identify a client, the Status field will show , indicating that the address cannot be resolved.
Schedule The backup schedule. The predefined default schedules are daily, weekly, monthly, and quarterly. You can also select any other defined schedule, or None (which means that you not use scheduled backups).
OS The operating system running on the client. Knowing which operating system a client is running is helpful – the information is used to generate default settings for the client that can be modified through the client’s Edit interface.
Priority The priority of this client configuration relative to other client configurations when the Backup System is processing multiple client configuration jobs concurrently. The priority can range from 1 to 999; lower-numbered priority jobs are performed first.
Job priorities 1 to 500 are nonexclusive—jobs will be submitted in priority order and will run concurrently, up to the number allowed by the Maximum Concurrent Jobs setting (see Global Settings).
Job priorities 501 to 999 are exclusive—no jobs of priority 501 to 999 will run until all jobs of less than priority 501 are done. For priorities in the range 501 to 999, only jobs of exactly the same priority will run, unless a job in the priority range 1 to 500 is executed while a job in the range 501 to 999 is already running.
Email The e‑mail address, if any, to which emails will be sent regarding jobs for the associated client configuration entry.
Active Jobs Identifies clients currently running a job. The column shows the status of active jobs for this entry; including information such as the count of files backed up so far. If a job is shown here but no active jobs are running (see Director Status for troubleshooting).
If a client is backed up on multiple CFAs and a job is running on one of them, the Active Jobs data will appear on each CFA. This is because the job data comes from the client, not the CFA. The actual job data will only be saved on the CFA that ran the backup.
Full The retention period for full backup jobs, after which the files will be automatically deleted and the storage space can be recycled. An infinity symbol in this column indicates that the job is not scheduled for deletion.
Diff The retention period for differential backup jobs.
Incr The retention period for incremental backup jobs.
AA Whether automatic archiving is enabled on files saved by backup jobs for this entry.
Retries The number of times that a backup should be attempted for a failed job before abandoning the job.
info These are the default columns under the Summary subtab. On this screen and many others, you can change which columns appear, the order in which they appear, and the sort order.

The following symbols are used in the Status column to indicate the client status:

Symbol Status
Indicates the client is a VMware VM.
Indicates the client is a Hyper-V VM.
The client is running the backup agent, and communication with the backup agent is functional.
The name given for the address of the client cannot be resolved. Check the DNS settings of the CFA and ensure that the given address is present in the DNS server’s database or try using the IP address rather than hostname.
The client is down or unreachable. If this status is displayed and the client can be reached by standard network protocols, the client may be behind a firewall that is blocking the TCP port that the backup agent uses.
TCP ports 9101, 9102, and 9103 must be open in order for the backup agent to function properly.
The client is reachable, but the backup agent is not running.
The backup agent is running, but the CFA cannot successfully communicate with the backup agent. 1
The client is not known to the system, or the system has not yet attempted to contact the client.
This status is normal for a brief period after the CFA has been restarted, after a client has been added but the configuration has not been saved, or if the Configuration update pending message is displayed at the top of the backup pages.
info Client status information is polled periodically rather than being updated immediately. This means that it may take a minute or two after a client’s status changes for the change to be indicated on the screen.

Special actions

All special actions on the Summary subtab are available via

  • the toolbar on the top left, or

  • the context menu of a client

info Each entry on the Summary subtab has a check box on the left side of the screen. If you check the check boxes for one or more entries, the actions that you select from the Toolbar will, if possible, apply to all selected entries.

Create a new client configuration

To create a new client configuration, click New on the toolbar or in the context menu of a client. The interface is the same as when you create a new client from the Edit subtab.

Edit a client configuration

To edit an existing client configuration, click Edit on the toolbar or in the context menu of a client. The interface is the same as when you edit a client from the Edit subtab.

Push backup agent

To push the backup agent to a client machine, click Push Backup Agent on the toolbar or in the context menu of a client. See Push Backup Agent for detailed information.

Browse and restore files and folders

To browse and restore files and folders on a client, click Browse and Restore on the toolbar or in the context menu of a client.

The Last Full and Subsequent Backups option displays the most recent full backup, and any incremental or differential backups since the full backup.

All Backup Jobs will display all backups on the RAID for this client.

Selecting Backup Jobs Within Range will display jobs on the RAID from a specific date to a specific date.

Once you have selected the method, click the Submit button.

For further information, see Browse and restore data.

Search files on a client

To search files on a client:

  1. Select the desired client, and then click Search on the toolbar or in the context menu.

  2. In the open dialog, enter the filename, and then click Search.

    The results displayed will be similar to the following:

  3. Once the search is completed, you can choose to restore the desired files.

    See Restore for more information on restoring.

You can use regular expressions to help in the search. See POSIX Regular Expressions for details.

Download client configuration

To download a client configuration file, click Download Configuration on the toolbar or in the context menu.

Client properties

To show properties of a client, click Properties on the toolbar or in the context menu. In the open window, use tabs to view the client’s real-time status, basic configuration, advanced configuration, storage utilization, and backup failures.

Manual client backup

To back up a client manually, click Manual Backup on the toolbar or in the context menu.

info For more information on backup levels, see Backup Level Considerations.

Advanced operations

To show available advanced operations, click Advanced on the toolbar or in the context menu. The following advanced operations are available:

  • Set the debug level (typically used by Infrascale Support for troubleshooting).

  • Dedup the client’s backups. This will dedup all backups on a client, which can take considerable time and CPU usage depending on the amount of data stored for that client.

  • Import (or reimport) the client’s backups.


Edit subtab

When you click the Edit subtab, the screen displays the interface for editing client configurations.

All of the clients on the system (except for Myself) are listed in the left column.

You can use the options on the Edit Clients line to

  • create a client configuration,
  • delete a client configuration,
  • filter the list of displayed clients, and
  • view and change the default configuration settings.


Creating a client configuration

To create a new client configuration, on the Edit Clients line, click New.

The New Client dialog box will appear.

Setting Description
Name The name of the new client configuration. It cannot be changed once the client has been created.
Description An optional description of the client configuration.
Operating System Select from the drop-down list.
Set as Default OS Check this check box if you want your operating system selection to be the new default for your CFA.
Address Specify the clients IP address or DNS name.
Push Backup Agent Software Will push the Agent and DR Image software to a Windows client.
Schedule Select the schedule you would like the client to start with.

Then press OK. The new client will then be listed on the Clients Edit screen.


Deleting a client configuration

To delete one or more client configurations, check the check boxes for the respective clients, and then click Delete on the Edit Clients line.

Then, on the Confirm Client Delete dialog box, to purge the client’s backup data, choose whether or not to purge the associated jobs from that client.

info If you do not purge the backup data with the client, there will be orphaned jobs left on the CFA. Without a client to refer to, the CFA will never know when to delete this information, as retention settings (recycling) is set at the client level. Therefore, the data will remain indefinitely.

File sets

CFA determines which files to backup using a file set for each client. Each file set has a number of attributes, which allow you to specify how the set is handled.

info The first time you click the Edit subtab on a new installation, no clients will be listed. (See Creating a Client Configuration.)

When clients are listed on the screen, you can use the check boxes to select one or more. If you select multiple clients, all settings that the clients have in common will be displayed. Any settings that are different among the selected clients (including check boxes) will be displayed with angle brackets (< >). When you save any changes that you make, only new settings will be modified for the selected clients.

When you edit any setting on the screen, a blue triangle () will appear next to the changed setting, indicating that a change (delta) has occurred.

After you complete any configuration changes, click Apply to apply your settings, or click Reset to return to the original. Also, Activate Configuration to confirm all changes made.

The settings on the screen are documented in the following sections.

info Clients can share defined file sets. (See Shared File Sets subtab.)

General settings

Name

The Name setting corresponds to the name of the client. The name is set when you create the client; you cannot change it.

Description

The Description setting is optional, and can be used to help further identify the client. Client descriptions can include any character except double-quotes (").

Password

The system-generated client password is used to authenticate the CFA and the client software installed on each client. This password will be entered automatically into the client’s configuration file. Each client uses its client password to authenticate the CFA each time a backup or restore is performed.

If you check the Auto Generate Password check box, when you save the client, the current password will be discarded and replaced with a random password string. Be sure to update the agent with the new password if it has been changed on the client.

Push Backup Agent

Push Backup Agent allows pushing the Backup Agent and DR Image software to a Windows client. Clicking the Push Backup Agent option during client creation or from the Clients > Edit tab will start the Push Backup Agent wizard.

Push Backup Agent Wizard

The push backup agent wizard will allow you to push the backup agent and DR Image software to a Windows machine. When you start the wizard it will pre-fill the CFA IP address, clients IP address, and port number.

These fields are not editable from the wizard. If you need to edit them, it is recommended to close the wizard and make the changes in the respective parts of the UI. You will need to provide credentials for an administrator level account on the desired Windows machine.

If you click the button on the top right of the dialog it will open a pre-requisite dialog. These conditions must be met in order for the push functionality to work.


Client Networking settings

The Client Networking pane has two settings:

  • The Address setting should be either the client’s IP address or the client’s DNS name. The default setting is the value used for the Name field. If the Name value is not a valid DNS name, enter a valid DNS name or an IP address into the Address field.

  • The Port setting is the TCP port that the CFA uses to communicate with the client. Normally you don’t need to change this port; however, if you want to run multiple agents with different privilege levels on the same client, each agent will require a different port setting. The default value is 9102.


Notification settings

You can set up emails to be sent to you in System > System Alerts for all clients on the CFA. It is recommended that you use this area only if there is another contact, besides this global recipient for this specific client.

If you want the contact to receive emails about all backup activity, type your email address in the Email box. If you want this contact to receive the emails only when errors occur, check the Email only on error check box.

info You can include multiple addresses separated with commas.

Backup settings

The Backup pane has three settings: Schedule, Priority, and File Set.

Schedule

The Schedule setting specifies when backups will run for the client, and at what backup level (full, differential, or incremental). There are four predefined schedules. You can edit these default schedules or add your own schedules. (See Schedules subtab.).

Backup schedule Description
Quarterly Performs a full backup on the first day of January, April, July, and October; a differential backup on the first day of every other month; an incremental backup on all other days.
Monthly Performs a full backup on the first Sunday of every month; a differential backup on each subsequent Sunday of the month; an incremental backup on all other days.
Weekly Performs a full backup on every Sunday; an incremental backup on every other day of the week.
Daily Performs a full backup every day.2

You can also set Schedule to None, meaning to never automatically back up the client. You can then back up the client manually at any time. This is useful for computers, such as laptops, whose presence on the network is not guaranteed. For information on performing manual backups, see Manual Backup.

The backup levels (full, differential, and incremental) are summarized in the following table.

Backup Level Definition
Full Saves all files specified for the client, whether or not the files have been modified since the last backup.
Differential Saves all files that have been modified since the last successful full backup.
Incremental Saves any file that has changed since any previous successful backup of that file.
info For more information on backup levels, see Backup Level Considerations.

Priority

The priority of this client configuration relative to other client configurations when the backup system is processing multiple client configuration jobs concurrently. The priority can range from 1 to 999; lower-numbered priority jobs are performed first.

Job priorities 1 to 500 are nonexclusive—jobs will be submitted in priority order and will run concurrently, up to the number allowed by the Maximum Concurrent Jobs setting (see Global Settings).

Job priorities 501 to 999 are exclusive—no jobs of priority 501 to 999 will run until all jobs of less than priority 501 are done. For priorities in the range 501 to 999, only jobs of exactly the same priority will run, unless a job in the priority range 1 to 500 is executed while a job in the range 501 to 999 is already running.

File Set

The File Set setting specifies what directories or files to back up. Each file set has a name and is defined for a specific operating system. The default file set for your client depends on the operating system. For example, by default, Windows clients will back up C:/, and Linux and Mac clients will back up /.

Using the File Set drop-down list, you can select a default file set based on the operating system, or you can customize your own file set (by selecting the file set having the name of the client).

Whichever file set you select, you can then click Edit to edit the file set according to your needs. This opens the File Set Editor window.

The File Set Editor window includes the following options.

Option Description
VSS To let the agent back up open files, check the check box.
Promote jobs to Full after file set configuration changes Indicates whether a full backup should be forced after the File Set configuration is changed.
Override Client-Configured Plug-in Settings Used to override the plug-in configuration. When the new control group is unselected, the override is not in effect, and all plug-in configurations are controlled through InfrascaleConfig.

Browsing for Starting Point folders

To use the file browser to find folders and files for backup and add them to the client’s file set, go to Clients > Edit, click the file set’s Starting Directories and Files entry that you want to edit. (If no entries exist, click New to create an entry.)

The list of directories to be backed up will appear, along with the Browse Client button which enables you to browse the client’s file system.

Click Browse Client and use the file browser to select a folder to add to the list.

info In some cases, such as when you are editing file sets from multiple clients or editing shared file sets, you may be prompted to identify, from the available clients, the single client that you want to browse.

As you browse a client, keep in mind that you must select the folder by clicking it in the Entry List pane. The selection will then appear in the Selection area at the bottom of the screen.

After you accept your selection in the file browser, the selection will be added to the list of directories to be backed up for the current file set.

VSS

VSS client plug-in now supports application writers as well as the previously supported in-use files. This complete implementation of the Microsoft standard is the foundation for many new features and functionality, and it will continue to provide for greater extensibility in future releases.

By default, most application “writers” that are discovered on a client will be backed up during a backup that has VSS enabled. The following exceptions apply:

  • The Microsoft SQL Server writer is never used. SQL plug-in provided by us has a richer feature set and is the preferred method for backing up and restoring SQL data-bases.

  • System writers will be backed up if the “system state” backup option is explicitly configured to be enabled on the client. If it is not enabled, all system writers will be ignored during backup.

  • The Microsoft Exchange Server writer is only used on Exchange 2010 clients when Exchange Database backups are explicitly configured using the plug-in override controls.

You can also exclude writers from backup by explicitly specifying them as excluded in the file set.

Matchers

Matchers are used for including and/or excluding files, folders, or writers from a given file set. Below are several examples of how to configure Matchers for different purposes.

Matchers may be created when editing a file set. Below the List of directories to backup, click the New button in the blue bar.

Add a “matcher” to an existing “starting directories and files” specification. Select the Exclude option and add a “Plug-in Config”.

For each VSS writer that you want to exclude from being backed up, add it to the “matching patterns” dialog.

The format of the entries must be VSS:/name of writer where name of writer is the exact name of the VSS writer itself. (You can use the vssadmin tool provided by Microsoft to list all writers available on a particular system.)

If you click Browse Client, you can browse the writers available on the client and select a writer to add to the list.

The Starting Directories and Files area shows what directories will be included in the backup. To add new directories, click New. To delete or edit an existing directory specification, click Delete or Edit, respectively.

If you click New, a window similar to the following will appear:

Enter the directories in the upper area of the window. You can select the various default options in the lower area by checking the check boxes or using the drop-down menus.

notification_important Be aware that the order of the matchers is important. For example, the job will fail if you first exclude everything and then try to include a certain folder.
info Matchers may be used for any file system; the examples below are written as if for Windows but could easily be converted to macOS, Linux or NetWare.
Matching examples

Example 1

This will back up the entire C:/ but will exclude any file with an .mp3 extension.

List of directories to backup: C:/

Matcher: Exclude, Case Ignore, Wild

File: \*.mp3

Example 2

This will back up everything under /departments and exclude only the /my music folders.

List of directories to backup: D:/departments

Matcher: Exclude, Case Ignore, Wild

Directory: D:/\*/my music

Example 3

This will back up everything at the /departments level and for each user, the /my documents folder and all its contents. Everything else will be excluded.

List of directories to backup: D:/departments

Matcher 1: Include, Case Ignore, Wild

Directory: D:/departments/users/\*/my documents

Matcher 2: Exclude, Case Ignore, Wild

Directory: D:/departments/users/\*/\*

Example 4

A more complex combination similar to all of the above. Mac users may recognize these paths, the C: was added just for the example.

This will backup each user’s Desktop and Documents folder. The subfolder Microsoft User Data will be excluded. Any files with .mp3 or .exe or .avi extensions will be excluded. All other directories under the starting point are excluded.

This one requires a bit more explaining. Obviously we have our starting directory and we are excluding three different file types. What is not clear is the fact that the path in Matcher 2 is a subdirectory to a path in Matcher 3. In other words, we are preemptively excluding /Microsoft User Data which is a subdirectory of the included /Documents directory. We then exclude everything else.

List of directories to backup: C:/volumes/docs/staff\_data

Matcher 1: Exclude, Case Ignore, Wild

File: \*.mp3;\*.exe;\*.avi

Matcher 2: Exclude, Case Ignore, Wild

Directory: C:/\*/Microsoft User Data

Matcher 3: Include, Case Ignore, Wild

Any: C:/volumes/docs/staff\_data/\*/Desktop; C:/volumes/docs/staff\_data/\*/Documents

Matcher 4: Exclude, Case Ignore, Wild

Directory: C:/volumes/docs/staff\_data/\*/\*

If using Regular Expressions the \* should change to .\*.

Matchers can be highly useful to trim down your backups and save space on your CFA. However, they may be a little tricky to get right on the first try. If these examples do not help your scenario or you have other questions, feel free to contact Infrascale Support for help. If you can describe exactly what you want, we should be able to help you create the matcher set to make it happen.

info For information on regular expressions, see POSIX Regular Expressions.
Browsing for files and folders used to define matchers

To use the file browser to find folders and files and specify them as wildcard or regular expression (matchers) for the client’s file set, go to a file set’s Starting Directories and Files entry that you want to edit. (If no entries exist, click New to create an entry.)

Find an existing matcher that you want to edit, or click New to create a new matcher. Click Add and select the type of matcher condition that you want to add.

The current list of patterns for the selected condition will appear along with the Browse Client button that enables you to browse the client’s file system.

Click Browse Client and use the file browser to select a folder or file to add to the list.

info In some cases, such as when you are editing file sets from multiple clients, you may be prompted to identify the single client that you want to browse.

As you browse a client, keep in mind that you must select the folder by clicking it in the Entry List pane. The selection will then appear in the Selection area at the bottom of the screen.

After you accept your selection in the file browser, the selection will be added to the list of patterns for the selected condition.

info You can further modify the new pattern by editing the text in the text area as needed.

Disaster Recovery Image settings

The Disaster Recovery Image group has the following settings:

  • Schedule. Allows to set a separate schedule to run your DR backups, independent of your file backups.

  • Priority. Allows you to set the priority of the client for Disaster Recovery Backups.

  • Volume Set. Allows to choose which volumes in Windows are captured with DR backups. These are set by specifying the drive letter that Windows has assigned to the volume.


Appliance Networking settings

From the Interface drop-down menu, select the network interface for your CFA. This tells the client which IP on the CFA to send its data to when doing a backup. This only rarely needs to be set.

If you select NAT, you are required to specify an IP address. If your CFA is behind a router doing NAT, and you have forwarded port 9103 to the CFA to let clients on the other side of that router access the CFA, you will have to put the router IP here because clients on the other side of the router will not be able to talk to the CFA IP address directly. This is a rarely used option.


Job Retention settings

These settings allow you to create a job retention period for each backup level. Jobs that exceed this retention period will be automatically deleted from the RAID, freeing the disk space they once used.

If you do not check the check box for a backup level, those backups will not be deleted but will be kept forever (or until manually deleted).

For each backup level, specify the number and use the drop-down list to select the unit (years, quarters, months, weeks, etc.).

info The month option reflects 30 days, not the number of days in the current calendar month. If you wish to reflect a 31 day month, it is recommended to set the recycling schedule to 31 days rather than 1 month.

If you would like to change the default retention settings for newly created clients, you may do so in Jobs > Retention.


Offsite Job Retention settings

These settings allow you to create a Job Retention policy for jobs that have been replicated offsite. These settings will only be applicable if replication is enabled.

If you would like to change the default retention settings for newly created clients, you may do so in Jobs > Retention.


Offsite settings

The Replicate checkbox selects to have the jobs for this client replicated to the cloud or secondary CFA (if replication is configured). There is also a priority number which indicates the relative importance of replicating jobs for this client comparted to other clients. Those with a lower number will be queued for replication ahead of those with a higher number.

Purge Remove Jobs checkbox selects if the jobs for this client that have been replicated to the replication target should be left in place on that target machine, or deleted when replication is disabled for this client.


Error Recovery settings

The Error Recovery group has two settings:

Setting Description
Rerun Failed Whether to rerun failed backup jobs
Recover Entries How many times to retry the backup job and at what interval

Other Actions settings

The Other Actions group has two settings:

Setting Description
Run Before Backup Use this to run a script you have set up before the backups for this client run. The script is not saved on the CFA, rather it is hosted on the server that needs to use it and the path to its location is stored here.
Run After Backup Use this to run a script you have set up after the backups for this client run. The script is not saved on the CFA, rather it is hosted on the server that needs to use it and the path to its location is stored here.

Filter the list of clients to edit

You can use the Filter drop-down list on the Edit Clients line to display only clients on the Clients Edit tab that are selected (check boxes checked), and/or have been changed (since the last you activated the configuration).


View or modify default settings of a client

To view the default client configuration (which will apply whenever you create a new client), click Defaults on the Edit Clients line.

If you want to modify the default client configuration, after you make your changes, click Apply.

When you have finished viewing or modifying your client defaults, click Defaults again.


VMware subtab


VMware server connection


Add new VMware server connection

Click Add Connection to launch the wizard.

The first page of the connection wizard will ask for the address and administrative level credentials of the vCenter or host you would like to connect to.

The second and final page of the connection wizard explains that each VM will need a local client to manage backup and restore operations. This page gives you the option to automatically register all VMs on the connection (see VMware auto registration). Click Finish to add the connection.

When connect directly to a host managed by a vCenter Server, you will be given the option to connect to the vCenter Server instead. If you choose to do so, a new connection wizard will appear, and the address will be automatically set.

Upon completion, you will receive a notification that the connection was added successfully, or message describing why the connection failed.

Edit existing VMware server connection

Select View Connections to open the connections dialog.

From this dialog you have the ability to disconnect, reconnect or completely remove a connection. To view further information about a particular connection click Properties from the context menu.

The Connection Properties dialog gives more in-depth information about a connection. From this dialog you can also edit address information (not editable if connected), view Hosts if connection is a vCenter Server, and enable/disable VMware auto registration.

VMware auto registration

VMware auto registration allows your CFA to automatically register all current and future VMs on a given connection. This process will create a local VM client and assign it the VM client defaults. This is an all or nothing setting however, individual clients can be manually unregistered at any time. If manually unregister, the client will be excluded from future auto registration.

Auto registration can be enabled as follows:

  1. Add new VMware server connection.

  2. Edit existing VMware server connection.

Once auto registration has completed, a notification will be added to the Dashboard tab.

If you click on this notification it will take you to the auto registration report for the given connection. You can view auto registration reports at any time on the Connection Properties dialog.

For each auto registration report there will also be an email sent if email notifications have been configured. You can disable auto register report emails in System > Settings > System Alerts.

info If your CFA happens to be running on the connection, it will not be automatically registered and will prevent manual registration.

Edit VMware client configuration

To edit a VM client configuration, click the Edit button on the actions bar.

Setting Description
Synthetic Full Complete VMware backups are a complete snapshot. Subsequent backups are appended to the previous backups and stored as a full file set/snapshot.
File Set VMware backups are complete and therefore do not have an editable file set.
Deduplication VMware backups are always deduplicated.
Change Block Tracking If enabled, Change Block Tracking will allow for incremental and differential backups of VMs.
Ignore Unallocated Sectors When CBT is enabled, this will only perform a backup of the used portion of the disk.3
Quiesce Data If selected, and the VM is powered on when the snapshot is taken, VMware Tools is used to quiesce the file system in the VM. Quiescing a file system is a process of bringing the on-disk data of a physical or virtual computer into a state suitable for backups. This process might include such operations as flushing dirty buffers from the operating systems in-memory cache to disk, or other higher-level application-specific tasks.4
Skip Independent Persistent Disks This option allows the CFA to skip any VMDKs in a VM that are in independent persistent mode, and continue to back up the other disks. VMware provides the independent persistent mode for virtual disks to allow them to be excluded from snapshots. This is sometimes used to allow snapshots to be taken of the OS and primary data disks for a VM without having to include disks used for temporary data (cache, temp files, etc.). If your VM has a virtual disk in independent persistent mode when the snapshot is taken for backup, the job will fail unless this option has been selected.

To enable CBT the following VMware conditions must be met:

  • The host must be ESX/ESXi 4.0 or later.

  • The VM owning the disks to be tracked must be hardware version 7 or later.

  • I/O operations must go through the ESX/ESXi storage stack. So NFS is supported, as is RDM in virtual compatibility mode, but not RDM in physical compatibility mode. Of course VMFS is supported, whether backed by SAN, iSCSI, or local disk.

  • CBT must be enabled for the VM (see below).

  • Obviously, VM storage must not be (persistent or non-persistent) independent disk, meaning unaffected by snapshots.

  • The virtual disk must be located on a VMFS volume, backed by SAN, iSCSI, or local disk. RDM is not VMFS.

  • The VM must have zero (0) snapshots when CBT is enabled, for a clean start.

  • CBT is enabled by default on 6.1 and later versions.

  • CBT can also be checked via the Clients > VMware and looking for the CBT Enabled Column for registered VMs.


Restore VMware VM

To restore a backed up VMware VM, launch the restore wizard via one of the following:

  • Clients > Summary

  • Clients > VMware

  • Jobs > History

With the exception of selecting the job itself from Job > History, you will be presented with the option of which job to restore.

Once the wizard has been launched, you will see a Preparing Wizard screen followed by a screen showing all backups that can be restored from that VM. Select the backup you wish to restore and click Next.

You will be prompted to select the restore method, either Restore to Existing Virtual Machine or Create New Virtual Machine. Select the desired option and click Next.

info If you select Create New Virtual Machine, an additional screen will display prompting you for the details of the new connection. Complete the destination and data store information and select Next.

You will be prompted to select which data stores you wish to restore the VM disks to. If the data stores used by the original VM backup are available, you can select Use Existing. Otherwise, select a data store for each disk being restored. Click Next.

  • If you selected Restore to Existing Virtual Machine, you will be prompted to take a snapshot of the state of the VM before restoring over the VM. This is not required.

  • If you selected Restore to New VM, you will be prompted to name the new VM. Click Next.

A summary window will allow you to review the settings you have chosen. You will be asked if you wish to power on the VM after it is restored and if you wish to connect the VM to the network after it is restored.

After you have made your selections, select Finish. You can monitor the status of the restore in Clients > VMware (Action column).


Browse and restore VM backups

To browse and restore a VM backup:

  1. Select a VM, and then click the Browse and Restore button in the actions bar, or right-click a VM, and then click Browse and Restore.

  2. Select the job to restore files from.

  3. Select the type of restore:

    • Component Files

      Browse and restore the files that make up (define) the VM. This includes the VM .ovf file as well as its .vmdk file. Typically, these files are only useful if you need access to low-level, technical information regarding the VM.

    • Contained Files

      Browse and restore the files that are contained on the VM hard disks. Each disk can be explored independently using our exclusive file system browser UI. This is a great way to restore selected files from within a VM without having to restore (and possibly create) the entire thing.

      info Mounting the VM disks may not be immediate. Once started, the process will make a copy of the disks to work from. Once copied, subsequent mounts/restore requests will be significantly faster.
  4. Review your selections and click Finish.

  5. Select the files and/or folders to restore.

  6. Select the client and path to restore to. The path can be selected or browsed.

    In order to restore files to a VM, the following conditions must be met:

    • The VM must be powered on and it must be running the latest version of VMware tools for the managing entity to which it belongs (vCenter, ESX/ESXi, etc.).

    • Login credentials must be supplied for a valid, available account on the VM. This account will be used to gain access to the file system for purposes of saving restored files. Administrator-level accounts are recommended.

  7. Click Restore to submit the restore job. The files are restored to the path specified.


Remove VMware client

You can remove a VM client in two ways:

  • Go to Clients > VMware, right-click a VM, and then click Unregister.

  • Go to Clients > Edit, select a VM, and then click Delete.


Remove all VMware clients

  1. Click View Connections.

  2. Right-click on the server to be removed and click Remove.

    The remove wizard will appear and list the VMs that will be removed with the server connection.

  3. Click Yes to remove the connection and all VMs on the server selected.

info Existing backup jobs may be retained or purged when unregistering a VM; however, a specific client cannot be retained while purging others if removed as a group/server. If you wish to retain a client in a group/server, see Remove a VM client above.

Application data restore from VM backups

Before doing a backup of a windows VM, the CFA can signal the guest OS to Quiesce the VSS writers. This will signal the writers to put their data into a consistent state like shutting down the service would without shutting down the service. This prepares the data in the program associated with the writer to be restored separately from the rest of the VM.

In this section, we will cover doing an application data restore for exchange, but other program with VSS writers can also be restored this way.

Preparing backups for application data restore

Before we can restore application data to a VSS writer, we need the files in a backup to be prepared for a restore. To do this, go to Clients > Edit, select the client for the VM, and check the Quiesce Data box in the VMware section.

The next backup will ask the VM guest OS to signal applications to prepare their data for restore before the VM snapshot is taken. After that the backup will proceed as normal.

Preparing a client for application data restore

In order to restore VSS data to a VM, the backup agent must be installed on the VM. This will provide the means for the CFA to send restore data to the VSS writers on the VM.

  1. Download and run the agent software from the Software subtab.

  2. On the agent configuration, set the IP address of the CFA, the password, and the port for the agent to listen on.

    The agent by default runs as the local system account, which only has administrator privileges on the local machine. Some VSS writers will require additional privileges within the application (i.e. Exchange or MSSQL).

  3. Open the agent configuration, go to the Service Control tab, and stop the service.

  4. Click Other Account, and enter the credentials for an account with local administrator access and administrator access to the application you are going to restore.

  5. Click Apply, and then start the agent service.

    A client configuration on the CFA will also need to be created, and configured to point to this agent. Go to Clients > Edit, and click New.

  6. Enter a name for the client, and choose the OS from the select list and click OK.

  7. Set the password and port to match the one used by the agent. Set the IP address to that of the guest OS, not the ESX host. This client is only needed for restoring data, and will not be used for backups, so we recommend setting the schedule to none.

Restoring the application data

To restore application data to a VSS writer:

  1. Go to Jobs > History, right-click the job to restore, and then click Browse and Restore.

  2. Select the Application Data restore type and click Next.

  3. Select the client to restore to from the list, and then click Next.

  4. Click Finish.

The CFA will communicate with VSS on the client VM through the agent running on that client, and display a list of VSS writers that can be restored. From here, you can select what data to restore to the available writers. It is possible with some writers like the Microsoft SQL Server or Exchange writers to browse into the writer, and select only a portion of the available to restore. In the screenshots below, only one Exchange database is being restored.

For an Exchange 2010 database restore, the agent will handle everything that has to be done one the exchange server (unmounting the database, preparing it for restoration, and mounting the restored database).


Hyper-V subtab


Hyper-V server connection


Add new Hyper-V server connection

To add a new Hyper-V host connection, you first need to ensure the proper software is installed on the Hyper-V host. You will need the latest 6.7 version of the Windows agent as well as the latest version of the DR Imaging software installed. In version 6.7 and later, during the client creation, you can push this software to the Hyper-V Host.

If a client has not already been created for this Hyper-V host you will want to do that now. For additional info, see Creating a Client Configuration.

Once the client is showing connected and ready we can now click Add Connection. A wizard will pop up which will guide you through the process of adding the Hyper-V host.

From the dropdown list, select the client that represents your Hyper-V host.

info If the client associate with your host is not listed here, you will need to check the Clients > Summary subtab for its current status. If it is showing anything other than a green checkmark, it will not be displayed in this drop down.

If have not yet added the client, you are given the option to Add New Client, which will take you through the Creating a Client Configuration wizard.

You can also specify a description for your selected host, however this is not required. Click Next will continue the wizard.

Here you will have the option of registering all VMs currently local to the Hyper-V host at connection time. You will still be able to register each VM one at a time after the connection is created if you do not enable this option.

info We do not allow multiple connections to the same Hyper-V host, you may receive an error that we failed to connect due to existing connection to that host already existing.

Edit existing Hyper-V server connection

Click View Connections to open the connections dialog.

From this dialog you have the ability to disconnect, reconnect or completely remove a connection. To view further information about a particular connection select Properties from the context menu.

The Connection Properties dialog gives more in-depth information about a connection. From this dialog you can also edit address information (not editable if connected), view Host connection properties and number of hosted VMs.


Edit Hyper-V client configuration

To edit a Hyper-V client configuration, click the Edit button on the actions bar.

Synthetic Full Complete Hyper-V backups are a complete snapshot. Subsequent backups are appended to the previous backups and stored as a full file set/snapshot.
File Set Hyper-V backups are complete and therefore do not have an editable file set.
Deduplication Hyper-V backups are always deduplicated.

Restore Hyper-V client

To restore a backed up Hyper-V VM, launch the restore wizard via one of the following:

  • Clients > Summary
  • Clients > Hyper-V
  • Jobs > History

With the exception of selecting the job itself from Job > History, you will be presented with the option of which job to restore.

Select the backup you wish to restore and click Next.

You will be prompted to select one of the connected Hyper-V hosts as a target restore location. If you do not see the desired host, ensure that it is currently connected (see Edit existing Hyper-V server connection). Choose a host and click Next.

The next step of the wizard will allow you to name the new VM. Hyper-V hosts will allow you to have multiple virtual VMs with the same name, so by default restored is appended to the original name. Change the name (optional) and the name click Next.

The final page is a summary page that will allow you to review the restore options you’ve selected. This page also has an option to power on the VM upon completion of the restore. By default this option is set to No. If you are satisfied with the restore options, click Finish.

You can monitor the status of the restore in Clients > Hyper-V (see Action column).


Browse and restore Hyper-V backups

  1. On the Summary tab, right-click a Hyper-V client to restore files from, and click Browse and Restore.

  2. Select the job to restore files from.

  3. Select the type of restore:

    • Component Files

      Browse and restore the files that make up (define) the VM. This includes the VM .ovf file as well as its .vmdk file. Typically, these files are only useful if you need access to low-level, technical information regarding the VM.

    • Contained Files

      Browse and restore the files that are contained on the VM hard disks. Each disk can be explored independently using our exclusive file system browser UI. This is a great way to restore selected files from within a VM without having to restore (and possibly create) the entire thing.

      info Mounting the VM disks may not be immediate. Once started, the process will make a copy of the disks to work from. Once copied, subsequent mounts/restore requests will be significantly faster.
  4. Review your selections and click Finish.

  5. Select the files and/or folders to restore.

  6. Select the client and path to restore to. The path can be selected or browsed.

    notification_important Currently we are only able to restore to the existing VMware VMs or any system with an agent installed. If you are attempting to restore files to a Hyper-V VM, you will need to install the agent on the VM and create a client in the UI.
    Restoring component files to a Hyper-V server will restore a .vmdk file, which Hyper-V is not able to use. The file will need to be converted to a .vhd file before it can be recognized by Hyper-V.
  7. Click Restore to submit the restore job. The files are restored to the path specified.


Remove a Hyper-V client

To remove a Hyper-V client:

  1. Go to Clients > Hyper-V.

  2. Right-click the client you want to remove.

  3. Click Unregister to open the wizard.

  4. Follow the wizard instructions.


Remove all Hyper-V clients

  1. Click View Connections.

  2. Right-click the server to be removed, and click Remove.

    This will open the wizard showing the list of VMs to be removed.

  3. Click Yes to remove the connection and all VMs on the selected server.

You can choose to delete the jobs that will remove all of the jobs from the storage. Or you can choose to orphan the jobs that will allow them to remain in the CFA storage until they removed manually.


Shared File Sets subtab

When you click the Shared File Sets subtab, the screen displays current file set configurations that can be shared by one or more client configurations.

After you edit the settings for a shareable file set, all client configurations sharing that file set configuration will perform backups using the modified file set.

By default, the Shared File Set subtab screen has the following columns:

Column name Column description
Name Name of the shared file set.
OS Operating system associated with the file set.
Clients Number of clients sharing the file set configuration. The number will vary as client configurations are changed to and from other file set configurations. In order for the shareable file set to be deleted, the number of clients must be zero.
No Full On Change Whether a full backup should be forced after the file set configuration is changed. If a check mark appears, the client will try to run the next scheduled or manual job without reverting to a full backup.
Volume Shadow Copy Whether the given sharable file set configuration will employ volume shadow copy capabilities when available for the particular client’s operating system.
Starting Directories and Files Starting backup point for clients sharing a given file set configuration.

File set operations

All operations, which can be performed for the file sets, are shown in the actions bar, or in the file set context menu.

Create new file set

  1. Click New.

  2. Enter the name and select the operating system for the shared file set.

Edit a shared file set

To edit a file set, click the desired file set, and then click Edit.

File set clients

To view a list of clients using a shared file set, click the desired file set, and then click Show Clients in the actions bar.

Delete a shared file set

To delete a shared file set, make sure no clients are associated with the file set, click the desired file set, and then click Delete in the actions bar.


Software subtab

The Software subtab contains links to download client software to the client computer.

info You may need to copy the software to the client by other means, such as SCP, FTP, or command line web tools.

Installing client software and configuration files

Linux, Solaris, FreeBSD

  1. Open a root shell.

  2. Enter the following:

    root\# cd /tmp
    root\# tar xf /path/to/Eversync-backup-client-6.1.0.xxx.XXXX.YYYY.tar
    root\# cd Eversync-backup-client-6.1.0.xxx.XXXX.YYYY
    root\# bash ./install.sh
    

    For your specific client, for the 6.5.0.xxx.*XXXX*.*YYYY* strings in these commands, substitute the corresponding client-specific information from your client operating system filename. For example, for the Solaris/Sparc operating system, you would enter the following commands:

    root\# cd /tmp
    root\# tar xf /path/to/rvx-backup-client-1.5.3.22.sparc.SunOS.tar
    root\# cd rvx-backup-client-1.5.3.22.sparc.SunOS
    root\# bash ./install.sh
    
    info Your file version information may be different from what is shown in the table due to updates in the downloaded software.
  3. Download the client configuration file.

    1. Go to Clients > Summary.

    2. Select the client that you want to download the configuration file from.

    3. Right-click the client, and then click Download Config.

    4. Save the bacula-fd.conf configuration file in the directory /opt/eversync/etc.

    warning The configuration file contains a password that will allow privileged access to the client; the password should not be made publicly available, and should be removed immediately after successfully downloading to the client. We recommend setting the permissions on this file to only allow root to read it.
  4. Enter root\# /etc/init.d/eversync-backup start to start the backup client manually.

HP/UX

  1. Open a root shell.

  2. Enter the following:

    
    root\# gunzip eversync-agent-VERSION.ia64.depot.gz
    root\# swinstall -s /full/path/to/eversync-agent-VERSION.ia64.depot.gz
    \\\*
    
    info Your file version information may be different from what is shown in the table due to updates in the downloaded software.
  3. Download the client configuration file.

    1. Go to Clients > Summary.

    2. Select the client that you want to download the configuration file from.

    3. Right-click the client and select Download Config.

    4. Save the bacula-fd.conf configuration file in the directory /opt/eversync/etc/.

    warning The configuration file contains a password that will allow privileged access to the client; the password should not be made publicly available, and should be removed immediately after successfully downloading to the client.
  4. Enter root\# /sbin/init.d/eversync-backup start to start the backup client manually.

    To stop the client, enter root\# /sbin/init.d/eversync-backup stop.

    info The agent should start automatically on boot (installer installs links in /sbin/init.d/rcX.d).

Windows

The Windows backup agent includes support for SQL Server 2005 and 2008, Exchange 2007 and Exchange 2010. We recommend that you install the latest service packs for both the operating system and the server applications.

For DR Image backups, it will require the additional download and install of the DR Imaging software. The software is compatible with both x86 and x64 versions of Windows. The DR Imaging software works with the windows agent, and both need to be installed to do DR Image backups of a client machine.

Prerequisites

Before installing the Windows backup agent, make sure the following software is installed:

  • Visual C++ Runtime Libraries
  • .NET 4.0 framework
  • MAPI (for exchange mailbox plugin only)
info Most required software will be automatically downloaded and installed during installation if it is not already installed, but the MAPI software for exchange mailbox backups requires manual installation. The agent installer will provide a link to the MAPI software to download from Microsoft if you need it and don’t have it installed already.
Installing the backup agent for Windows
  1. Run the Infrascale-backup-client-X.exe file.

  2. If the prerequisite software is missing, it will be installed automatically.

  3. Click Install to install the listed components, or click Cancel to exit the installation.

  4. Follow the instructions to complete the process.

    info By default, the Infrascale Backup Agent check box will be checked.

    If you are installing on an Exchange Server, the Exchange Database Plugin or Exchange Mailbox Level Plugin options may be available. See Exchange Server Backups.

    If you are installing on a SQL Server, an additional option MsSQL Database Backup Plugin will be listed.
  5. After installation is completed, the following window shows:

    • If you select the manual method, specify the CFA address, CFA password, and client name.

    • If you select the active directory method, click Lookup. The screen will display a list of the CFAs detected on your network. Select your CFA from the list, and then click Next. Then, on the screen that appears, type the administrator password.

Installing the DR Imaging software
  1. Run the DR Imaging software installer.

  2. Click Install.

  3. Click Close when installation completes.

Configuring the backup agent for Windows

Use the Infrascale Agent Configuration (InfrascaleConfig) program to configure the Service Control, Exchange Database Backup, Exchange Mailbox Backup, and SQL Backup tabs.

Service Control tab

The Service Control tab controls how the Bacula service runs. The default account type is the local system account, but you can change it to run as a user account. Running as a user account is usually required for the Exchange agent to run properly. The Service Control tab is the same for all Windows agents.

To capture your system station information, check the Enable System State Backup check box. Client settings, such as setting the location to save the .bkf file, should be configured here in the Service Control tab. However, each client file set can enable or disable the entire System State feature so that some clients use it and others don’t.

Exchange Database Backup tab

See Exchange Server Backups for more information on configuring Exchange backups.

This tab allows to enable or disable the online backup (enabled by default). You can also choose to truncate the Exchange logs after the backup, though by default Exchange logs are truncated after full backups only. The following setting is to truncate after incremental and differential backups, which is not recommended:

Exchange Mailbox Backup tab

The Exchange server tab also displays the Message Store(s) and server name to be backed up, and indicates whether the permissions are OK for the account. Also, mailboxes in the message store can be displayed. Finally, you can select the restore method (overwrite, skip, or duplicate) if a message already exists.

SQL Backup tab

On an SQL Server you can use the SQL Backup tab to enable or disable the SQL backup (enabled by default).

The screen displays a list of databases found on the server. By default, all databases, except the tempdb database, are selected for backup. To explicitly include or exclude a database for backup, check the check box in the Include or Exclude column, respectively.

SQL Support Chart

The CFA supports the following SQL versions for client configuration:

  • SQL Server 2005
  • SQL Server 2008
  • SQL Server 2012
  • SQL Server 2014
info CFA does not support backing up and restoring of the Evaluation editions and IA64 versions.

macOS

The backup agent supports macOS 10.3 (Panther) or later. It installs a universal binary that supports both PowerPC and Intel hardware.

First, you need to install the client configuration file, and the client software after that. (If you have installed the client software first, and then the configuration file, you need to restart the system in order for the client service to find the client configuration.)

To download the client configuration file:

  1. From the /usr folder, create the /rvx/etc/ folder.

  2. In the CFA Management Console, go to Clients > Summary.

  3. Select the client that you want to download the configuration file from.

    In order for you to download the configuration file, the client needs to be communicating with the backup agent (as indicated by a green check mark in the Status column).

  4. Right-click the client and then click Download Config.

  5. Save the bacula-fd.conf configuration file in the /usr/rvx/etc/ folder.

To install the backup agent, run the rti-backup-client-X.X.X.X.MacOSX.mpkg file.

NetWare

  1. Create the SYS:\system\revinetix folder.

  2. Unzip the rvx-backup-client-3.0.4 090218.i386.netware.zip file and copy its contents into the new \system\revinetix folder.

    As software client files are updated, the client filename that you enter may be different to reflect the file version that you downloaded.

  3. Download the client configuration file as follows:

    1. Go to Clients > Summary.

    2. Select the client that you want to download the configuration file from.

      In order for you to download the configuration file, the client needs to be communicating with the backup agent (as indicated by a green check mark in the Status column).

    3. Right-click the client, and then click Download Config.

    4. Save the bacula-fd.conf configuration file in the \system\revinetix folder.

    5. Enter SYS:\system\revinetix\revinetix to start the backup service.

The NetWare client also has a migration feature that can be used to work with migration software such as the CaminoSoft MSHSM solution.

Follow these steps to enabling migration:

  1. Add the -m option to the Bacula-fd client start command in the revinetix.ncf file.

    For example: Load Address Space=Bacula sys:rvx\baculafd.nlm -m -c sys:rvx\bacula-fd.conf.

  2. Create a run.ncf command script on the Novell server, and save it in the SYS:\system\revinetix directory.

    The client’s Run Before option in its configuration on the CFA must point to the script. The script should be similar to the following:

    SYS:\MSHSM\MSSTUBSV SAVE PATH SYS: FILE
    SYS:/STUBS/STUBSAVESAV FLAG /L /NODISP
    delay 120
    SYS:/MSHSM/MSSTUBSV SAVE PATH SYS: FILE
    TEST:/STUBS/TESTSAV.SAV FLAG /L /NODISP
    
info NetWare does not actually support command output redirection. The user must check the server console log screen to see the output. Some NLMs cannot be multiply loaded. The delay value in the example command script needs to be long enough (measured in seconds) for the first instance of MSSTUBSV to complete before the command runs again on another volume.

Active Directory subtab

Once the CFA has been added to the Active Directory, a list of clients in the Active Directory will be displayed.

Select the computers that you want to create a client for.

You can also assign default settings to a single or to multiple clients as follows:

  1. Select a client you want to inherit the default settings.

  2. Click the Create Clients link in the lower-left corner.

notification_important Remember to click Activate Configuration to activate your changes.

Deploying the backup agent

  1. Copy the backup-client-\[version\].msi file (this file can be downloaded from Support > Portal) to a shared location on the network that all target machines will have access to. If you are going to apply any .mst transformation files, copy them as well.

  2. From the Group Policy Management console, create a new group policy.

  3. Enter the name for the new group policy.

  4. Right-click the newly created group policy, and then click Edit.

  5. Go to Computer Configuration > Software Settings, right-click Software Installation, and then click New > Package.

  6. Select the rvx-backup-client-\[version\].msi file that you previously copied to a server share.

  7. Click Assigned for normal installation, or Advanced to apply an .mst transformation file, then click OK.

  8. If applying a transformation file such as backup-client-NoFirewallChange.mst, go to the Modifications tab, and then add the desired .mst files.

  9. Close the Group Policy Object Editor (but not the Group Policy Management console).

  10. To change the security address for the group policy object (you will apply it to computer objects and not users), delete Authenticated Users, and then add Domain Computers.

  11. Drag and drop the newly created group policy object into a container to create a link.

    In the example below, the group policy object named Infrascale Backup Agent is being linked to the top of the domain. The policy that deploys the .NET framework must also be in the container.

  12. To link the group policy object, click OK.

  13. To ensure that the .NET framework is installed before the backup agent, select the container that contains the backup agent, and order the group policy object links such that the priority for the .NET framework group policy object is greater than the priority for the backup agent.

Software installations are only applied when the client computer reboots. During the startup process, before the login screen, you should see the following messages:

Installing managed software Microsoft NET Framework 2.0

Installing managed software Infrascale Backup Agent

info The first message will appear only if the .NET framework had not been deployed previously.

You would use the same process for the 64‑bit .NET framework and Infrascale Backup Agent. WMI filtering could be used to only deploy correct software on 32‑bit and 64‑bit machines.

Back up Active Directory components

By default, system Active Directory components are backed up as part of a system state backup. After you have installed the client on the Active Directory server (domain controller), complete these steps to enable system state backups.

  1. Start InfrascaleConfig on the server, and go to the Service Control tab.

  2. Select Enable System State Backup.

    info You can also select any other required plug-in overrides.
  3. Click OK or Apply to commit changes.

    info Agent configuration to enable/disable system state backups is also subject to override using the new plug-in controls on the CFA.

For information on restoring Active Directory components from a backup, see Restoring Active Directory domain controllers.

Troubleshooting

Make sure that the target machine is properly communicating with Active Directory. From a command prompt, run netdiag and make sure there are no issues related to DNS or Active Directory and that all of the reported values are expected.

If you want to check whether the group policy object will be applied without rebooting the target machine, from the command prompt, run gpupdate /force. The output should provide information if reboot is required to install the software.

Also, make sure that the target machine is a member of the container that contains the group policy object(s).

Check the event log.


Schedules subtab

The Schedules subtab shows the backup schedules that have been configured.

Schedule settings are used on the Clients > Edit subtab to determine when to run backup jobs and at what level (full, differential, or incremental). (See Backup level considerations.)

Information on the Schedules subtab is shown in the table format.

Column name Column description
Name Name of the schedule
Description Optional description of the schedule
Clients Number of clients that use the schedule. (You cannot delete a schedule if clients are using it.)
Summary Summary of runs in the schedule

Schedules subtab additional operations

All additional operations on the Schedules subtab are available via

  • the toolbar on the top left, or

  • the context menu of a schedule

Create a new schedule

  1. Click New on the toolbar or in the context menu.

  2. In the Identification group, provide a name and an optional description for the schedule.

  3. In the Runs group, click New to create a new run.

    A run determines when backups will run in the current schedule. Each run covers the backup level, as well as the time and days for it to perform.

  4. In the Options group, select the backup level (full, differential, or incremental).

  5. In the Scheduling group, set the frequency and the relevant time/day/month options when the backups will run.

Edit a schedule

To edit an existing schedule, click the schedule, and then click Edit on the toolbar or in the context menu.

Show clients that use a schedule

To show a list of clients that are using a schedule, click the schedule, and then click Show Clients on the toolbar or in the context menu.

Delete a schedule

To delete a schedule, click the schedule, and then click Delete on the toolbar or in the context menu.

info You can only delete schedules with no clients.

Backup level considerations

The table below describes the available backup levels.

Backup level Description
Full Saves all files specified for the client, whether or not the files have been modified since the last backup.
Differential Saves all files that have been modified since the last successful full backup.
If a previous full backup (or a suitable full backup) cannot be found, then the differential backup will be upgraded to the full backup.
Incremental Saves any file that has changed since any previous successful backup of that file.
If a previous full backup (or a suitable full backup) cannot be found, then the incremental backup will be upgraded to the full backup.

The backup system will search for a suitable full backup. If the full backup cannot be found, the CFA will search for a job with the following attributes:

  • the same client name

  • the same file set definition

    info Any change to the client’s file set definition, such as adding or deleting a file in the section for included files or excluded files or directories, constitutes a different file set definition.
  • for a differential backup job, the earlier backup job was a full backup

  • for an incremental backup job, the earlier backup job was a full, differential, or incremental backup

  • the earlier backup job terminated normally (that is, it did not fail and was not canceled)

If the aforesaid conditions are not met, the differential or incremental backup job will be promoted to a full backup job.

For a differential or incremental backup, the backed up files that are determined by comparing the start time of the previous backup job and the time when each file was last modified; files modified after the backup start time will be backed up. The time on the client should be synchronized as closely as possible to the time on the CFA to be sure that all modified files are backed up.


Usage subtab

The Usage subtab shows the summary of the disk space used to store backed up files on the CFA.

notification_important This subtab is hidden by default unless in the advanced view mode. It is not recommended to open without prior consultation with the support representative.

If deduplication has been enabled for this configuration, this area shows the space used after duplicate copies of the saved files have been recognized and the extra storage space for these duplicate files has been freed.

The top row on the subtab contains the following data:

Global Shared Bytes Number of bytes used to store files that are duplicated on one or more clients
Global Shared Files Number of files duplicated on one or more clients
Global Unique Bytes Number of bytes used to store files for which there is only one occurrence among all jobs/clients
Global Unique Files Number of files for which there is only one occurrence among all jobs/clients

Main statistical data is presented in the table format with the following default columns:

Column name Description
Name Name of the client
Client Pre-Dedupe Size Number of bytes backed up from the client before deduplication
Client Exclusive Size Number of bytes for files backed up only once on this and all clients
Inter-Client Shared Size Size of the data on the client that was also found on one or more other clients
Intra-Client Shared Size Size of the data on the client that was found more than once only on the same client
Legacy Data Size Number of bytes stored without deduplication (with deduplication disabled, or on pre-deduplication client versions)
Meta Data Size Total number of bytes used for file attribute information, book-keeping, and inlined files
Client Inline Size Number of bytes used to store data directly as metadata, bypassing the deduplication process
Client Exclusive Size Share of the client in total bytes saved for files backed up only once across all clients
Intra-Client Shared Size Share of the client in the intra-client shared size out of the total (intra- and inter-) shared data
Inter-Client Shared Size Share of the client in the inter-client shared size out of the total (intra- and inter-) shared data
  1. This is mostly due to an authentication problem. Make sure that the client password on the Edit Client page and in the client’s configuration file are the same. If you change the client’s configuration file, make sure that you restart the backup agent on the client. Also, make sure that there is no firewall or antivirus software blocking communication and also that the correct software version for the OS is installed. 

  2. Use this schedule sparingly, because it could quickly use up your available backup space. 

  3. For information on how to enable CBT manually, see the VMware Knowledge Base article

  4. If the VM requires a CBT reset, (usually due to a host being shut down uncleanly) see the Knowledge Base article