verify-backup

Description

        verify-backup-Clusteraware <True|False>-lcr Boolean <True|False>-VerifyOnDestVolumes <src_storage_system_list:src_vol:dest_storage_system:dest_vol>-Server <server_name>-ManagementGroup <Standard|Weekly|Daily>-StorageGroup <storage_grp1, storage_grp2, ...>-Database <database1, database2, ...>-ActiveDatabaseOnly <True|False>-PassiveDatabaseOnly <True|False>-BackupTargetServer <server name>-ActivationPreference <ActivationPreferenceNum>-UpdateMirror <True|False>-VerDestVolume <True|False>-Throttle <throttle_val>-VerificationServer <server_name>-UseMountPoint <True|False>-MountPointDir <mountpoint_dir>-CCRActiveNode <True|False>-VerifyBackups <no_of_backups_to_verify>-ReportProgress <True|False>-ArchiveBackup <True|False>-ArchivedBackupRetention <Hourly|Monthly|Daily|Weekly|Unlimited>-VerifyArchiveBackup <True|False>common parameters

This command enables you to verify the SnapManager backup sets with all of the options available through the SnapManager GUI.

-Clusteraware <True|False>

Short name: cl

Assumes significance only when scheduling jobs in cluster configurations, by facilitating scheduling the same job in multiple cluster nodes to improve fault tolerance.

In the case of Single Copy Cluster (SCC), if a job is scheduled with -Clusteraware, the job runs only if the host in which it is scheduled is the active node of the cluster.

In the case of Cluster Continuous Replica (CCR), the processing of -Clusteraware depends on whether the host in which it is scheduled is an active or passive node and the value of -CCRActiveNode. The job runs if the host is a CCR active node and the job targets it with -CCRActiveNode as true. If the host is a CCR passive node, the job runs if the job targets the host with -CCRActiveNode as false.

In the case of DAG, if a job is scheduled with -Clusteraware, the job runs only if the host in which it is scheduled is the active node of the DAG.

-lcr <True|False>

Processed only if the Storage Groups are not specified explicitly using -StorageGroup. In Exchange Server 2007, -lcr is false by default and in such cases only the production Storage Groups are backed up. Note the following points:

• In Exchange Server 2007, set -lcr as true, if you want to back up only the replica Storage Groups.
• If you specify the list of Storage Groups explicitly, the -lcr Storage Group is ignored.

Note: In Exchange Server 2003, -lcr is not supported.

-VerifyOnDestVolumes <src_storage_system_list:src_vol:dest_storage_system:dest_vol>

Short name: vermirror

Overrides the existing SnapMirror relationships.

-Server <server_name>

Short name: svr

Specifies the target Exchange server name.

In a cluster configuration, you need to specify -Server explicitly in all of the cmdlets to perform all operations. If -Server is not specified explicitly in a stand-alone server, SnapManager uses the local machine as the default to run the following cmdlets: new-backup, verify-backup, restore-backup, get-backup, and delete-backup.

-StorageGroup <storage_grp1, storage_grp2, ...>

Short name: sg

Specifies the list of Storage Groups to be verified during the backup operation.

If invalid Storage Groups are specified in new-backup during backup operation, PowerShell cancels the new-backup operation. SnapManager displays an appropriate error message and does not selectively backup any valid Storage Groups. Scheduled jobs and backup scripts also fail when there is an invalid Storage Group configuration.

-Database <database1, database2, ...>

Short name: dbs

Lists the databases in the following format:

-Database "DatabaseName1", "DatabaseName2"

If you do not specify Database, the cmdlet verifies backups of all the databases on the server specified with the -server parameter.

You can verify backups of all mailbox databases in the DAG without specifying each member server of the DAG in the following way:

verify-backup -server DAG1

Note: If the server name specified is a DAG name, and if the ActiveDatabaseOnly or the PassiveDatabaseOnly option is not specified, to select a database for backup you have to specify both the database and the server on which the database resides. For example, specify the databases in the following way:

-Database "db1\server1", "db1\server2"

-ActiveDatabaseOnly <True|False>

