if that file system is accessed from a Unix/Linux client, you can access snapshot by cd'ing into .snapshot directory (dot snapshot). You can be anywhere in the file system tree to cd into .snapshot directory. On a Windows client you access snapshots by right selecting a directory, going into properties and then select Previous Versions.

That really depends on your config and what exactly you want to achieve

I would suggest to involve a local EMC contact for advice

I assume you are using Replicator.

If you use MirrorView or RecoverPoint for sync replication than its different.

You can either do a failover – then the readonly replicated file system becomes available read-write

Or create a writeable checkpoint of the readonly DR file system and use that for testing

In both cases the ftp config isn’t going to be replicated and you need to configure it on the DR site.

Your DR file system might have a different path – that you could fix by either changing the clients or trying with a symlink.

ok, we are using replicator and the FTP file system is replicated and taking checkpoints.  My question was not on how to replicate but more so on how to I access this filesystem ?  Customer does not want to do FAILOVER because production would point to the secondary/DR site.  Customer, with EMC input, has decided that taking a writeable checkpoint would work.  My question is how does a client server know to access this checkpoint?  Where does an IP address get assigned to this chekcpoint ? How does the client server access it ? some type of networking magic ? Again,I'm unfamiliar with NAS storage.  I only know SAN.  I know to map/mask a lun and zone a switch. Do I do the same thing here on this "checkpoint" ? 

the easiers thing would be to export that file system via NFS and mount it from a Linux client. From the linux client you would mount it by the same ip address that you use on the ftp server.

The hidden directory that contains snapshots is .ckpt not .snapshot (got it mixed up with Isilon)