I am unable to back up certain files on my system that are in use by other processes. Why is that?
For non-snapshot backups, when Backup Exec encounters a file that is in use by another process, it either skips the file or waits for the file to become available. These actions depend on the options for no-snapshot backups that you configure when you create the backup.
See Files and Folders options.
If you configure Backup Exec to back up open files with a lock, it attempts to open the files in a different mode. It locks these files during backup to prevent other processes from writing to them. Symantec recommends that you close the applications that leave files open so that the files are backed up in a consistent state.
To back up open files on Windows computers, use the Advanced Open File options to configure the backups that use snapshot technology.
See Advanced Open File options.
Why doe the Backup Exec Administration Console continue to own a storage device even when it's not running?
Backup Exec is a client/server application that must always be available to process the jobs that are submitted from both local and remote administrative consoles.
The Backup Exec services claim all of the storage devices that are attached to the Backup Exec server whenever the services are running. Backup Exec requires constant control of the storage devices to collect statistics on media and storage device usage, and to provide media overwrite protection when necessary.
When I run a local backup, the total number of bytes backed up by Backup Exec does not match the number of bytes displayed by Windows. Why?
The type of partition for which the system is formatted may cause this problem.
If you have a Windows NTFS compressed partition, Backup Exec displays the uncompressed byte count of the files that are backed up. Meanwhile, Windows Explorer displays the compressed byte count of the files on the hard drive. For example, Windows compresses an NTFS partition that contains 1 GB of data to 500 MB. Backup Exec reports that 1 GB of data was backed up, even though Windows Explorer displays that only 500 MB of compressed data exists on the hard drive.
If you have a FAT partition, Backup Exec reports the actual number of bytes of the files being backed up while File Manager reports an inflated amount of disk space. For example, a 2 GB FAT partition has a 32-K cluster size and File Manager displays 1.9 GB of used space. Backup Exec reports that 1.4 GB of data was backed up. Assuming that a 50-MB pagefile.sys is excluded from the backup, there is a 450-MB difference in the number of bytes.
Converting to NTFS regains disk space since it is more efficient and the default cluster size (automatically set by Windows) in NTFS is less than FAT. Windows lets you specify a cluster size other than the default; however system performance may decrease. For more information, see the Windows documentation.