Specify these parameters when you want to change a protected node’s configuration from the PROTECTION CONFIG tab.
|
•
|
Hostname: If you are adding a protected node, type the host name or IP address of the node to protect. This field is display-only under MODIFY.
|
|
•
|
onQ Proxy Service Rev: (This parameter is not applicable for agent‑based enrollment.) The software revision running on the PN proxies.
|
|
•
|
Proxy Host. (This parameter is not applicable for agent‑based enrollment.) This is the ESX/ESXi server that’s hosting the PN proxies.
|
|
•
|
onQ Node Service Rev: (This parameter is not applicable for agent‑less enrollment.) The software revision running on the PNs.
|
|
•
|
Backup Mode: (This parameter is not applicable for agent‑based enrollment.) As outlined in (Workflow) Fail over a PN to an RN and (Workflow) Fail back an RN to a PN, this parameter reflects whether onQ is currently backing up the agent‑less PN (Agentless) or the RN (Recovery Node) in production mode. onQ Portal changes this parameter automatically as it powers on and off the RN.
|
|
•
|
Group Name. A logical means of grouping your PNs. Groups are required to configure startup dependencies as outlined in Configure startup dependencies. For Agent-less PNs, the onQ Portal groups the PNs by ESXi server. If you do not want these PNs in such a group, clear the default Group Name field at the time of enrollment to remove the PNs from this group and place them in the shared pool.
|
|
•
|
Backup Interval. The interval (in minutes/hours) between the start of data backups. As with any backup solution, this interval represents your potential data loss in the event of a failure. The shortest interval is 15 minutes, which is impractical for an onQ that’s protecting a large number of PNs, possibly resulting in queued backups as outlined in Stop in‑progress backups. Use this parameter in conjunction with the Initial Backup Time. If you set the Initial Backup Time for 2AM and the Backup Interval to 24 hours, incremental backups would occur each day at 2AM. To monitor these backups, go to Monitor protected nodes and Monitor backups.
|
|
•
|
Backup Retention Time. The maximum number of days to retain backed-up data that is no longer referenced. The PROTECTION CONFIG tab on a DR Appliance is slightly different from its HA counterpart: the DR version shows the HA Appliance’s backup retention time as well as its own backup retention time; the DR version does not show a protection disabled status because this concept does not exist on a DR Appliance.
|
|
•
|
Initial Backup Time: Select the time of day for the initial backup. Choose a time when the network is the least busy. Select ASAP to begin initial backup as soon as possible; all subsequent backups are measured from this initial backup time using the Backup Interval. The initial backup can take a considerable amount of time. Subsequent backups record only changes that have occurred since the preceding backup and so will be relatively brief.
|
|
•
|
File Backup Only: When set to Yes, squirtcopy backs up up only those files and directories that you specify in the Backup Include List (see Advanced Parameters). This parameter can only be enabled by Quorum Support and is typically used only for file servers. Note the following when this parameter is enabled:
|
|
•
|
Auto RN Creation? parameter is hidden because it is not applicable.
|
|
•
|
Recovery Node Configuration pane is hidden because the protected drives are determined via the Include List.
|
|
•
|
OS Type?: Both Linux and Windows operating systems are supported, though the parameters available vary.
|
|
•
|
Auto RN Creation?: Instructs onQ to create a recovery node for this protected node. See also Modify recovery node creation policy.
|
|
•
|
Disable Protection?: Select Yes or No to disable or enable protection for this node. If you have disabled protection, the most recent re-build of the recovery node is retained but backups are suspended. If you disable protection while a backup is in progress or an RN is being rebuilt, that process continues to completion but further backups are suspended. When you re-enable protection, backups resume and subsequent RN rebuilds are based on the existing RN. See Disable protection of nodes.
|
|
•
|
Number of CPUs: # of CPUs for this recovery node.
|
|
•
|
RN Memory: RN’s memory in GBs.
|
|
•
|
Disk Letter: Disk’s letter, Volume Mount, or CIFs Mount.
|
|
•
|
Mount Point: This parameter varies by platform:
|
|
1.
|
|
2.
|
In the Mount Point text box, provide the path to the directory. For example: C:\Documents and Settings\administrator\My Documents\public.
 |
