The Windows File System iDataAgent on a physical node of the cluster includes the quorum data during a system state backup. It is essential for quorum data to be backed up, as it includes recovery logs as well as cluster configuration and state data. To back up the quorum data on a regular basis, you must ensure that a data protection operation is scheduled for a Windows File System iDataAgent subclient on the physical nodes, with the Backup System State option selected; a system state backup will automatically include quorum data.
When backing up a snapshot of a client computer, ensure that the operating system of the backup server is either same or higher version than the client computer.
It is recommended to perform a full backup after changing or adding and subclient content to ensure that the newly added or modified data is completely backed up.
Ensure that the volume, network or the user quota for an object are not set lower than the amount already used.
Depending upon the backup from which you are restoring the system, install the QSnap either before the full system restore or after the full system restore. The following table explains the scenarios to reinstall the QSnap:
Backup |
Install QSnap |
| QSnap Enabled Backup | Install QSnap before performing the full system restore. |
| QSnap was installed on the source computer after the backup was performed. |
|
If you have authoritatively restored objects that have back-links in another domain, you need to create LDAP Data Interchange Format (LDIF) file and then run the LDIF file on any domain controller in the same domain. Do not run the LDIF file on the same domain controller where you created the file. For more information on how to create and run the LDIF file, refer to http://technet.microsoft.com/en-us/library/cc778643(WS.10).aspx.
By default, the directory junction point gets backed up but the source data (data linked to junction point) is not backed up. This prevents undesired backup and restore of system created directory junction points. To back up the source data of a junction point that is not part of a subclient contents, the source data must be explicitly added to a subclient's content.
During the system state restore some components are staged in the job results folder and then get deleted once the restore of that component is complete. If a file needs to be moved during reboot, the file will not be deleted from the job results folder until the computer reboots.
You can view the log files of an active backup job and use performance counters in the logs to check the performance bottle necks. For more information about how to View the Log Files of an Active Job. A log has following IDs
A log displays time take by each of this process. For example, a log snippet may look as follows:
ID=File Open time, Bytes Read = 0, Total time = 0.011359, Average = 0.011359, Samples = 1
ID=Disk Read time, Bytes Read = 20, Total time = 0.013465, Average = 0.001417, Samples = 1
ID=Pipeline Allocation time, Bytes Read = 0, Total time = 0.000010, Average = 0.000010, Samples = 1
ID=Pipeline Write time, Bytes Read = 1160, Total time = 0.000004, Average = 282.587336, Samples = 1
The time value is in seconds. The highest "Total time" indicates that the majority of the time is spent in that operation. Generally it is the Disk Read Time.
If the time taken by Disk Read operation is high, the disk is the bottle neck. You can use Disk Read utility to verify the disk read performance.
If multiple reads are enabled on the disk, ensure that the hardware supports multiple reads. Enabling multiple reads degrades the performance if the hardware does not support. On the other hand if you have Raid disks or disks that allow multiple simultaneous reads, allowing multiple reads can improve the backup performance.
Slowness can be because of either the network or the media. For troubleshooting this slowness, you can use the testport, DiskRead and tapetest utilities. If the media is a tape, use tapetest utility. If the media is a disk, use DiskReadWrite utility in the write mode. For more information about all the utilities, refer to Tools and Utilities.
Yes. You can perform the backup and restore of the data which is encrypted using the McAfee Endpoint Encryption.
When you enable the Data Classification Scan for a File System, a meta database is created. The meta database contains information about the files in the associated volume. The Data Classification service constantly updates the databases to track file additions, volume additions, content update to files, etc. Journals from the FSF driver are used to keep track of the updates to each meta database.
On each volume, the meta database is created at the following location:
System Volume Information\Bull Calypso \Data Classification
It is named as dc_<instance_number>.db
For example: On the C drive, it would be C:\System Volume Information\Bull Calypso \Data Classification\dc_<instance_number>.db
You cannot relocate the database.
Use the ServiceEnabled registry key to enable or disable the data classification monitoring threads for all volumes on a client computer.
If you want to disable data classification for selected volumes, use the VolumeFilters registry key to provide the list of volumes.
During a VSS backup, the free space needed on a volume for the shadow copy is related to the duration of the backup and the amount of changes being made to the data objects (files, databases) that are being backed up. VSS snapshots capture and copy disk blocks that are being changed by other processes while the backup for a particular object is running. If the backup runs longer, or there is a lot of disk activity (files or databases being changed). This causes VSS to copy more data blocks and therefore, use more disk space.
For Clustered Virtual Servers, use of VSS controls the backup method for file system data only, not system state components; system state data is backed up by the physical node(s), not by the virtual server(s). Note that the physical cluster node will automatically filter all shared disk resources, and the virtual server will automatically filter all physical disk resources from backup operations.
If you use Classic File scan and the select the Check archive bit during backups option, then all backups by VSS on subclients will be converted to full backups. If you want to perform incremental or differential backup, you must use the Change Journal scan. If you want to use Classic File scan, do not select the Check archive bit during backups option.
When you want to backup only data, ensure that the the Backup System State check box is not selected on the Content tab of the Subclient Properties dialog box. Now when you perform the backup for any such subclient, the VSS will filter any system state component from the backup data. VSS will be used for this operation even when Use VSS option is not selected on the General tab of the of the Subclient Properties dialog box.
You can use wildcards to specify a pattern of file names only in the default subclient. For more information, refer to Configuring The Default Subclient for Wildcard Support.
If a subclient contents has brackets which are treated as wildcards, e.g. [!ensure] and [?ensure], ensure that the default subclient is not associated to a subclient policy. If the contents is defined in a subclient policy, it will only be treated as literal path.
In a user defined subclient, you can use the wildcards only in the last level of the path. For example: c:\temp\** or c:\temp\*.doc. Therefore, if you want to use a subclient created in 8.0 version of Windows File System iDataAgent, ensure that the wildcards are present only in the last level of the path.
If you have included a mount point or an UNC path in the subclient, ensure that the wildcards are not present in the path.