two way synchronization

[rudy]

I've got two NAS-R3 servers, same setup.

How to replicate both servers?
I created a volume of 350GB, snapshot 64GB

Shares have data replication enabled.
Created a data replication task under Maintenance -> Backup.
With a interval of 10 minutes ( why not continues synchronization? ).
In the tasks list the replication shows no problems.

When I place a new file on one of the shares sometimes it's replicated, sometimes removed..
Maybe problems with snapshot?

[To-M]

Data Replication is not continues synchronization, so when it is completed replicating files waits until next interval.

Files should not be deleted unless you are doing a cross synchronization to the same shares and this will cause this effect and is not desirable.

Not sure about the snapshot as you have enough assigned space. You could delete and re-create the replication task to see if this happens again.

[rudy]

Files should not be deleted unless you are doing a cross synchronization to the same shares and this will cause this effect and is not desirable.

Yes, I'm doing a cross synchronization.
How to solve this problem?
I want high availabilty, that's why I choose open-e.

[To-M]

Are you replicating to the same shares:

Example:

Source: {share name} Data to Destination: {share name} Data

Then >

Destination: {share name} Data to Source: {share name} Data

If so we do not recommend this. We recommend the following.

Example:

Source: {share name} Data to Destination: {share name} Data

Then >

Destination: {share name} Data to Source: {share name} Data01

In this case you will not overwrite the data if changes on Destination.

[rudy]

If so we do not recommend this. We recommend the following.
Example:
Source: {share name} Data to Destination: {share name} Data
Then >
Destination: {share name} Data to Source: {share name} Data01
In this case you will not overwrite the data if changes on Destination.


I'll try this next monday!
Thank you for your quick reply!

[rudy]

I tried some different setups, but I can't get it two work.
Replication gives no errors, but synchronization doesn't work right.

nas1:
path : /lv0000/www
share name : /www

nas2:
path : /lv0000/www
share name : /www

enabled replication on both shares.

Files aren't replicated in the right way.
When I add some files tot nas1 and to nas2 at the same time, the synchronization goes wrong. Files are placed on the other server, but the files I placed orginally aren't there anymore.

Could you give me the right configuration for this setup?
I also tried the setup you recommended, but I think I'm doing something wrong.
Isn't there any documentation how to solve these problems?

[To-M]

Set the nas2: (Destination Server) first.
path : /lv0000/www
share name : /www
Enable the Data replication agent:
CONFIGURATION -> NAS settings -> Function: Data replication agent.
Then enable the Data replication agent for the share:
SETUP -> NAS resources -> Shares -> [share_name] -> Function: Data replication agent settings.


nas1: (Source Server)
path : /lv0000/www
share name : /www

Assign Snapshot to lv0000 (located in Volume Manager)
Go to Maintenance / Backup / Data Replication
Select Snapshot (lv0000)
Set Data Replication schedule (Now, Interval or scheduled)

[rudy]

This is one way synchronization...

Isn't it possible to setup a two synchronize both servers. So when I put some files on nas1 the files are synct to nas2, and when I add some on nas2 the files are put on nas1?...

[To-M]

Yes but not on the same share going back to NAS1.

[rudy]

Ok, now I understand.

How do I setup a high availabilty setup with two NAS R3 servers?
Is there anything to automaticaly take over first server if it fails?

I saw bonding, but the take over isn't immediately.
What do you recommend?

[To-M]

We do not have Automatic failover in our NAS-R3 (DSS will have this near November this year for the NAS - not sure for NAS-R3). If using Microsoft you can use there clustering feature. If using NFS mounts simply remount to the second NAS share.
If using a bonding I would recommend Balance RR.


Update to Auto Failover!!

Please be advised that Auto-Failover has been delayed - there is no set date or details related to this subject.
We will announce this at a later date. Thank you for your patience on this matter.