This section documents the System tab which contains all the tools that are required for monitoring the system or performing the re-configuration. All options are visible in the navigation pane on the left side of the window. All available configuration options are described further. Please note that depending on the software version the list order may vary.

Basic settings

Basic section includes the set of tools that is required for basic configuration changes.

Appliance Status

Appliance Status displays the screen containing a variety of information about the current conditions of the CFA. This screen is particularly useful to identify the CFA firmware version and model, and other system-related information.


You can use this screen to set the CFA time manually or to specify an NTP server that will synchronize the time.

To use an NTP server, select NTP Server, type the server IP address in the NTP Server Address box, and click Query Server to verify the address.

To configure the CFA time manually, select Manual Time Configuration, configure New Time and New Date, and then click Change Time to update the time on the CFA.

For both manual and NTP server settings, use the Time Zone dropdown menu to select the time zone. Backup schedules are defined and executed with respect to the selected time zone.

You can verify the time settings on the CFA in System > Status.

Firmware Update

The section allows to update the CFA firmware automatically or manually.

Automatic update

Updates, when available will show as available. Click to download the update.

If selected, updates will automatically download to your CFA upon release; however, they will NOT be automatically installed. In this example, the update rvh- has been downloaded and is ready to be installed. To do so, click Install.

You will be presented with the license agreement. When you have reached the bottom, you will have the option to Agree or Cancel.

Selecting agree will begin installing the update.

Once the update is complete, the CFA must be restarted to apply the installation. Select Reboot to continue.

The update process will complete with the reboot of the CFA. As soon as the CFA has booted, you may login as normal.

After upgrading the CFA firmware, it is strongly recommended to update the software on the clients as well. See Installing client software and configuration files.

Manual update

  1. Click Advanced.

  2. Click Browse to open the file manager. Choose the update file and click Open.

  3. Click Yes to confirm that you would like to run the update.

  4. Once uploading is complete, the restore process is the same as the automatic process. Install the file, agree to the license agreement, and then reboot.

  5. After upgrading the CFA firmware, it is strongly recommended to update the software on the clients as well. See Installing client software and configuration files.


Use this screen to change the password, which is used for CFA configuration, and to sign in to the CFA Management Console. In the respective boxes, type the existing password, then enter and re-enter the new password.

infoThe password is case-sensitive and can be any combination of alphanumeric characters and punctuation marks. The minimum password length is one character, but we recommend a password longer than six characters, using upper- and lower-case letters with digits and punctuation characters. Use a password that will not be easily guessed.

Should the password become lost or otherwise forgotten, the only way to reset the root (and admin) password is from direct keyboard access to the console. Here’s how:

  1. Reboot the system. DO NOT remove the power source. Try to reboot by pressing Ctrl+Alt+Del. If that still fails, try the reset button.

  2. When it is powering back on, interrupt the boot loader (which waits for 3 seconds) by pressing any key.

    If you are unable to interrupt the boot loader in time, press Ctrl+Alt+Delete, or the reset button on the chassis and try again.

  3. Change boot options to boot to Single User mode.

    1. Select Infrascale Current (VGA).

    2. Press e.

    3. Select kernel….

    4. Press e.

    5. Press End, press Space, type 1, press Enter, press b (make sure Caps Lock is off).

  4. This should boot to a command prompt, run the Linux command to change your password.

    1. Type passwd and press Enter.

    2. Follow the on-screen instructions to enter and re-enter the new password.

    3. Type reboot and press Enter.

  5. The system should boot normally and you may login with the new password.

  6. To apply your changes, click Submit.


Use this screen to reboot or shut down the CFA. Information on any pending or active jobs will be displayed for your review prior to the reboot or shutdown. You will be prompted to confirm the action before the reboot/shutdown is applied.

Remote Access

The CFA can be registered with your Infrascale Dashboard account (see Registration). If the CFA is registered with a Dashboard account, and if Allow Remote Access selected, then the Dashboard will also have a link to open the CFA Management Console. This makes the CFA interface accessible from the Dashboard, even when on a remote network that would not otherwise be able to access the CFA Management Console.

The remote access feature, when enabled, will establish an outgoing TCP connection to the Infrascale Dashboard. Because it is an outgoing connection most common firewall configurations will not block the connection. When you sign in to the Dashboard and use it to access the CFA, the connection is redirected back through the connection the CFA already established with the Dashboard, allowing access to the CFA Management Console from networks that would otherwise not have access.

While remote access is in progress, a notification will be displayed on the Dashboard tab.

