Eclipsys1

updated

17 years ago

E

Eclipsys1

13 Posts

0

367

September 1st, 2009 11:00

Replicator V2 Growing pains

We are cloning file systems and I have tried both copying as well as replicating. If I stop the replication and I want to start it again and it may have been stopped for a number of days, I can't start it. I get this screen:

Current Local:server_2 test Local:server_2 test_replica1 loopback
New Local:server_2 test Local:server_2 test_replica1 loopback

Sometimes I can start it but if I let it sit for maybe a day, I can't. It tell me that the destination is not empty or not the same and then fail to start. All we want to do is clone file systems to test patching. I have been told that replication is the way to go and avoid copying. I also understand that once the copy is complete, I would have to run another job if I wanted to update the destination file system but if I replicate, I can refresh the destination. Do I always have to keep the replication session active to do this?

Suggestions??
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    126

    0

    Posted September 2nd, 2009 09:00

    I would first make sure that you use a recent DART version - at least 5.6.44
    there have been quite a number of RepV2 bug fixes lately

    If you just want to test and later throw it away you could also use writable checkpoints as well

    Both nas_copy and replication allow for incremental update

    replication is more geared towards automatic updates

    I havent tried replication with manual refresh, but I think nas_copy is a bit more work since you have to refresh the checkpoints manually

    If you are at a recent DART and still have problems I suggest to open a service request so that customer service can troubleshoot why

    Rainer