Flush Cache .. GUI or CLI ??

G,

You should consider consistency or you data too, i.e. application consistent vs crash consistent. RM would give you application consistency¿

To get application consistency the order of activities should be

1. Quiesce I/O to the source LUN.
2. Flush all cached data to the source LUNs by using the admsnap flush command to flush all server buffers: admsnap flush ¿o driveletter:
3. Replicate data

Admsnap is a prerequisite for your RM installation too.

I hope this helps
Calle

PS What replication method are you using, SAN Copy or MirrorView, and are you going directly from the source LUN?

Thanx for the help, I am using Mirrow/View (Async)

So the admsnap command is just that simple...

admsnap flush ¿o driveletter:

Note the admsnap command will flush server buffers. Your question was flushing of write cache onthe CX which is not necessary. The replication software accesses a LUN object, and the LUN can have data in cache and on disk, it will all be handled properly. That is part of the 'virtualization' that has been in the product for many years.

So whether replicating via host reads fom the LUN, SnapView, MView or MView Async, the write cache state is immaterial. Making sure you have the right process for establishing the remote is important. That is handled in the help and, for advanced techniques, tech notes on Powerlink.