Merge pull request MicrosoftDocs#2491 from ktoliver/code-outdent-3-StorSimple-backup-articles-B

fix code (outdent) in three StorSimple backup articles

Author: v-thepet

articles/storsimple/storsimple-configure-backup-target-using-backup-exec.md

@@ -7,7 +7,7 @@ author: hkanna
 manager: matd
 editor: ''
 
-ms.assetid: 
+ms.assetid:
 ms.service: storsimple
 ms.devlang: na
 ms.topic: article
@@ -89,7 +89,7 @@ Although StorSimple presents two main deployment scenarios (primary and secondar
 
 For more information about StorSimple, see [StorSimple 8000 series: hybrid cloud storage solution](storsimple-overview.md) and review the [technical StorSimple 8000 series specifications](storsimple-technical-specifications-and-compliance.md).
 
-> [!IMPORTANT] 
+> [!IMPORTANT]
 > StorSimple device as backup target is only supported with StorSimple 8000 Update 3 or later.
 
 ## Architecture overview
@@ -176,7 +176,7 @@ It is important to size your high-performance volume with ample space and perfor
 
 The deployment of this solution consists of three steps: preparing the network infrastructure, deploying your StorSimple device as a backup target, and finally deploying the Veritas Backup Exec. Each of these steps is discussed in detail in the following sections.
 
-### Configure the network 
+### Configure the network
 
 StorSimple as an integrated solution with the Azure cloud requires an active and working connection to the Azure cloud. This connection is used for operations such as cloud snapshots, management, metadata transfer, and to tier older, less accessed data to the Azure cloud storage.
 
@@ -219,7 +219,7 @@ Ensure that the host backup server storage is configured as per the following gu
 
 - Spanned volumes (created by Windows Disk manager) are not supported.
 - Format your volumes using NTFS with 64 KB allocation size.
-- Map the StorSimple volumes directly to the “Veeam” server. 
+- Map the StorSimple volumes directly to the “Veeam” server.
     - Use iSCSI in case of physical servers.
     - Use pass-through disks for virtual servers.
 
@@ -248,7 +248,7 @@ Configure your solution as per the following guidelines.
     - Download: [PSEXEC – Microsoft Sysinternals](https://technet.microsoft.com/sysinternals/bb897553.aspx)
 
       - After downloading PSEXEC, run Windows PowerShell as an administrator, and type:
-            
+
             `psexec \\%computername% -s schtasks /change /tn “MicrosoftWindowsTaskSchedulerMaintenance Configurator" /disable`
 
 ### StorSimple
@@ -348,7 +348,7 @@ Based on the preceeding assumptions, create a 26 TiB StorSimple tiered volume fo
 
 ## StorSimple as a primary backup target
 
-> [!NOTE] 
+> [!NOTE]
 > Be aware that if you need to restore data from a backup that has been tiered to the cloud, the restore occurs at cloud speeds.
 
 In the following figure, we illustrate mapping of a typical volume to a backup job. In this case, all the weekly backups map to Saturday Full disk, and the incremental backups map to Monday-Friday Incremental disks. All the backups and restores happen from a StorSimple tiered volume.
@@ -360,7 +360,7 @@ In the following figure, we illustrate mapping of a typical volume to a backup j
 | GFS Rotation Schedule for 4 weeks, Monthly and Yearly |               |             |
 |--------------------------------------------------------------------------|---------------|-------------|
 | Frequency/Backup Type   | Full          | Incremental (Day 1 - 5)  |
-| Weekly (week 1 - 4)    | Saturday | Monday - Friday | 
+| Weekly (week 1 - 4)    | Saturday | Monday - Friday |
 | Monthly     | Saturday  |             |
 | Yearly      | Saturday  |             |
 
@@ -385,12 +385,12 @@ The following sequence assumes that Backup Exec and the target host are configur
 
 1.  Assign corresponding StorSimple volumes to your backup schedule.
 
-    > [!NOTE] 
+    > [!NOTE]
     > **Compression** and **Encryption type** are set to **None**.
 
 2.  Under **Verify**, select the **Do not verify data for this job** as this may affect StorSimple tiering.
 
-    > [!NOTE] 
+    > [!NOTE]
     > Defragmentation, indexing, and background verification negatively affect the StorSimple tiering.
 
     ![Backup Options verify settings](./media/storsimple-configure-backup-target-using-backup-exec/image17.png)
@@ -470,14 +470,14 @@ The following table illustrates how the backups should be configured to run on t
 
 StorSimple cloud snapshots protect the data that resides in StorSimple device. This is equivalent to shipping tapes to an offsite facility and if using Azure geo-redundant storage (GRS), as shipping tapes to multiple sites. If a device restore was needed in a disaster, you could bring another StorSimple device online and do a failover. Following the failover, you would be able to access the data (at cloud speeds) from the most recent cloud snapshot.
 
-The following section illustrates how to create a short script to trigger and delete StorSimple cloud snapshots during backup post-processing. 
+The following section illustrates how to create a short script to trigger and delete StorSimple cloud snapshots during backup post-processing.
 
-> [!NOTE] 
+> [!NOTE]
 > Snapshots that are manually or programmatically created do not follow the StorSimple snapshot expiration policy. These must be manually or programmatically deleted.
 
 ### Start and delete cloud snapshots with a script
 
-> [!NOTE] 
+> [!NOTE]
 > Carefully assess the compliance and data retention repercussions before you delete a StorSimple snapshot. For more information on how to run a post-backup script, refer to Veritas Backup Exec documentation.
 
 #### Backup lifecycle
@@ -511,38 +511,37 @@ The following section illustrates how to create a short script to trigger and de
 5.  In Notepad, create a new Windows PowerShell Script and save it in the same location where you saved the Azure publish settings. For example, `C:\\CloudSnapshot\\StorSimpleCloudSnapshot.ps1`.
 
     Copy and paste the following code snippet:
-
-        ```
-        Import-AzurePublishSettingsFile "c:\\CloudSnapshot Snapshot\\myAzureSettings.publishsettings"
-        Disable-AzureDataCollection
-        $ApplianceName = <myStorSimpleApplianceName>
-        $RetentionInDays = 20
-        $RetentionInDays = -$RetentionInDays
-        $Today = Get-Date
-        $ExpirationDate = $Today.AddDays($RetentionInDays)
-        Select-AzureStorSimpleResource -ResourceName "myResource" –RegistrationKey
-        Start-AzureStorSimpleDeviceBackupJob –DeviceName $ApplianceName -BackupType CloudSnapshot -BackupPolicyId <BackupId> -Verbose
-        $CompletedSnapshots =@()
-        $CompletedSnapshots = Get-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName
-        Write-Host "The Expiration date is " $ExpirationDate
-        Write-Host
-
-        ForEach ($SnapShot in $CompletedSnapshots)
-        {
-            $SnapshotStartTimeStamp = $Snapshot.CreatedOn
-            if ($SnapshotStartTimeStamp -lt $ExpirationDate)
-
-            {
-                $SnapShotInstanceID = $SnapShot.InstanceId
-                Write-Host "This snpashotdate was created on " $SnapshotStartTimeStamp.Date.ToShortDateString()
-                Write-Host "Instance ID " $SnapShotInstanceID
-                Write-Host "This snpashotdate is older and needs to be deleted"
-                Write-host "\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#"
-                Remove-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName -BackupId $SnapShotInstanceID -Force -Verbose
-            }
-        }
-        
-        ```
+      ```
+      Import-AzurePublishSettingsFile "c:\\CloudSnapshot Snapshot\\myAzureSettings.publishsettings"
+      Disable-AzureDataCollection
+      $ApplianceName = <myStorSimpleApplianceName>
+      $RetentionInDays = 20
+      $RetentionInDays = -$RetentionInDays
+      $Today = Get-Date
+      $ExpirationDate = $Today.AddDays($RetentionInDays)
+      Select-AzureStorSimpleResource -ResourceName "myResource" –RegistrationKey
+      Start-AzureStorSimpleDeviceBackupJob –DeviceName $ApplianceName -BackupType CloudSnapshot -BackupPolicyId <BackupId> -Verbose
+      $CompletedSnapshots =@()
+      $CompletedSnapshots = Get-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName
+      Write-Host "The Expiration date is " $ExpirationDate
+      Write-Host
+
+      ForEach ($SnapShot in $CompletedSnapshots)
+      {
+          $SnapshotStartTimeStamp = $Snapshot.CreatedOn
+          if ($SnapshotStartTimeStamp -lt $ExpirationDate)
+
+          {
+              $SnapShotInstanceID = $SnapShot.InstanceId
+              Write-Host "This snpashotdate was created on " $SnapshotStartTimeStamp.Date.ToShortDateString()
+              Write-Host "Instance ID " $SnapShotInstanceID
+              Write-Host "This snpashotdate is older and needs to be deleted"
+              Write-host "\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#"
+              Remove-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName -BackupId $SnapShotInstanceID -Force -Verbose
+          }
+      }
+
+      ```
 
 1.  Add the script to your backup job in Veritas Backup Exec, by editing your Veritas Backup Exec job options pre-post commands
 

articles/storsimple/storsimple-configure-backup-target-veeam.md

@@ -7,7 +7,7 @@ author: hkanna
 manager: matd
 editor: ''
 
-ms.assetid: 
+ms.assetid:
 ms.service: storsimple
 ms.devlang: na
 ms.topic: article
@@ -38,7 +38,7 @@ StorSimple is a great backup target for the following reasons:
 -   It automatically provides offsite storage for disaster recovery.
 
 
-## Target audience 
+## Target audience
 
 The audience for this paper includes backup administrators, storage administrators, and storage architects with knowledge of storage, Windows Server 2012 R2, Ethernet, cloud services, and Veeam.
 
@@ -89,7 +89,7 @@ Although StorSimple presents two main deployment scenarios (primary and secondar
 
 For more information about StorSimple, see [StorSimple 8000 series: hybrid cloud storage solution](storsimple-overview.md) and review the [technical StorSimple 8000 series specifications](storsimple-technical-specifications-and-compliance.md).
 
-> [!IMPORTANT] 
+> [!IMPORTANT]
 > StorSimple device as backup target is only supported with StorSimple 8000 Update 3 or later.
 
 ## Architecture overview
@@ -217,14 +217,14 @@ Ensure that the host backup server storage is configured as per the following gu
 
 - Spanned volumes (created by Windows Disk manager) are not supported.
 - Format your volumes using NTFS with 64 KB allocation size.
-- Map the StorSimple volumes directly to the “Veeam” server. 
+- Map the StorSimple volumes directly to the “Veeam” server.
     - Use iSCSI in case of physical servers.
     - Use pass-through disks for virtual servers.
 
 
 ## Best practices for StorSimple and Veeam
 
-Configure your solution as per the following guidelines. 
+Configure your solution as per the following guidelines.
 
 ### Operating system
 
@@ -245,7 +245,7 @@ Configure your solution as per the following guidelines.
     - Download: [PSEXEC – Microsoft Sysinternals](https://technet.microsoft.com/sysinternals/bb897553.aspx)
 
       - After downloading PSEXEC, run Windows PowerShell as an administrator, and type:
-            
+
             `psexec \\%computername% -s schtasks /change /tn “MicrosoftWindowsTaskSchedulerMaintenance Configurator" /disable`
 
 ### StorSimple
@@ -367,7 +367,7 @@ In the following figure, we illustrate mapping of a typical volume to a backup j
 | GFS Rotation Schedule for 4 weeks, Monthly and Yearly |               |             |
 |--------------------------------------------------------------------------|---------------|-------------|
 | Frequency/Backup Type   | Full          | Incremental (Day 1 - 5)  |
-| Weekly (week 1 - 4)    | Saturday | Monday - Friday | 
+| Weekly (week 1 - 4)    | Saturday | Monday - Friday |
 | Monthly     | Saturday  |             |
 | Yearly      | Saturday  |             |
 
@@ -488,14 +488,14 @@ More details on the way to configure Backup Copy Job please refer to [Creating B
 
 StorSimple cloud snapshots protect the data that resides in StorSimple device. This is equivalent to shipping tapes to an offsite facility and if using Azure geo-redundant storage (GRS), as shipping tapes to multiple sites. If a device restore was needed in a disaster, you could bring another StorSimple device online and do a failover. Following the failover, you would be able to access the data (at cloud speeds) from the most recent cloud snapshot.
 
-The following section illustrates how to create a short script to trigger and delete StorSimple cloud snapshots during backup post-processing. 
+The following section illustrates how to create a short script to trigger and delete StorSimple cloud snapshots during backup post-processing.
 
-> [!NOTE] 
+> [!NOTE]
 > Snapshots that are manually or programmatically created do not follow the StorSimple snapshot expiration policy. These must be manually or programmatically deleted.
 
 ### Start and delete cloud snapshots with a script
 
-> [!NOTE] 
+> [!NOTE]
 > Carefully assess the compliance and data retention repercussions before you delete a StorSimple snapshot. For more information on how to run a post-backup script, refer to Veritas Backup Exec documentation.
 
 #### Backup lifecycle
@@ -530,38 +530,37 @@ The following section illustrates how to create a short script to trigger and de
 5.  In Notepad, create a new Windows PowerShell Script and save it in the same location where you saved the Azure publish settings. For example, `C:\\CloudSnapshot\\StorSimpleCloudSnapshot.ps1`.
 
     Copy and paste the following code snippet:
-
-        ```
-        Import-AzurePublishSettingsFile "c:\\CloudSnapshot Snapshot\\myAzureSettings.publishsettings"
-        Disable-AzureDataCollection
-        $ApplianceName = <myStorSimpleApplianceName>
-        $RetentionInDays = 20
-        $RetentionInDays = -$RetentionInDays
-        $Today = Get-Date
-        $ExpirationDate = $Today.AddDays($RetentionInDays)
-        Select-AzureStorSimpleResource -ResourceName "myResource" –RegistrationKey
-        Start-AzureStorSimpleDeviceBackupJob –DeviceName $ApplianceName -BackupType CloudSnapshot -BackupPolicyId <BackupId> -Verbose
-        $CompletedSnapshots =@()
-        $CompletedSnapshots = Get-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName
-        Write-Host "The Expiration date is " $ExpirationDate
-        Write-Host
-
-        ForEach ($SnapShot in $CompletedSnapshots)
-        {
-            $SnapshotStartTimeStamp = $Snapshot.CreatedOn
-            if ($SnapshotStartTimeStamp -lt $ExpirationDate)
-
-            {
-                $SnapShotInstanceID = $SnapShot.InstanceId
-                Write-Host "This snpashotdate was created on " $SnapshotStartTimeStamp.Date.ToShortDateString()
-                Write-Host "Instance ID " $SnapShotInstanceID
-                Write-Host "This snpashotdate is older and needs to be deleted"
-                Write-host "\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#"
-                Remove-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName -BackupId $SnapShotInstanceID -Force -Verbose
-            }
-        }
-        
-        ```
+      ```
+      Import-AzurePublishSettingsFile "c:\\CloudSnapshot Snapshot\\myAzureSettings.publishsettings"
+      Disable-AzureDataCollection
+      $ApplianceName = <myStorSimpleApplianceName>
+      $RetentionInDays = 20
+      $RetentionInDays = -$RetentionInDays
+      $Today = Get-Date
+      $ExpirationDate = $Today.AddDays($RetentionInDays)
+      Select-AzureStorSimpleResource -ResourceName "myResource" –RegistrationKey
+      Start-AzureStorSimpleDeviceBackupJob –DeviceName $ApplianceName -BackupType CloudSnapshot -BackupPolicyId <BackupId> -Verbose
+      $CompletedSnapshots =@()
+      $CompletedSnapshots = Get-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName
+      Write-Host "The Expiration date is " $ExpirationDate
+      Write-Host
+
+      ForEach ($SnapShot in $CompletedSnapshots)
+      {
+          $SnapshotStartTimeStamp = $Snapshot.CreatedOn
+          if ($SnapshotStartTimeStamp -lt $ExpirationDate)
+
+          {
+              $SnapShotInstanceID = $SnapShot.InstanceId
+              Write-Host "This snpashotdate was created on " $SnapshotStartTimeStamp.Date.ToShortDateString()
+              Write-Host "Instance ID " $SnapShotInstanceID
+              Write-Host "This snpashotdate is older and needs to be deleted"
+              Write-host "\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#\#"
+              Remove-AzureStorSimpleDeviceBackup -DeviceName $ApplianceName -BackupId $SnapShotInstanceID -Force -Verbose
+          }
+      }
+
+      ```
 
 6.  Add the script to your backup job in Veeam, by editing your Veeam job
     advanced options pre-post scripts
@@ -573,7 +572,7 @@ It is recommended that you run your StorSimple Cloud Snapshot backup policy at t
 StorSimple as a restore source
 ==============================
 
-Restores from a StorSimple device work as restore from any block storage device. When restoring data that is tiered to the cloud, restores occur at cloud speeds. For local data, restores occur at local disk speed of the device. 
+Restores from a StorSimple device work as restore from any block storage device. When restoring data that is tiered to the cloud, restores occur at cloud speeds. For local data, restores occur at local disk speed of the device.
 
 Veeam enables fast granular file-level recovery through StorSimple using the built-in Explorers in the Veeam console. Use the Veeam Explorers to recover individual items such as email messages, Active Directory objects, or SharePoint items from the backups. The recovery can be done without on-premises VM disruption. You can also accomplish the point-in-time recovery for Microsoft SQL and Oracle Databases. Veeam and StorSimple make the process of item level recovery from Azure both fast and easy. For information on how to perform a restore, refer to Veeam documentation.
 
@@ -614,4 +613,4 @@ The following documents have been referenced in this article:
 
 - [Using GPT drives](http://msdn.microsoft.com/windows/hardware/gg463524.aspx#EHD)
 
-- [Enable and configure shadow copies for shared folders](http://technet.microsoft.com/library/cc771893.aspx)
+- [Enable and configure shadow copies for shared folders](http://technet.microsoft.com/library/cc771893.aspx)