Backup Restrictions and Limitations
Windows
LiveVault has the following backup restrictions for Windows:
-
Shared network drives and volumes. LiveVault does not back up any shared directory that is not located on the local computer.
-
DFS shares: LiveVault does not recognize DFS shares but can be installed on servers where DFS is in use.
LiveVault can only back up data that resides locally on the server where it has been installed. One aspect of DFS is to organize multiple shares across a network and let multiple physical file servers use a single logical network path. LiveVault will not identify all of these network locations; you must install the software on all the physical servers where this data resides. A separate aspect of DFS is file replication, which replicates changed files across all servers.
Note: Domain-based DFS roots exist within Active Directory, but will be automatically excluded from System State backup by the LiveVault agent. It can be protected by a Standard file/directory backup policy. -
Direct File System and RAW file system: LiveVault does not back up Direct File System drives or the RAW file system. .
-
Disk and partition configuration: LiveVault does not back up disk and partition configuration information.
-
Extremely large directories: Directories with more than 500,000 files are not supported by default.
Contact Support for assistance with this functionality. See Backing up and Restoring Directories with more than 500,000 files.
Linux
LiveVault has the following backup restrictions for Linux:
-
Open files: LiveVault does not provide special handling for files that are open when backup runs. If a file is open when it is backed up, incomplete data can be backed up in that version.
LiveVault lets you create and run scripts before and after backup which could for example automatically stop the application and close the files before backup runs. See Run Scripts Before and After Backup.
-
Databases: LiveVault does not use special technology to provide transactionally safe database backup. To guarantee transactionally safe database backup, LiveVault enables you to create and run scripts before and after backup that can, for example, stop the database, back up the database, then start the database.
-
Filename encoding: LiveVault encodes filenames based on the locale of the server at backup time.
If the locale is changed on the server while LiveVault is installed, it can lead to filenames that do not match the backup rules and thus being excluded from backup.
To prevent encoding problems of this sort, do not change the locale on the Linux server once LiveVault is installed.
-
Mount points: LiveVault supports backup of local mount points, but you must specify each mount point individually in order for it to be backed up. For example, if
/
is the root, but/usr
is mounted, you need to specify/usr
directly in order for it to be backed up. It will not be backed up automatically if you back uproot
. -
Symbolically linked data: If you specify a local directory tree to back up and the top of the directory tree is a symbolic link, you must specify the actual directory tree containing the data that you want to back up. If you choose to also back up the symbolic link, you can specify the symbolic link for backup.
-
Raw disks: LiveVault does not back up raw disks.
-
Device files: LiveVault does not preserve device files.
-
NFS mounted filesystems: LiveVault does not back up NFS mounted filesystems.
-
CD-ROM filesystems: LiveVault does not back up CD-ROM filesystems.
-
Swap filesystems: LiveVault does not back up swap filesystems.
-
Floppy drives: LiveVault does not back up floppy drives.
-
Extended Attributes: LiveVault does not support extended attributes.