Networking settings

This section allows you to configure the networking settings of or for the CFA.

Active Directory

In the Search For box, type the name of your domain controller and then click Find. If the CFA finds the domain, the information will populate in the Domain Information section. If this information is correct, click Join. When prompted, type your username and password, and then click OK.

Once you are connected to the Active Directory, you will have access to view the entire list of computers on your domain.


DNS server translates between host names (such as and IP addresses (such as When given only a short name (such as www) to translate, the CFAs domain name (if any) is used to constrain the search within this one domain. You can override this domain name by specifying a domain name in the Search Domains box. You can specify additional domains to widen the search to more domains. Enter the IP address of your network primary DNS server in the DNS Servers box.

Host Name

The short name for an CFA serves to uniquely identify the CFA within the specified domain. The short name can be comprised of a maximum of 63 alphanumeric characters and hyphens (). Neither the first nor last character can be a hyphen.

The domain name can be one or more short name-like sequences of characters that are separated by periods (.). Two periods cannot be together without other valid characters between them.

Network Adapters

Use this screen to configure the CFA network interfaces. For each interface, specify:

  • Whether the interface is enabled (active on startup)

  • Whether the device uses an IP address from a DHCP server or a static IP address

  • The speed and duplex settings

  • Export Virtual, if selected, allows a VM from the Boot tab to use this network interface

If you would like to use a static IP address, enter IP Address and Netmask in the Static Settings panel.

Client ID in the DHCP Settings group is optional. Client ID is sent to DHCP servers when the CFA is started, and it can help the server(s) to configure the CFA network settings. Configuring multiple network devices to be on the same subnet is not supported.

Faster networking of the CFA

Starting from IDR v5.0, there is support for 2 faster networking methods, 10 GigE Ethernet connections, and network connection bonding. Each of these has its pros and cons. This document will summarize some of these to help you choose the method that is best for your environment.

  Pros Cons
10 GigE - Easier to setup than bonding
- Faster than bonding
- Can provide faster throughput for individual clients and for multiple simultaneous backups
Requires a 10GigE NIC, 10GigE port on the switch, and adequate wiring
NIC bonding - Software only solution allowing the existing NICs to work together
- Even if more NICs need to be added, it is usually cheaper than adding a 10 GigE NIC
- Enhanced fault tolerance (one bad network cable doesn’t completely disconnect the machine from the network)
- Not as fast as the 10GigE connection
- Harder to set up
- Most modes require support by the switch
- Will not make any one client’s connection much faster, but does allow multiple simultaneous clients to be faster (for details, see the NIC Bonding setup section)
- Clients past an IP gateway might see no speed increase
Network monitoring with ntop command

Ntop must be started first by the ntop command at the command line. Setting a password will be required. Once the password is set, the session must be stopped via CTL+C.

infoThis is only required the first time ntop is to be started.

Once the password is set, the ntop service can be started with the command service ntop start.

infoThe service will not be started by default. To start the service at boot edit /etc/rc.local.

ntop can now be viewed at http://{cfa-ip}:3000, where {cfa-ip} is IP address of the CFA.

infoDue to limitations of ntop, the URL may require viewing with incognito/private browsing. Alternatively, clearing the browser cache will also clear up some issues.

10-GbE networking setup

Setting up a 10-GbE connection requires no different settings in the software than does setting up 1 GbE.

To confirm that the network is connected at 10 GB/s go to System > Network Status, and click Networking. On the page dialog that opens, look for a network connection with the speed shown as 10000 (10000 MB/s ~ 10 GB/s).

NIC bonding introduction

NIC Bonding (also known as port trunking) allows multiple network interface cards to share one IP address and work simultaneously on one network. Bonding provides fault tolerance, and depending on the mode used might provide some load balancing to improve throughput.

There are several modes of bonding supported by the CFA. We generally recommend balance-alb or 802.3ad, but your specific needs might be better served by one of the other modes. All of these modes provide some fault tolerance, and some provide some level of load balancing. The first consideration when choosing a mode is what modes (if any) are supported by the switch that the CFA will be connected to.

Mode Pros Con
active-backup Fault tolerance
No switch support required
No improvement to backup speed
No improvement to restore speed
balance-tlb Fault tolerance
NICs shared for send only (restores)
No switch support required
No improvement to backup speed
balance-alb Fault tolerance
Balance load between NICs for both send and receive
No switch support required
Can only balance load for local network segment
balance-xor Fault tolerance
Load for transmits spread across NICs
Balanced for transmit only, so can only help speed multiple simultaneous restores
Requires switch support
No improvement to backup speed
balance-rr Fault tolerance
Each packet sent from the next NIC (round-robin)
If the switch is capable, it can send packets to the CFA in the same round-robin way
If the switch can spread packets across the interfaces, throughput from one client can be faster than 1 NIC alone
Packets might arrive out of sequence, which will cause some packets to be retransmitted
Overall throughput of bond connection lower than the sum of the connections.
Requires switch support
802.3ad (LACP) Fault tolerance
Packets can be sent and received through different NICs for different clients
Overall throughput of bond connection can be nearly the sum of all connections
The maximum throughput of one client equals to the throughput of one NIC.
Requires switch support
Turning on the bonding

The bonding is configured from the CFA Management Console, so when setting up a new CFA, first configure the networking with only one interface. To turn on the NIC bonding, follow these steps:

  1. Sign in to the CFA Management Console, go to System > Network Adapters.

  2. In the NIC Bonding group, select NICs to be included in the set.

  3. Select Enabled.

  4. In the Bonding Modes dropdown list, select the mode.

    A reminder will be shown for those modes that require special support at the switch.

  5. Configure the IP address, or select DHCP, and then click Apply.

  6. Go to Reboot, and click Shutdown.

  7. If the selected bonding mode requires switch support, turn on the bonding (port trunking) for the ports the CFA is connected to in the switch configuration, then turn on the CFA.

Modes that do not require support from the switch

Active-backup – Fault tolerance. If the active interface loses connection, a backup interface is brought online. This mode only provides fault tolerance. Only one interface is ever active.

Balance-tlb – Fault tolerance and load balancing (for transmit only). In this mode data is transmitted out all of the interfaces in the bond set. Only one interface will receive data.

Balance-alb – Fault tolerance and load balancing. This mode is balance-tlb, with the addition of modifying arp replies so different clients will talk to different interfaces. Each client machine can only talk to one interface, but multiple clients’ traffic can be spread across multiple interfaces.

Modes that require a switch that supports bonding

balance-xor – Fault tolerance and some load balancing. The source and destination mac addresses are XORed to choose which interface to send traffic through. All traffic going through one gateway will share one interface on the CFA.

802.3ad (LACP) – Fault tolerance and load balancing. Client’s traffic through a gateway will share one interface on the CFA. Connections must all use the same speed and duplex. One client will only be able to use the bandwidth of one NIC. Multiple simultaneous clients can be spread across the NICs. 2 clients might share one NIC, even if others are available (see How the network layout affects bonding performance for details).

balance-rr – Fault tolerance and load balancing across multiple interfaces. If the switch supports the balance-rr mode traffic into and out of the CFA will be balanced across the connections. This is the only mode in which traffic from one client can use more than one NIC. This means that packets can arrive out of order, which can cause higher CPU use on the computers at both ends, and packet retransmissions. This will cause the TCP congestion control to limit the speed to less than the sum of the connections in use. With 4 1GigE interfaces bonded on the CFA, a single client on a fast enough connection (also using port trunking, or a single faster connection, like 10GigE); the connection might only achieve 2Gb/s.

Choosing between balance-rr and 802.3ad

If your switch supports both the balance-rr and 802.3ad (also known as LACP) modes, we recommend that you use one of these modes, as they provide the best benefit to throughput. Generally, we recommend 802.3ad but the trade-offs between these two modes are listed discussed below.

802.3ad allows the maximum throughput of the bond to be nearly the sum of the speed of the component connections. One client can only use the bandwidth of one NIC at a time, so with any number of 1Gb/s links in the bond, one client will only be able to use 1 Gb/s. To make use of the bandwidth of more than one NIC, more than one client must be backed up simultaneously. To fully saturate the bond usually requires at least as many clients as there are NICs in the bond. The MAC address of the client machines determines which NIC they use, so some may share NICs even if other NICs are free.

balance-rr allows a single client to use more bandwidth than one of the component NICs. The maximum possible throughput of the bond is lower than when using 802.3ad, but the maximum throughput that a single client can use is higher than the maximum that a single client can use in 802.3ad.

How the network layout affects bonding performance

With the exception of the balance-rr mode the modes that do load balancing (like balance-xor, and 802.3ad) select which interface to send packets based on the MAC address of the sender. Network traffic going into the CFA from the clients will not be evenly balanced across the interfaces. All traffic from one source will have the same sending mac address, and so will all go to one interface on the CFA.

The throughput possible between 2 machines is only as fast as a single link in the set. For example, on an CFA configured with 4 1GigE NICs with a client computer connected on a 10GigE connection, communication between them will not be faster than a single 1GigE link. This is because all packets coming from that client will have the source same mac address and will therefore always be sent to the same interface on the CFA.

Selecting the destination interface based on the sender’s MAC address makes it easy for the switch to determine very quickly where a packet should be routed, but does introduce some limitations. For example, in the diagram below traffic from server 5 and server 6 passes through a router to get onto the CFA’s local network segment. This will cause all packets from those servers to have the same source MAC address (that of the router), so they will share one link to the CFA. Servers 1-4 are on the same network segment, and so they will each have a unique source MAC address.

The balance-rr mode uses a different scheme to decide which interface to send data to and data from a single source can be spread across multiple interfaces on the CFA. This allows traffic from Server 5 and Server 6 to use more than one interface on the CFA, but has the disadvantage that packets will often be delivered out of order in both directions. This will cause the TCP congestion control to limit the speed to less than the theoretical max. With 4 1GigE interfaces bonded on the CFA, a single client on a fast enough connection (also using port trunking, or a single faster connection, like 10GigE); the connection might only achieve 2Gb/s.

See further information on Wikipedia and Linux Foundation.

Network Status

This screen provides a summary of the current networking configuration.


Proxy settings allow you to enter in client side settings for a proxy server, if you have a non-transparent proxy on your network.


Use this screen to manually add and delete routing table information.

The routing table keeps information about paths to other networked nodes. Each route entry consists of a device, a target/mask combination, the VIA address (or next hop), and an optional metric. The default route is / 0.

You can use this screen to add, delete, or edit routes.

Adding routes

To enter route information, use the text boxes and list box at the bottom of the table on the screen. Click Add to add the new route to the table.

Only valid routes can be added to the routing table.

Editing routes

You can edit the route for any row that has an Edit button. Rows without an Edit button are permanent and cannot be edited.

To edit a route, click the corresponding Edit button:

When you have finished editing the route, click Change. Or, click Cancel to discard your changes.

Only valid route information can be included in the routing table.

Deleting routes

You can delete the route for any row that has a Delete button. Rows without a Delete button are permanent and cannot be deleted.

To delete a route, click the corresponding Delete button.

Tools settings

The Tools group includes settings that allow advanced configuration, re-configuration and maintenance procedures of your CFA.


Use the Certificate configuration screen to enable interface operation in an encrypted mode, in which data passed between the authorized user and the system cannot be intercepted easily. Enter the appropriate information in the text boxes. This information forms the distinguished name for the certificate and should be customized for your installation. Browsers typically expect the Common Name to be the Internet name of the CFA.

After you enter the information, click Submit.


Licensing for all Infrascale data protection solutions – which includes Infrascale OS application running on Infrascale CFAs – is based on the net capacity of the product you have purchased. The “net capacity” of each offering equates to the total raw capacity minus the capacity allocations needed for standard RAID 5 configurations and archiving.

For example, your capacity license of 2.4 TB will be derived from 3.2 TB of raw capacity minus 400 GB for a RAID 5 setting, and minus 400 GB for archiving.

If you wish to upgrade your capacity license, you may not simply buy higher capacity hard drives and install them in your CFA. This course of action will void any warranties associated with your purchase. Instead, you must contact your Infrascale dealer and purchase a capacity license upgrade. This license upgrade includes our approved installation and configuration process.

For details concerning Infrascale capacity licenses, upgrades, and warranty offerings, please refer to the official Infrascale price list available from your Infrascale Reseller.

Local Boot

This window will allow you to override the default value for maximum number of booted VMs. The default value is calculated based on system resources, and exceeding this value runs the risk of degraded performance. It is recommended that you leave the boot limit at the default value, and delete previously booted VMs before booting a new VM.


NAS is a provision of disk space via commonly used network file sharing protocols. This disk space can be shared by many client computers using one or both of the following protocols:

  • SMB protocol is commonly used to provide shared network access to files for computers running Microsoft Windows.

  • NFS protocol provides the same service to computers running many of the Unix-based operating systems, such as AIX, Linux, and Solaris.

Use the NAS screen to manage folders and network file sharing protocols and to control firewall interaction with the NAS space.

Adding a new share

To create a new share, on the main NAS screen, click the Folder link. A screen similar to the following will appear:

You should choose a folder name that meaningfully represents what this folder and possible subfolders will be used for. Remember that it will be possible to share this folder with one or more people on one or more client computers using one or more network file sharing protocols. An example folder name would be “Staff.”

In the Enter Folder Name box, type the name for the new share, and then click Register. A screen similar to the following will appear:

From this screen you can unregister the specified folder, create the space for the folder or delete it if it already exists, and change the folder’s service availability.

If space for the folder does not already exist, click Create to create the folder and move towards sharing it. The screen will then appear similar to the following:

This screen gives you the additional options to delete the space that you created, check your disk usage, and change which local user or group owns the folder.

This screen also indicates the service availability of the NFS and SMB file sharing protocols for the share. In the example in the figure, the “NFS no and “SMB no” links indicate that neither protocol is currently available. (If the respective protocols were available, the links would be labeled “NFS yes” and “SMB yes”.)

To configure the file sharing protocols and make them available:

For the SMB protocol (for computers running Microsoft Windows), continue with the next section, see SMB Protocol.

For the NFS protocol (for computers running Unix-variant operating systems, such as AIX, Linux, and Solaris), see Enabling the NFS Protocol.

SMB protocol

This section documents SMB protocol, which is commonly used to provide shared network access to files for computers running Microsoft Windows.

Enabling SMB protocol

The first task for using the SMB protocol is to enable the protocol on the CFA. This task also includes configuring global SMB protocol settings and creating SMB users.

When you enable or disable the SMB protocol, the setting will apply immediately, as well as whenever the CFA starts up, until you change the setting.

To enable SMB protocol on the CFA, on the main NAS setup screen, click SMB (on) (the links indicate the current status):

At the top of the screen, under Current Status, click Enable to enable SMB protocol. (Or, if SMB is already enabled, click Disable to disable the protocol.) The browser will then return to the previous screen.

You can use the Global Settings panel on this screen to configure the overall service behavior for any folders shared via SMB in the global settings. The settings are in five categories:

Settings Description
Security Mode Use to specify whether users need to log on to the server in order to connect to the share
Workgroup/Server String Use to specify the workgroup that the CFA should log in to, as well as what will be displayed to users in addition to the CFA name
Map to Guest Use to specify whether to allow guest logins
Hidden Files Use to configure what file types, if any, will be hidden files that will not normally be seen on the remote clients. For each file type listed, you can use the dropdown list to select Unset, Hide, or Show
Filename Mangling Use to configure filename case and format settings

To save your global settings, click Set.

This screen also includes an Account Management link at the bottom for creating and managing SMB users.

There are no predefined users. You can use the following buttons on the screen to create a new user, or manage existing users (select users by checking the respective check boxes):

Button name Button description
Add Add new account with the specified name (minimum three characters) and password (minimum four characters)
Password Change password for the selected users
Enable Enable selected users
Disable Disable the selected users
Remove Remove the selected users

When you have finished managing users, close the screen.

Making SMB available on a folder

To make SMB protocol available on the folder, either:

  • On the main NAS setup screen (see NAS), click no in the SMB column for the respective folder, or

  • On the disk share configuration screen (see Adding a new share), in the Service Available row, click SMB no.

infoRemember, no indicates the current status of the folder (before you make these changes).

From this screen, you can configure various remote access capabilities specific to the named folder.

For security purposes, new folders are created with no access rights. You will need to enable various configuration settings in order for the folder to actually be usable:

Option Description
Folder The folder for sharing. (You cannot edit this setting here)
Share Name The share name, which defaults to the share name. Share names should be 12 characters or less
MS‑DOS Volume Name The MS‑DOS volume name for the share
Comment Arbitrary notes regarding the share
Available When selected, allows access to the folder. This setting is configurable in case you need to quickly disable that folder availability without necessarily removing the folder or disabling the SMB protocol service.
Whether Available is selected determines whether SMB protocol is listed as available (yes) or not (no) on the main NAS screen and other related screens
Browsable When selected, allows the folder to be browsed
Writable When selected, allows the folder to be written to (although at first you may want to leave the checkbox clear in order for the folder to be read-only)
Guest OK When selected, allows guest access to the folder

Next, use the Users section of the screen to configure what authenticated users can do with the folder (please refer to the screenshot above)

This screen lists the defined SMB users from whom you can configure the users for the share, using the Valid, Assigned, and Administrators options:

In the Valid selection list, select one or more users who will then all be able to access the folder share. To select multiple users, hold down Ctrl while you click individual users.

Use the Assigned dropdown list to select which user (if any) to assign as the owner of files created by valid users. (If no user is selected as owner, users will own their own files.)

Valid users who are not assigned as owners will not be able to make any changes to this top level folder, but only to any subfolders that the valid user does own. To change this, click Owning User, and then on the disk share configuration screen (see Adding a new share), change the local user to match the valid user. (Be sure to click Change User so that the change will take effect.)

Use the Administrators selection list to select one or more users as administrators.

You can use the Hidden Files section to configure what file types, if any, will be hidden files that won’t normally be seen on the remote clients. For each file type listed, you can use the dropdown list to select Unset, Hide, or Show.

To save these new configuration settings and return to the main NAS screen, click Set.

NFS Protocol

This section documents NFS protocol, which is commonly used to provide shared network access to files for computers running many of the Unix-based operating systems, such as AIX, Linux, and Solaris.

Enabling NFS protocol

The first task for using the NFS protocol is to enable the protocol on the CFA. This task also includes configuring NFS clients.

When you enable or disable the NFS protocol, the setting will apply immediately, as well as whenever the CFA starts up, until you change the setting.

To enable NFS protocol on the CFA, on the main NAS setup screen, click NFS (off) (the links indicate the current status):

To enable NFS protocol, click Enable. (Or, if NFS is already enabled, click Disable to disable the protocol.) The browser will then return to the previous screen.

Making NFS available on a folder

To make NFS protocol available on a folder, either:

  • On the main NAS setup screen (see NAS), click no in the NFS column for the respective folder, or

  • On the disk share configuration screen (see Adding a new share), in the Service Available row, click NFS no.

infoRemember, no indicates the current status of the folder (before you make these changes).

In the General Settings group, select Available to allow access to the folder. You can also enter arbitrary folder notes in the Comment box.

In the Client Specific Access group, you can make the following settings for the folder:

Setting Description
Client The client that the setting applies to. You can use asterisks (*) as wildcard characters to match the setting to multiple clients
R/W When checked, enables write access as well as read access to the client for the export
Async When checked, improves performance at the cost of possible data loss or corruption on unclean server restarts
Any‑port When checked, allows NFS requests from any Internet port number – not just less than 1024
Root When checked, allows remote superuser
Anon When checked, treats all users anonymously
UID When Anon is checked, user ID for the anonymous user
GID When Anon is checked, group ID for the anonymous user

To add additional client lines to the table, click Add Client. Or, to remove the selected (checked) client lines, click Remove Client.

To save these new configuration settings and return to the main NAS screen, click Set.

RAID Configuration

RAID management module provides a simple graphical way to manage the CFA RAID arrays that are present on the system. RAID system does not require any user intervention under normal operating conditions. In the event of a hard drive failure, use this interface to replace the failed drive and repair the RAID array.

infoThis section does not apply to the CFA Model 1200 or vCFAs.

Getting started

infoThese settings are also available via the RAID icon in the lower right of the Management Console.

The bay configuration section shows the logical setup and status of the bays as a table. The table lists the bays, their format, storage capacity, and the status.

The Alarms section shows a list of recently logged messages regarding the status of the individual RAID arrays. For a complete list of the events and their explanations, see Array notification events.

If an array and its constituent drives are operational, the background color of the drive bays is green.

If any of the RAID arrays have problems, the background color of the drives is red, and a red banner is displayed on the View Notices screen. In addition, the RAID icon in the lower right will be red. Any notice will cause the banner behind the View Notices button to turn red:

Identifying a failed disk drive

When the system detects a failed disk drive in one of the redundant arrays, the failed disk drive will be marked with . Once a disk and its associated array have been marked, the first step is to attempt a rebuild. If the rebuild fails, it is likely the failed drive needs to be replaced to restore array integrity. Contact Infrascale Support to confirm, if necessary. Once the new drive has been installed, the associated array must be rebuilt.

infoIf the disk drive was removed or taken offline accidentally, you only need to rebuild the degraded array. (See Rebuild the array.)

Restoring array operation

Once you have identified a failed disk drive, complete the steps in the following sections to replace the drive and restore the array to full operation.

Logically remove the degraded disk

While RAID drives are hot-swappable, to logically remove the disk drive, click the button associated with the drive bay of the failed disk, and then click Offline. (Archive drives must always be prepared for removal.)

When prompted to confirm the Offline action:

  • Click Yes to remove the selected disk (taking it offline), or

  • Click No to cancel the operation.

Once the disk is logically removed, you can no longer select the bay without first using the Rescan button.

Replace disk

Physically remove the bad drive and replace it with a good drive of equal (or greater) capacity. A tested and supported replacement disk can be obtained from your Infrascale dealer or reseller.

To remove the disk, slide the button on the drive bay to the right, which releases a small lever. Pull back on the level until the disk and the mounting sled are released from the CFA.

Insert the new disk and sled into the drive bay until the disk is almost entirely inserted. You should feel a small amount of resistance. Then press the lever to finish inserting and locking the sled into place.

infoDo not remove two or more array disks at one time, or else data loss will occur and you will need to restore the data from an archive.

Rebuild array

Once you have installed and scanned the new disk, you can initiate rebuilding the degraded array. Select the button of the replacement disk, along with the button(s) of any other disk(s) in the degraded array, and then click Rebuild.

The system will begin to rebuild the unit, and the background of the array disks will become yellow. The rebuilding status is displayed with and the status changes to Rebuilding tracking % of completion. When is covered with green slices, the rebuilding process is complete, and the background colors are reset to green.

infoThe rebuild process can take up to two hours per 1 TB. During this time, the system is fully operational but may exhibit reduced performance. The busier the CFA is with other processes while the RAID is rebuilding, the slower the array will rebuild. To maximize rebuild speed, contact Support to stop services. While these services are stopped, backup jobs will not run. This is recommended for very large arrays.

Rescan array

You can scan the RAID for new drives by clicking Rescan. The system will recognize any new drives, including the one just replaced. If the new drive appears to have data stored on it, you will need to format the drive before it can be used for rebuilding the array.

Format new drive

This step may be necessary only if the new drive appeared to have been used before to store non-redundant data. If reformatting is necessary, the system will enable the Reformat button and prevent you from rebuilding the array with this drive until the disk has been reformatted. Reformatting will cause some basic information on the disk to be erased and any previously stored data to be lost. Reformatting should only take a few seconds. Once the drive is reformatted, it can be used for rebuilding a degraded array.

Command button actions

The actions of the command buttons in the displays are summarized in the following table:

Button Description
Refresh Refresh the drive information
Rescan Scan disks for physical changes and update the display presentation
Clear Alarms Clear all alarms
Rebuild Rebuild the array using the selected disk
Offline Take the disks in the selected bays offline, prepare them for physical removal
Reformat Make a disk in the RAID bay or in the archive bay usable for that bay’s function by erasing data on that disk.
This is a high-risk operation. Be careful not to reformat a disk that you used to save data unless you no longer need the data
Verify Initiate the array verification
Stop Verify Stop the array verification

Array notification events

The following table explains the most common messages than can appear in the Alarms box on the RAID status page. These messages will be preceded by the time the event occurred, the bays of the disks involved, and the severity of the message.

infoHere, port is equivalent to a physical disk, and unit is equivalent to an array.
Message Description
Drive error An error was encountered with the disk in the specified bay
Incomplete unit detected Incomplete unit detected disks to bring it online
Rebuild failed An attempt to rebuild an array has failed
Array degraded The system has stopped using a disk in the specified array and has started using the redundant information to retrieve data
Verify failed An attempt to verify the redundant information in an array has failed; the disk drive that contained erroneous data is given
Initialization finished The system has finished creating the redundant information on a new array or on an array that was not cleanly shut down
Initialization started The system has started creating the redundant information on a new array or on an array that was not cleanly shut down
Rebuild finished The system has finished rebuilding a replaced disk with information from the other disks in the specified array
Rebuild started The system has started rebuilding a replaced disk with information from the other disks in the specified array
Verify complete A verification process has finished on the specified array
Verify started A verification process has been started on the specified array
Soft reset occurred The disk has been reset without powering down
Array degraded The specified array has been degraded and should be replaced
Controller error The disk controller of the specified disk has issued an error
Logical array deleted The specified logical array has been deleted
Sector repair occurred Sector repair occurred A sector on the specified disk had reported an error and has been repaired
Encountered bad sector during rebuild During a disk rebuild a bad sector was found
Replacement drive is too small The drive used as a replacement is smaller than the one it is intended to replace
Verify error An error has been found during verification of the specified disk
Drive not supported The specified drive is not supported by the CFA
Unclean shutdown detected If the CFA is not properly shut down, the system does not have time to stop the RAID controllers. This may cause the system to reinitialize the RAID array(s). This initialization process can cause performance degradation while the initialization is in progress. Loss of data may also occur. Turning the power off, pressing the Reset button, or losing power to the box are common ways to cause an unclean shutdown

Status values

The following table describes the messages displayed in the bay configuration and status section.

Message Description
Degraded When the label is applied to an array, the array is compensating for a failed or missing disk by recalculating data from the remaining disks.
When the label is applied to a disk, the system has detected a fault with the disk and is no longer using the disk to retrieve information
Initializing The system is calculating the redundant data used to recover information in the event of a disk failure or loss
Rebuilding The system is recalculating the information of one or more disk drives in an array, usually as a result of a disk drive replacement process
Unused There is no disk in the drive bay
Verifying The system is recalculating the redundant data and comparing it to the data on disk to ensure the integrity of the entire array


Use this section to register the CFA via the Infrascale Dashboard. Registration will link the CFA with the Infrascale Dashboard and allow features such as remote access and cloud replication.

The Cloud Region option determines the location of the cloud endpoint that will be used for cloud replication. It is suggested that you select the region closest to the location of the CFA.

Save/restore configuration

You can use this screen to save and restore CFA configuration files, using the Save Configuration and Restore Configuration buttons, respectively.

infoRestore Configuration restore only client configurations; it does not restore the backup data.


The on-battery runtime of most uninterruptible power sources is relatively short but sufficient to start a standby power source or properly shut down the protected equipment. The CFA provides USB connectivity for most standard UPS battery units. In the event of a power outage, the CFA will run on battery power until a low battery signal is received. At that time, the CFA will execute automatic power-fail shutdown.

The UPS settings can be found under System > Settings. To scan for a battery unit, select UPS and click Rescan.

When the device has been found, the CFA can monitor the power status. If desired, select Shutdown on power failure.

When your options have been selected, apply the settings and close the window.


Storage settings are available in the vCFA Management Console only.

This section displays the usable and licensed capacity of your storage.

It allows you to increase the size of the RAID or the Catalogs volume. After adding additional storage to the vCFA, you will need to complete the wizard to make the newly added storage available to the vCFA.

Monitoring settings

This group provides the tools and resources for effective monitoring of your CFA system.

Audit Log

Director Status

Displays details about the backup kernel version. The tab also shows when the backup daemons were last started and how many jobs have run since then.

Restart Backup Service can be helpful if the backups seem to be locked up or frozen. Keep in mind that this will cause all running, importing, and deduping jobs to stop. If you select this option, you will be prompted to continue.

Disk Thresholds

Use this page to specify when disk space and disk temperature notifications are sent.


Setting Description
From Address (Required) Displayed in the From section when an email notification is sent
Send Email To Email to receive notifications. Can include multiple emails separated by comma
Prepend To Subject Text entered in this field will be added to the front of the subject line of emails sent by the CFA
Email Server Email server to be used to send notifications. By default, localhost is used to send emails directly from the CFA, but you can specify an existing email server
Email Server User Name Email user account name on the email server (if localhost is not used
Password for Email Server Password for the email user account (if localhost is not used

To save the configuration, either:

  • click Submit, or
  • click Send test E-mail that also sends a test email using the saved configuration.


Setting Description
Port Port used on the SNMP management console. Default is 162. Before changing the port, consult the documentation for your SNMP management software
Community Community string. Default is public. Before changing the community string, consult the documentation for your SNMP management software

After SNMP is configured, it will be possible to use the following SNMP protocol data units (PDU) in order to manage your CFA:

  • GetRequest
  • GetNextRequest
  • GetBulkRequest
  • Response

System Alerts

Use this screen to specify the alerts that will be sent as notification emails.

Alerts are divided into several groups, which cover the following:

Alert name Alert description
Audit Alerts  
User Login Notifications  
Daily Audit Summary  
System Alerts  
S.M.A.R.T. Failure  
RAID Alarm Sent when an alert is show in the alarm list in System > RAID Configuration
Disk Over Temp  
System Alert  
New Update  
Disk Storage Utilization  
Hardware Sensor  
System Settings Changed  
Replication Alerts  
Replication Failure Sent whenever a replication failure occurs
Replication Summary Report Summary of replication progress
Communication Failure  
License Alerts  
License Warning  
Communication Failure  
Backup/Restore Alerts  
Job Successful Sent whenever a backup or restore job completes successfully
Weekly Job Summary Summary of all backup and restore jobs during the previous week. Sent on Sunday morning
Lack of Job Progress Sent when a job has been running for some time without sending any data or visiting new files
Media Request Sent when the archive drive needs a new (empty) disk
Archive Completion Sent whenever an archive is completed
VM Auto Register Report  
Daily Appliance Report List of all jobs completed during the day and whether they were successful
Job Failed Sent whenever a backup or restore job fails