new-backup

Description

        new-backup-Clusteraware <True|False>-lcr <True|False>-VerifyOnDestVolumes <src_storage_system_list:src_vol:dest_storage_system:dest_vol>-Verify <True|False>-Server <server_name>-StorageGroup <storage_grp1, storage_grp2, ...>-Database <database1, database2, ...>-ManagementGroup <Standard|Weekly|Daily>-ActiveDatabaseOnly <True|False>-PassiveDatabaseOnly <True|False>-BackupTargetServer <server name>-ActivationPreference <ActivationPreferenceNum>-UpdateMirror <True|False>-VerDestVolume <True|False>-NoUTMRestore <True|False>-NoTruncateLogs <False>-Throttle <throttle_val>-VerificationServer <server_name>-UseMountPoint <True|False>-CCRActiveNode Boolean <True|False>-MountPointDir <mountpoint_dir>-RetainBackups <no_of_days_to_retain_backup>-RetainDays <no_of_days_delete_backup>-Command <True|False>-RunCommand <win_path_and_script_name>-GenericNaming <True|False>-BackupCopyRemoteCCRNode Boolean <True|False>-RecoveryPoint <win_path_and_script_name>-ReportProgress <True|False>-ArchiveBackup <True|False>-ArchiveBackupCopyRemoteCCRNode <True|False>-ArchivedBackupRetention <Hourly|Monthly|Daily|Weekly|Unlimited> common parameters

The new-backup command enables you to initiate a backup or verification job, 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.

-Verify <True|False>

Short name: ver

Verifies the backed up SnapManager databases and transaction logs.

-Server <server_name>

Short name: svr

Specifies the target Exchange server name. You can also specify the Database Availability Group (DAG) 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 back up 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 backs up all the databases on the server specified with the -server parameter.

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

new-backup -server DAG1

If a database, for example, MB1, is replicated on three member servers in the DAG, you can back up this database in the following way:

new-backup -server DAG1 -database MB1. This will back up all three copies of the database on all three member servers.

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

Backs up the active databases. This is a switch parameter.

Note: If neither the ActiveDatabaseOnly nor the PassiveDatabaseOnly option is specified, all passive and active databases in the DAG are included in the backup.

-PassiveDatabaseOnly <True|False>

Short name: passivedb

Backs up the passive databases. This is a switch parameter.

Note: If neither the ActiveDatabaseOnly nor the PassiveDatabaseOnly option is specified, all passive and active databases in the DAG are included in the backup.

-BackupTargetServer <server name>

Short name: bkupsvr

Backs up the databases on the specified server. If you do not specify BackupTargetServer, mailbox databases on all member servers in the DAG are backed up . For example, the command new-backup -server DAG1 will back up all databases on all member servers in the DAG.

-ActivationPreference <ActivationPreferenceNum >

Short name: actpref

Back up the databases with the specified ActivationPreference number.

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 frequency of a 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.

-NoUTMRestore <True|False>

Short name: noutm

Denies the retention of up-to-the-minute restore ability.

The logs are also deleted for any backup copies that you delete as part of this backup operation. This does not retain the up-to-the-minute restore ability for older backup copies that remain after the delete phase of a backup operation.

-NoTruncateLogs <False>

Short name: notrunc

Denies the backup of truncated transaction logs. This option can be used to conserve space on the LUN containing the backed up Exchange transaction logs.

-Throttle <throttle_val>

Short name: throt

throttle_var is an integer value; 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.

-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.

-MountPointDir <mountpoint_dir>

Short name: mpdir

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

-RetainBackups <no_of_days_to_retain_backup>

Short name: rtbackups

Specifies the number of backup copies to retain after the delete phase of a SnapManager backup operation.

-RetainDays <no_of_days_to_delete_backup>

Short name: rtdays

Specifies the number of days after which a backup copy is to be deleted. Specifies that the deletion of backup copies is to be based on an "older than number of days" policy. Use this option in conjunction with RetainBackups. Absence of this option denotes a deletion policy based on retained backup count.

-Command <True|False>

Short name: cmd

Indicates that RunCommand is to be used after the current operation. This is a switch parameter.

-RunCommand<win_path_and_script_name>

Short name: runcmd

Specifies the complete path name of and runs the specified command after the SnapManager backup or verification operation is complete.

Note: You need to specify this command explicitly, the preconfigured command does not run after the backup or verification operation.

-GenericNaming <True|False>

Short name: gen

Specifies the generic naming convention to be used for the SnapManager backup sets.

-BackupCopyRemoteCCRNode Boolean <True|False>

Creates a secondary backup on a remote node. This is a Boolean parameter.

-RecoveryPoint <win_path_and_script_name>

Indicates a Frequent Recovery Point backup.

Note: If you specify this parameter new-backup, all the other parameters except -Server, -StorageGroup, -UpdateMirror, -Clusteraware, -lcr, -BackupCopyRemoteCCRNode are ignored.

-ReportProgress <True|False>

Short name: repprog

Displays the operation status and progress information in the PowerShell output. If you do not use this switch parameter, the progress information is logged only to the report file, and not to the PowerShell output.

Note: Avoid using 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.

-ArchiveBackupCopyRemoteCCRNode <True|False>

Short name: arch

Creates an archive of the copy backup created on the secondary node. Secondary node is the remote node of the primary node. Include this parameter if you have datasets configured on the secondary node and want to archive the copy backup 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 the parameter ArchiveBackup. If you use the parameter ArchiveBackup only, the daily retention type is used by default.

ArchiveBackupCopyRemoteCCRNode <True|False>

Short name: archbkupcopy

Archives the backup copies at the remote node specifically for a CCR configuration, as the remote node could be an active node if you run the backup copy from passive node.