Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Dell EMC PowerMax and VMAX All Flash: TimeFinder SnapVX Local Replication
Executive summary Introduction TimeFinder SnapVX overview
Creating snapshots
Generation numbers
Time-to-live value
Host writes to source
Redirect-on-write
Replication cache
Shared allocations
Linking target volumes to snapshots
Relinking
Unlinking
Defining state
Linking a larger target
Source-volume or linked-target SRP relationships
Restore operations
Cascading snapshots
Reserved capacity
Interoperability
Storage group operations
Secure snaps
Online device expansion
Role Based Access Controls
Implementing TimeFinder SnapVX PowerMaxOS Q3 2020 release enhancements TimeFinder legacy modes: Mirror, Clone, and VP Snap Conclusion Appendix A: TimeFinder SnapVX state table Appendix B: Geometry compatibility mode Appendix C: Monitoring the copy process Appendix D: Nocopy Linked Target behavior before HYPERMAX OS 5977.810.184 Appendix E: Scheduling snapshots with Unisphere for PowerMax Appendix F: System resource planning for capacity and performance Appendix G: Technical support and resources

Relinking

Home > Storage > PowerMax and VMAX > Data Protection > Dell EMC PowerMax and VMAX All Flash: TimeFinder SnapVX Local Replication > Relinking

Relinking

  • The relink command provides the capability to perform incremental refreshes of linked targets. The relink command can also be used to link a target to a different snapshot of the same source volume. The relink command can be issued to both copy and nocopy mode linked targets. This functionality provides an easy way for users to check different points-in-time if they are unsure which one is the best for them to access.

    Note: Just like the link command, relink is in nocopy mode by default unless the user specifies –copy, regardless of the mode of the original link.

    A relink operation is always differential. The target being relinked will be updated with the changes between the two snapshots. If the target is an SRDF R1, the relink operation will propagate the differential changes to the remote array. This applies to both copy and nocopy modes.