HP B6960-96035 manual See also Command View CV EVA, See also source volume and target volume

	user rights. Users have the access rights of the user group to
	which they belong.
vaulting media	The process of storing media to a safe and remote place. The
	media are brought back to the data center when they are
	needed for restore or are ready for reuse in subsequent backups.
	The vaulting procedure depends on your company's backup
	strategy and policies for data protection/reliability.
verify	A function that lets you check whether the Data Protector data
	on a specified medium is readable. Additionally, consistency
	within each block can be checked if the backup was performed
	with the cyclic redundancy check (CRC) option ON.
Virtual Controller	(HP StorageWorks EVA specific term) The firmware that manages
Software (VCS)	all aspects of storage system operation, including communication
	with Command View EVA through the HSV controllers.
	See also Command View (CV) EVA.
Virtual Device	(Microsoft SQL Server specific term) This is a SQL Server
Interface	programming interface that allows fast backup and restore of
	large databases.
virtual disk	(HP StorageWorks EVA specific term) A unit of storage allocated
	from an HP StorageWorks Enterprise Virtual Array storage pool.
	Virtual disks are the entities that are replicated using the HP
	StorageWorks Enterprise Virtual Array snapshot functionality.
	See also source volume and target volume.
virtual full backup	An efficient type of synthetic backup where data is consolidated
	using pointers instead of being copied. It is performed if all the
	backups (the full backup, incremental backups, and the resulting
	virtual full backup) are written to a single file library that uses
	distributed file medium format.
Virtual Library	A disk-based data storage device hosting one or more virtual
System (VLS)	tape libraries (VTLs).
virtual server	A virtual machine in a cluster environment defined in a domain
	by a network IP name and address. Its address is cached by
	the cluster software and mapped to the cluster node that is
	currently running the virtual server resources. This way all
	requests for a particular virtual server are cached by a specific
	cluster node.

Concepts guide 397