Meet DataCore: Data Infrastructure for Next-Generation Data Centers
DataCore parallel I/O and virtualization technologies deliver the advantages of next generation Join this webinar to meet DataCore, learn about what we do and how we can help your business. Haluk Ulubay, Senior Dir., Marketing DataCore Software Software-defined storage services that continuously replicate data. Replication Operations. Create replication. Creates a relationship between two virtual disks on different DataCore Servers and causes the data on the source. Compare DataCore Hyper-converged Virtual SAN vs vCenter Server. Marketing · Enterprise Video · Marketing Automation · Nonprofit Constituent Relationship . The Linked Mode allows you to replicate permissions, licenses and roles. There are similar products in the market, both commercial as well as open source.
To enable test mode: The replication status will temporarily reflect Standby off-line while test mode is being activated. Test mode in the Replication tab will change from Disabled to Active. The icon for the virtual disk in the panels will change from grey paths disabled to the standard icon reflecting a healthy virtual disk. Data on the standby and active sides of the virtual disk may differ due to the remaining replication data see Remaining Data under Performance in the Replication tab.
To disable test mode: The replication status will temporarily reflect Standby off-line while test mode is being exited. Test mode in the Replication tab will change from Active to Disabled.
The icon virtual disk icon in the panels will change from healthy to grey paths disabled. Activating and Deactivating Replications Either activating or deactivating a replication causes the current replication direction to be reversed.
A virtual disk in Active status can be deactivated and a virtual disk in Standby status can be activated. When either operation is performed, the "active" virtual disk becomes the "standby" virtual disk and the "standby" virtual disk becomes the "active" virtual disk. Front-end paths to the host are enabled on the new "active" virtual disk in order to receive write operations and the front-end paths to the host are disabled on the new "standby" virtual disk to prevent write operations.
Activating or deactivating a replication can be performed from either the active or standby side of a replication. This can be accomplished by performing a clean shut down on the host.
The active virtual disk will be deactivated after files in the buffer have transferred. This process can take a considerable amount of time, depending on the amount of files to transfer.
Also, ensure that the virtual disk that is being activated, has a replication buffer assigned. To activate or deactivate a replication: Do not perform both. Click Yes to continue. Canceling Deactivation If a virtual disk is deactivated in error, while the virtual disk is in the process of Deactivating which is a transitional state, the deactivation operation can be canceled.
To cancel the deactivate command: When a controlled or emergency failover is necessary, the roles of the source active and destination standby virtual disks must be swapped in order to reverse the direction of the replication.
This can be accomplished by either activating the standby side or deactivating the active side of a replication. When replication direction is reversed, the paths from the host to the virtual disk being deactivated will be disabled and the paths from the host to the virtual disk being activated will be enabled.
Data changes made by the host at the failover site are added to the replication buffer on the DataCore Server at the failover site. When the production site is functional again, the virtual disks at the production site can be activated again failback. Data changes will be transferred from the replication buffer on the DataCore Server at the failover site to the DataCore Server at the production site. The procedures for a controlled failover and an emergency failover differ somewhat; please follow the correct instructions based on the situation.
This operation can be performed from either the source or destination. Either of these actions will cause the source virtual disk to go into the Deactivating state and the destination virtual disk will go into Activating state while the buffer files on the source are being transferred to the destination. At the same time, the destination virtual disk will go into the Active state and become the new source of the replication and paths to the virtual disk will be enabled.
Read and write operations to the host at the failover site will be processed on the virtual disk at the failover site and replicated to the production site. Since the DataCore Server at the production site is unavailable, operations will be performed from the destination server at the failover site. The destination virtual disk is currently in Standby state. The virtual disk can be served to a host and used from the failover site.
In order to failback, a replication buffer must be assigned on the DataCore Server at the failover site. Confirm the operation to continue. Checkpoint Markers Checkpoint markers can be used to update existing snapshots on the destination. Checkpoints can also be used as triggers and actions for configured tasks. The snapshot to be updated must exist and should be selected for the destination virtual disk on the destination server.PHD Virtual (a Unitrends Company) and DataCore: Data Protection, Disaster Recovery for Virtual Cloud
Since the checkpoint is a marker in a data transmission and latency does occur, the action will be delayed in time. Data on the source virtual disk should be in a known good state. The virtual disk must be in the Active replication state.
To select a snapshot to update on the destination server: To mark a checkpoint: Open the Virtual Disk Details page for the virtual disk used as the source of a replication. The operation will be logged in the Operations Panel and an event message is logged. The checkpoint will be inserted into the data stream and transferred to the standby virtual disk on the destination server.
Pausing and Resuming Data Transfers Replications can use considerable network resources.
How to Avoid Disasters via Software-Defined Storage Replication & Site Recovery
If an occasion arises when it is necessary to free-up those resources in order to expedite a different process or activity, or if the network is experiencing problems, data transfers can be temporarily paused and resumed later.
In the event of heavier than usual traffic on the network, data transfers can also be paused until traffic subsides then resumed.
- How to Integrate Hyperconverged Systems with Existing SANs
- Meet DataCore: Data Infrastructure for Next-Generation Data Centers
- Replication Operations
When a replication is paused, other replication operations cannot be performed on that replication. To pause or resume data transfers: Splitting Replications The replication configuration between source and destination virtual disks can be split removed. Data transfers must be active in order to split a replication.
This operation can be performed from the source or destination. When the split operation is invoked, an end-of-stream marker is inserted at the end of all files that currently exist in the buffer and the replication goes into Splitting state; therefore, all data files that existed in the buffer at the time that the split operation is invoked will be processed.
When the marker is received at the destination, the split will be completed. This will leave both source and destination virtual disks in the same state as when the operation is invoked. After the split replication operation is invoked, new data changes will continue to be added to the buffer, but when the marker is received at the destination, any files that were added after the command was initiated will be deleted from the buffer and will not be transferred to the destination virtual disk.
The splitting process can take a considerable amount of time. To stop replication immediately, the replication split can be forced.
How to Avoid Disasters via Software-Defined Storage Replication & Site Recovery
Use caution when a virtual disk is using duplicate disk IDs and is involved in replication. To split a replication configuration: The replication state will change to "splitting" until the operation is complete. Forcing the Split Replication The split replication can be forced under two different circumstances: The replication split can be forced to stop replicating immediately and perform the split.
When a split replication is forced, replication stops immediately new data files are not created and all data that exists in the buffer is deleted immediately instead of transferring it to the destination.
Forcing the split replication operation is useful when there are many files to be transferred and it is not important to leave the source and destination virtual disks in the same state as when the split replication operation is invoked. In these cases, the only option is to force the split. Forcing the split replication operation will leave the standby virtual disk in an unusable condition unless the split can be performed from both replication partners.
To force the split replication operation: This will leave the standby virtual disk in a usable condition. The replication state will change to "splitting". Click Yes to continue with the operation. Cancelling the Split Operation The split operation can be cancelled while the replication status is in the process of splitting.
To cancel the split operation: The location of the replication buffer can be assigned or changed using the instructions below.
The path to the replication buffer can be changed on-the-fly, even if active replications exist. Any replication files existing in the original folder will be transferred and then the replication files will be deleted. The original folder will not be deleted. Like always in real life, there is no clear black or white, but some circumstances you should be aware of — especially if you intend to leverage these technologies.
You may ask yourself: Do I need to rip and replace my existing storage? What is the best way to integrate both? What benefits do I receive? Sep 25 41 mins Augie Gonzalez, Director of Product Marketing, DataCore Software Shifting weather patterns across the globe force us to re-evaluate data protection practices in locations we once thought immune from hurricanes, flooding and other natural disasters.
Offsite data replication combined with advanced site recovery methods should top your list. Aug 22 53 mins Augie Gonzalez, Director of Product Marketing, DataCore Software Business continuity, especially across data centers in nearby locations often depends on complicated scripts, manual intervention and numerous checklists. Those error-prone processes are exponentially more difficult when the data storage equipment differs between sites. Such difficulties force many organizations to settle for partial disaster recovery measures, conceding data loss and hours of downtime during occasional facility outages.
You also know that you need technology that enables rather than hinders you, and you may be wondering how some leading-edge healthcare organizations are making this happen right now. Audience members that have an affiliation with any area of healthcare, medical, life sciences, or similar areas will be treated to a very special healthcare-specific presentation from data center technology provider DataCore.
Jun 27 54 mins Alwin Kohl, Sr. Product Marketing Manager - DataCore If you were to pose this question to your storage vendor or VMware support today, you would be likely to receive the answer: Use of local discs alone or in combination with other storage arrays as part of the Virtual Volumes datastore would even be sufficient. Discover in our expanded live demo: O How to setup such a solution in real life O How to implement auto-tiering across different arrays Hyperconvergence - Getting Started with Hyperconvergence Recorded: