vxsnap prepare


vxsnap prepare
Prev	vxsnap	Next

For Exchange and volume operations:

vxsnap prepare component=<ComponentName>/writer=<WriterName>
[-b] [source=<Volume>/harddisk=<Hardisk>...]

Creates snapshot mirrors of the volumes in the specified component and eliminates the need for multiple vxassist prepare commands. The snapshot mirrors remain attached to and synchronized with the original volumes.

Note:

Either the prepare or start keyword may be used in the CLI, however prepare is recommended.

The following attributes apply:

component=<ComponentName>	Name of the component; for Exchange, this is the storage group name found in the Exchange System Manager, for example, "First Storage Group".
writer=<WriterName>	Unique ID of the VSS writer, for example, "Microsoft Exchange Writer".
-b	Run the process as a background process.
source=<Volume>	Indicates the source volume for the snapshot mirror that is specified by a drive letter, drive path (mount point), or volume name of the form "\\?\Volume{GUID}\".
harddisk=<Harddisk>	Name of the disk where the snapshot mirror is created, for example, harddisk2.

Example

vxsnap prepare component=SG2/writer="MicrosoftExchange Writer" 
source=L:/harddisk=harddisk2source=M:/harddisk=harddisk3

This command creates snapshot mirrors of all the volumes that the Exchange component contains. The snapshot mirror of the volume that is mounted on L: is created on disk 2 and the snapshot mirror of the volume that is mounted on M: is created on disk 3.

For Enterprise Vault operations:

vxsnap prepare [-b] writer=<WriterName>  
[site=<SiteName>[/VSG=<VSGName>[/VS=<VSName>]]]
[[/]component=<ComponentName>]

Creates snapshot mirrors of the volumes in the specified site, vault store group, vault store, or component. The snapshot mirrors remain attached to and synchronized with the original volumes.

Note:

Either the prepare or start keyword may be used in the CLI, however prepare is recommended.

The following attributes apply:

-b	Run the process as a background process.
writer=<WriterName>	Unique ID of the VSS writer, for example, EnterpriseVault. Required if you specify the component.
site=<SiteName>	Name of the Enterprise Vault Site.
VSG=<VSGName>	Name of the Enterprise Vault Vault Store Group
VS=<VSName>	Name of the Enterprise Vault Vault Store
component=<ComponentName>	Name of the Enterprise Vault component. For example, VaultStore database, Fingerprint database, or Volume Component, such as index, partitions, etc.

Note:

Any text string that contains spaces must be enclosed in quotation marks.

Additional information about the prepare operation for Enterprise Vault:

Specifying only the writer attribute (as in vxsnap prepare writer=EnterpriseVault), results in the preparation of the components of the entire Enterprise Vault farm. This would include the Enterprise Vault directory database, monitoring database, audit database, and reporting database.
Specifying the site attribute (as in vxsnap prepare writer=EnterpriseVault Site=Site1), results in the preparation of the components at the Enterprise Vault site level. This prepares the directory database and all the components (SQL and volume) in the specified site.
Specifying the vault store group attribute (as in vxsnap prepare writer=EnterpriseVault Site=Site1/VSG=VSG1), results in the preparation of the fingerprint database and all the components in all vault stores in the specified vault storage group.
Specifying the vault store attribute (as in vxsnap prepare writer=EnterpriseVault Site=Site1/VSG=VSG1/VS=VS1), results in the preparation of the vault store database and all the partitions in the specified vault store.
Specifying the component attribute (as in vxsnap prepare writer=EnterpriseVault Site=Site1/VSG=VSG1/VS=VS1 Component=<Component Name>), results in the preparation of the specified component. The component can be an Enterprise Vault SQL database or a volume component (e.g.vault store database, fingerprint database, directory database, monitoring database, reporting database, audit database, partition, index volume, etc.).
- For vault store components: When the vault store database component is specified, the open partition in the vault store is also prepared.
- For vault store components: When the open partition component is specified, the vault store database in the vault store is also prepared.
- For different components: When different components reside on a common volume, the volume is prepared only once.
Upon completion of the operation, the status (success or failure) of the selected components is recorded in a log, %VMPATH%\logs\EVStatus.log. The log contains information about the success or failure of the operation for the components. In the event that the prepare of a volume for a component fails, the operation continues to prepare the remaining volumes of the component and any other requested components. If the operation succeeds for all the volumes of a component, then the status of the component is logged as a success. If the operation fails for any one of the volumes of the component, then the status of the component is logged as a failure along with the cause of failure.

Example

vxsnap prepare writer=ev site=site1/vsg=vsg1/vs=vs1 
site=site2 component="Index Location (V:)" 
component="Directory DB"

The command prepares all the volumes for a snapshot for the Enterprise Vault Store vs1 of site1/vsg1, Index Location (V:) of site2 and Directory DB.

For SQL operations:

vxsnap prepare component=<ComponentName>/writer=<WriterName>
[server=<ServerName>][instance=<InstanceName>][-b]
[source=<Volume>/harddisk=<Hardisk>...]

Creates snapshot mirrors of the volumes in the specified component. The snapshot mirrors remain attached to and synchronized with the original volumes.

Note:

Either the prepare or start keyword may be used in the CLI, however prepare is recommended.

The following attributes apply:

component=<ComponentName>	Name of the database. The command prepares mirrors for both the database and log volumes of the SQL database.
writer=<WriterName>	Unique ID of the VSS writer, for example, SQLServerWriter or the GUID for the writer. Required if you specify the component.
server=ServerName	SQL Server server name.
instance=InstanceName	SQL Server instance name.
-b	Run the process as a background process.
source=<Volume>	Indicates the source volume for the snapshot mirror that is specified by a drive letter, drive path (mount point), or volume name of the form "\\?\Volume{GUID}\".
harddisk=<Harddisk>	Name of the disk where the snapshot mirror is created, for example, harddisk2.

Note:

Any text string that contains spaces must be enclosed in quotation marks.

Example

vxsnap prepare component=billing_DB/writer=SQLServerWriter
source=L:/harddisk=harddisk3
source=M:/harddisk=harddisk3

This command creates snapshot mirrors of all the volumes that the billing_DB database contains. The snapshot mirror of the volume mounted on L: will be created on harddisk 3 and the snapshot mirror of the volume mounted on M: is also created on harddisk 3.

Note:

Ensure that the [NT AUTHORITY\SYSTEM] account is granted the sysadmin server role (from SQL Management Studio Console) on each node. This is applicable for SQL Server 2012 or later.