Short name: activedb

Verifies the active databases. This is a switch parameter.

Note: If neither the ActiveDatabaseOnly nor the PassiveDatabaseOnly option is specified, backups of all active and passive databases in the Database Availability Group (DAG) are included in the verify-backup operation.

-PassiveDatabaseOnly <True|False>

Short name: passivedb

Verifies the passive databases. This is a switch parameter.

Note: If neither the ActiveDatabaseOnly nor the PassiveDatabaseOnly option is specified, backups of all active and passive databases in the Database Availability Group (DAG) are included in the verify-backup operation.

-BackupTargetServer <server name>

Short name: bkupsvr

Verifies the databases on the specified server.

If you do not specify BackupTargetServer, backups of mailbox databases on all member servers in the DAG are verified. For example, the command verify-backup -server DAG1 will verify the backups of databases on all member servers in the DAG.

-ActivationPreference <ActivationPreferenceNum >

Short name: actpref

Verifies the backups of databases with the specified ActivationPreference number on each member server.

Note: You can use the following cmdlet from the Microsoft Exchange 2010 PowerShell to get the list of ActivationPreference numbers on the member servers for a database: Get-MailboxDatabase -Identity databasename | fl

-ManagementGroup <Standard|Weekly|Daily>

Short name: mgmt

Specifies the backup or verify operation that is scheduled to be performed on a daily, weekly, or standard basis.

-UpdateMirror <True|False>

Short name: updmir

Starts a SnapMirror synchronization after the backup operation.

SnapMirror updates the specified volume to reflect incremental updates to a source volume. If a SnapManager volume is enabled for SnapMirror use, the SnapMirror destination is updated from the source volume.

-VerDestVolume <True|False>

Short name: verdest

Verifies the SnapMirror destination volume.

-Throttle <throttle_val>

Short name: throt

Defines the throttling value to be used during the verification operation.

-VerificationServer <server_name>

Short name: versvr

Overrides the preconfigured SnapManager verification settings. It denotes the host to be used as the verification server for the verification phase of a backup operation. This is a switch parameter.

-UseMountPoint <True|False>

Short name: mp

Mounts the Snapshot copy to a NTFS directory. During a SnapManager verification operation the Snapshot copies are mounted in a default NTFS directory for database verification. This option is effective when there are no drives available to mount the Snapshot copies during database verification. The value of this parameter overrides the preconfigured SnapManager verification settings.

-MountPointDir <mountpoint_dir>

Short name: mpdir

Specifies which mountpoint directory a Snapshot copy is to be mounted to, during database verification.

-CCRActiveNode Boolean <True|False>

Short name: ccrnode

Specifies whether the connection is to an active or a passive node, respectively. This is a Boolean parameter.

-VerifyBackups <no_of_backups_to_verify>

Short form: verbkups

Verifies the unverified SnapManager backup sets. The default value is one, but you can specify the number of backup copies that you want to verify.

-ReportProgress <True|False>

Short form: reppro

Gets the operation status and progress information in the PowerShell output. If this switch is not used, the progress information is logged on only to the report file and not to the PowerShell output.

Note: It is recommended that you do not use this switch for scheduled backup and verification jobs.

-ArchiveBackup <True|False>

Short name: arch

Creates an archive of the backup copy created on the primary node. Primary node is the node where backup operation is initiated. Include this parameter if you have datasets configured on your primary node and want to archive the backup copy to the SnapVault secondary storage system.

-ArchivedBackupRetention <Hourly|Monthly|Daily|Weekly|Unlimited>

Short name: archret

Determines the retention time for the archives that were created using the ArchiveBackup parameter. The retention can be hourly, monthly, daily, weekly, or unlimited.

Note: Do not use ArchivedBackupRetention without using ArchiveBackup. If you use the parameter ArchiveBackup only, the daily retention type is used by default.

-VerifyArchiveBackup <True|False>

Short name: verarch

Specifies that the backup copy that has to be verified is an archived backup copy. If you do not specify VerifyArchiveBackup, and one local and one archived backup copy exist with the same name, SnapManager verifies the local backup copy.