|
•
|
(Windows) Full path (<mount-point>|<url> where url is //<ip-address>/<path>) to the mounted shared volume:
|
|
1.
|
|
•
|
Format: File system type. This parameter is for Linux only.
|
|
•
|
VDs: # of virtual disks required to hold the configured disk. Every multiple, or portion thereof, of 1980GB requires a virtual disk. For Unix RNs, each configured disk must fit on a single VD: spanning of virtual disks is only supported for Windows RNs.
|
|
•
|
Size: Size of the disk in GBs.
|
|
•
|
+: Adds a new line to the Recovery Node Configuration list.
|
|
•
|
-: Removes a highlighted line from the Recovery Node Configuration list.
|
|
•
|
REVERT button
 : Reverts all the fields to the last saved values. |
ParametersThere are several ADVANCED parameters:
|
•
|
Execute Pre Snapshot script? (This parameter is not applicable for agent‑less enrollment.) Executes before a snapshot starts on the protected node. See Run custom backup scripts.
|
|
•
|
Execute Post Snapshot script? (This parameter is not applicable for agent‑less enrollment.) Executes soon after a snapshot completes on the protected node. See Run custom backup scripts.
|
|
•
|
Enable Filter Driver? (This parameter is not applicable for Linux-based protected nodes and agent‑less enrollment.) See (Agent‑based PNs) Methods of Performing Incremental Backups.
|
|
•
|
Truncate SQL logs after backup? (This parameter is not applicable for Linux-based protected nodes.) After a successful backup, onQ truncates the SQL logs.
|
|
•
|
VSS Copy Only? (This parameter is not applicable for agent‑less enrollment.) onQ’s backup utility clears VSS flags after it performs backups. This process can conflict with some applications that depend on these VSS flags. For example, other backup products can trigger Exchange and SQL Server to truncate log files after incremental backups. Only change this setting to Yes if you are using an application that relies on and updates these VSS flags; otherwise, set this option to No (default).
|
|
•
|
PN Scan Threads: This is the number of threads used during the scan process. The more threads used, the more likely you are to lock up your PN. If you are unsure, specify 1 thread.
|
|
•
|
PN Transfer Threads: The number of threads used during the backup process. The more threads used, the sooner the backup process completes. Ensure that the client machine has enough resources to handle the number of threads you specify. If you are unsure, specify 4 threads.
|
|
•
|
CPU Resource Limit: Sets the CPU usage limit for the backup process on the protected node during the transfer phase. The default is 30% of all cores.
|
|
•
|
Disk Resource Limit: Sets the disk bandwidth limit for the backup process on the protected node during the transfer phase. The default is 170 MB/second.
|
|
•
|
Network Resource Limit: Sets the network bandwidth limit for the backup process on the protected node during the transfer phase. The default is 170 MB/second.
|
|
•
|
Enable Cluster Support?: (This parameter is not applicable for Linux-based protected nodes. Also, for information on how to work with PNs/RNs in a cluster environment, refer to Windows Cluster Services.) If you select Yes, specifies that the node is part of an MSFT cluster (Microsoft Cluster Server/MSCS). In a nutshell, cluster support works by creating a virtual SAN to replicate your physical SAN. The PN accesses the SAN using a virtual IP address. For each volume, the onQ Appliance creates a virtual disk.
|
|
•
|
Cluster Volumes: PN’s volumes/partitions. List of non‑boot drives. From this list, choose the volumes that correspond to your cluster.
|
|
•
|
Virtual SAN IP Address: Any dedicated and unique IP other than the SAN’s physical IP address. This IP address must be on the same subnet as the onQ Appliance’s physical IP address.
|
|
•
|
Virtual SAN Gateway Address: Virtual SAN’s Gateway address.
|
|
•
|
Virtual SAN Subnet Mask: Virtual SAN’s subnet.
|
|
•
|
onQ Proxy Address: Specifies the onQ Proxy that the PN needs to use to communicate with the onQ for backups. Unless your PN is on a separate subnet, leave this field blank. For more information, go to About onQ Proxy.
|
|
•
|
Backup Exclude List: The button shows the exclude list to be either DEFAULT (as defined by Quorum) or CUSTOM (as defined by your administrator). Click the button to modify the backup exclude list for this protected node. See Edit backup exclude list.
|
|
•
|
Backup Include List: onQ backups up only those files and directories that you specify. This button appears if File Backup Only is enabled. See Edit backup include list.
|
|
•
|
Startup Dependencies. onQ will start a given RN after the RNs on which it depends are up and running. See Configure startup dependencies.
|
|
•
|
RN Services. Some services installed on a PN will cause problems if they attempt to run on the RN. In this case, you can configure the startup settings for these services. See Edit RN services list.
|
|
•
|
RN Networks. onQ enables your RNs to run on multiple networks. See Create Custom Networks for RNs.
|
