![]() ![]() This means the replica is in an application-consistent state and can be cleanly brought back online in the event of failover. In my environment I will only be using VMDK for the virtual storage and can utilise the Nimble built in vCenter synchronization to quiesce I/O during snapshots. The SRA is the main integration point between SRM and Nimble allowing storage interactive workflows to be initiated from SRM. Make sure you review the Nimble Storage Best Practices for VMware Site Recovery Manager guide.Īll Nimble Storage arrays are listed on the VMware Compatibility Guide, and Nimble have been providing a VMware specific Storage Replication Adapter (SRA) since version 5.1 of SRM. It is best practice to have Active Directory and DNS servers already running at the secondary site, and also recommended for virtual machine swap files to be stored in a dedicated datastore without replication. Part 3 – Site Recovery Manager Configuration and Failover Guideīefore beginning ensure that time synchronization and DNS are in place across the Nimble arrays and vCenter / SRM servers. Part 2 – Site Recovery Manager Install Guide Part 1 – Nimble Storage Integration with SRM The following posts in this Site Recovery Manager series detail the end to end installation and configuration process. This post will walk through the steps required to prepare Nimble Storage arrays at primary and secondary sites for VMware Site Recovery Manager (SRM) using array based replication. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |