Backup mode cmdlets

Enterprise Vault provides a set of PowerShell cmdlets which you can use to set and clear backup mode on the following:

You can run these cmdlets directly in the Enterprise Vault Management Shell, and use them in your backup scripts. For example, use the cmdlets in a pre-backup script to set backup mode on index locations and vault stores before the backup is taken. After the backup has completed, use the cmdlets in a post-backup script to clear backup mode when the backup has completed.

To run PowerShell cmdlets directly, first run the Enterprise Vault Management Shell

PowerShell opens and loads the Enterprise Vault snap-in which makes the backup mode cmdlets available in the shell.

The Enterprise Vault Management Shell provides the following backup mode cmdlets:

Cmdlet

Description

Get-IndexLocationBackupMode

Reports the current backup mode settings on index locations.

Set-IndexLocationBackupMode

Sets backup mode on index locations.

Clear-IndexLocationBackUpMode

Clears backup mode from index locations.

Get-VaultStoreBackupMode

Reports the current backup mode settings on vault stores.

Set-VaultStoreBackupMode

Sets backup mode on vault stores.

Clear-VaultStoreBackupMode

Clears backup mode from vault stores.

Help is available for all the cmdlets. For example, the following command shows the detailed help for Clear-VaultStoreBackupMode:

Get-Help Clear-VaultStoreBackupMode -detailed

You can also generate PowerShell backup mode commands that are based on the configuration of your environment and ready for use in your backup scripts.

See Generating PowerShell backup commands for your environment.

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.