Skip to content

Commit bb81155

Browse files
committed
Addressing acrolinx score
1 parent 1439957 commit bb81155

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/storage/solution-integration/validated-partners/data-management/komprise-quick-start-guide.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Before deploying Komprise, the target service must be deployed. You can learn mo
107107
- How to create [Azure File Share](../../../files/storage-how-to-create-file-share.md)
108108
- How to create an [SMB volume](../../../../azure-netapp-files/azure-netapp-files-create-volumes-smb.md) or [NFS export](../../../../azure-netapp-files/azure-netapp-files-create-volumes.md) in Azure NetApp Files
109109

110-
The Komprise Grid is deployed in a virtual environment (Hyper-V, VMware, KVM) for speed, scalability, and resilience. Alternatively, you may setup the environment in your Azure subscription using [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/komprise_inc.intelligent_data_management).
110+
The Komprise Grid is deployed in a virtual environment (Hyper-V, VMware, KVM) for speed, scalability, and resilience. Alternatively, you may set up the environment in your Azure subscription using [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/komprise_inc.intelligent_data_management).
111111

112112
1. Open the Azure portal, and search for **storage accounts**.
113113

@@ -218,7 +218,7 @@ Managing object provides different experience. The Director and Observer are pro
218218

219219
## Migration guide
220220

221-
Komprise provides live migration, where end users and applications are not disrupted and can continue to access data during the migration. The migration process automates migrating directories, files, and links from a source to a destination. At each step data integrity is checked. All attributes, permissions, and access controls from the source are applied. In case of an object migration, objects, prefixes, and metadata of each object are migrated.
221+
Komprise provides live migration, where end users and applications are not disrupted and can continue to access data during the migration. The migration process automates migrating directories, files, and links from a source to a destination. At each step data integrity is checked. All attributes, permissions, and access controls from the source are applied. In an object migration, objects, prefixes, and metadata of each object are migrated.
222222

223223
To configure and run a migration, follow these steps:
224224

@@ -229,17 +229,17 @@ To configure and run a migration, follow these steps:
229229

230230
1. Add migration task by selecting proper source and destination share. Provide a migration name. Once configured, click on **Start Migration**. This step is slightly different for file and object data migrations.
231231

232-
1. File migrations
232+
1. File migration
233233

234234
:::image type="content" source="./media/komprise-quick-start-guide/komprise-add-migration.png" alt-text="Specify details for the migration job":::
235235

236-
File migrations provides options to preserve access time and SMB ACLs on the destination. This option depends on the selected source and destination file service and protocol.
236+
File migration provides options to preserve access time and SMB ACLs on the destination. This option depends on the selected source and destination file service and protocol.
237237

238-
1. Object migrations
238+
1. Object migration
239239

240240
:::image type="content" source="./media/komprise-quick-start-guide/komprise-add-object-migration.png" alt-text="Screenshot that shows adding object migration":::
241241

242-
Object migrations provide options to choose the destination Azure storage tier (Hot, Cool, Archive). You may also choose to verify each data transfer using MD5 checksum. This involves additional egress costs as cloud objects must be retrieved to calculate the MD5 checksum.
242+
Object migration provides options to choose the destination Azure storage tier (Hot, Cool, Archive). You may also choose to verify each data transfer using MD5 checksum. Egress costs can occur with MD5 checksums as cloud objects must be retrieved to calculate the MD5 checksum.
243243

244244
2. Once the migration started, you can go to **Migrate** to monitor the progress.
245245

0 commit comments

Comments
 (0)