I don’t know what most people know about TimeFinder, so I’ll start with a short introduction.
EMC Timefinder was developed to provide customers with a dynamic mirror they could use to try and cut some of the tediousness out of copying data, whether from one host to another or within the same host.
When I was working for EMC, Timefinder was still more or less in it’s infancy, and only came in one flavor.Â (Now referred to as “TimeFinder/Mirror”)
A Timefinder volume is a volume that is essentially a dynamic mirror of a production volume.Â Called a ‘BCV’ (for Business Continuance Volume) it was a straight 1:1 mirror of your production data.Â (If you were running in a 2-Way-Mirrored configuration, the BCV essentially become a third mirror.)Â At a point-in-time, you could split the third mirror off it’s production pair and make it available to another host.
The main benefits were obviously discovered in Backup.Â You could split a BCV of your production data off, mount it to another host, and back it up to a locally attached tape library with zero network overhead.Â Using this you could also use a single backup host to back-up copies of BCV’s from multiple production hosts.
Another good use for BCV’s was in development.Â One story I like to tell was from I was an admin several years ago.Â Developers liked to “break” their database on a friday afternoon, knowing that the restore from tape would take the better part of a day and in doing so they guaranteed they would make their tee-time.Â With the advent of TimeFinder, I was able to tell them “Not a problem, I’ll have it back up in 20 minutes.”Â Â The reason being that I could restore from the mirror almost instantly.
The main negatives for TF/Mirror are that in all cases, the initial synchronization has to complete before the data can be made available to the target system.Â Now this is mitigated by the fact that after the initial relationship is established all further mirrors are incremental, meaning that only changed tracks are copied to the BCV volume, but it can still be a time consuming process.
Now EMC has come out with two new forms of TimeFinder in Symmetrix, very similar to the Clariion functionality.
Â Â SNAP uses a process called “Copy On First Write”.Â Â This uses a much smaller volume than the production volume as a “virtual device”Â (Called a VDEV)Â Â The VDEV serves as a list of pointers for each track in the volume.Â Reads are serviced from the original volume until the track is changed.Â When the track is changed the original data is copied to a cache area, and the pointer for this track in the VDEV device is changed to point to the cached original track.Â In doing this the VDEV device will contain an exact copy of the production data as it was when the Snap session was activated.Â When the data is no longer needed, you terminate the Snap session and the cached changes are discarded.
The data is available the instant the SNAP session is activated.
The downside to this is that all reads touch the production volumes.Â In a heavily utilized system there can be a noticible impact.Â Another negative is that SNAP sessions are limited to the amount of cache set aside.Â A usual configuration is to set aside about 20% of the area used by production as “SnapCache”Â This can then be used as needed.Â If the SnapCache fills up, the Snap session ends and that is that.
Â Â Clone uses another process, similar to SNAP, called “Copy On Access”.Â Clone volumes are identically sized to the production volumes, which of course uses up more space, but provides for a more permanent home.Â This provides theÂ data permanance ofÂ TimeFinder Mirror, the speed of TimeFinder Snap, and the agility to move data from Standard volume to another standard volume. (Raid-1 production volumes to Raid-5 Development volumes is a good example)
What copy-on-access offers is the unique ability to use the volume before it’s actually finished mirroring.Â When a clone session is first started, all the target volume contains are pointers to the source volume.Â Every time a track is accessed, (read or write) it is copied to the target volume first.Â (prior to any write operations)Â If no options are selected this is the only time a track is copied.Â If the -copy option is selected when the Clone session is created, a background copy of the production volume is started.Â This will eventually result in a copy of the data that will persist after the clone session is terminated.Â (when no option is specified, the data will disappear when the session is terminated)Â There is also the option to copy (mirror) the entire production volume to the target volume before the session is activated.Â This is called “Precopy” and is a close emulation to what is done using TimeFinder mirror without the limitations of having to use BCV’s as targets.
TF/Clone has to be the best of all worlds.Â It gives you the flexibility of Snap with the data-resilience of Mirror, and the flexibility of being able to go from one volume to another without restrictions on what type of volume your target is.Â (TimeFinder/Mirror requires the use of BCV volumes)
Timefinder is the production that gave me my introduction into EMC.Â TimeFinder and SRDF are also the technologies I’ve implemented more often than any others in my work for (and with) EMC.
If you’ve got questions, feel free to post them.Â You’re probably not the only ones.