Printable View
2 boxes with 3518.
I have problems replicating the NAS Volumes, because I cannot see any destination volume on the source filer.
What i've done:
Created a NAS Volume with Repl. on each filer. Set one as source and the other as destination. Giving the IPs of each other. But cannot see any dest. vol.
Am I missing something?
regards
Matthias
Hi Mhubert
Are you using data or volume replication ?
If volume replication, make sure the volumes are the exact same size.
( I type the volume size to be sure)
can you ping the dest from the source ?
If you are using the Volume Replication for NAS you wont see the Destination until you switch the roles from Source > Destination and Destination (Clear Metadata) > Source.
Hi symm,
i am using volume replication.
both boxes can see and ping each other.
the source volume is 500GB and has already data and shares on it. Replication was enabled afterwards.
on destination site, i cretaed a new 500GB volume with replication enabled at creation time. Could this be a problem? Both volumes show a size of 500GB + 0.12 reserved for replication.
cheers
Matthias
Hi Todd,
not quite sure what you mean, i changed the roles on source filer to destination and on destination filer to source and back again, but i still can't see any dest volume on source filer.
regards
Matthias
Did you clear the Meta data?
Clearing metadata is required when you want to start the replication process from the beginning. Another usage example is when the data on the source volume is inconsistent and you want to restore it from the destination volume. In this situation you need to switch replication modes between the volumes (i.e. the destination volume should now be in source mode, while the previous source should be switched to destination mode). Before starting a replication for a new source and destination please clear the metadata from the previous destination volume. When replication is complete the data on the previous source volume will be consistent. If a volume is set to the destination replication mode then it will not be visible in the iSCSI initiator.
yes, i cleared the metadata. But why should there be any metadata? I want to start a new replcation task.
Maybe I should explain in more details:
on my primary DSS I have two existing NAS Volumes, which I want to replicate to the secondary DSS. Therefore I enabled the replication option on the primary (which broke my existing NFS sessions, by the way) and created two new volumes with replication on the secondary. Now I want to setup a new replication task on the primary but can't see any volume from my secondary DSS in the "Destination Volume" field, no matter what I change from "Source", "Destination" or "Clear Metadata". Mirror IP is correct.
regards
Matthias
Sounds like it should be working
Are both systems on the same subnet ?
How far away is the destination DSS?
If the destination is in another location did you enable replication over WAN?
Yes, they are on the same subnet and can ping each other.
It has already worked with version 3278, now i have 3518.
cheers
Are both systems on the same version Source - 3518 & Destination - 3518?
Check this doc out and verify the steps.
http://www.open-e.com/library/product-presentations/
Open-E Replications
2008 - Open-E DSS Synchronous Volume Replication over a LAN, April 2009
Yes, both have version 3518.
and I have done the first setup regarding to the document mentioned.
I do have a ticket with support for this problem.
regards
What is the ticket #?
Ticket #1009665
cheers
I have narrowed the problem down to the NAS Settings.
We use a NIS Server in our environment, so I activated the NIS option in Authentication method.
As soon as I change from NIS to internal LDAP the destination volume appears in the replication task window.
Any idea??
regards
Are there any VLANs or other security policies in place, very hard to see why changing an Authentication method allows the volumes to be online. Now if the volume in the replication feature was not set correctly and the origanal was not set to destination then ok but for an Authentication method might lean to an outside issue.
No VLANs. The 2 boxes share the same subnet. I have already tried disabling the bonding but without sucess.
What impact has changing the authentication method?
Is this only for user authentication or resolving hostnames as well?
Lets start over as if all users are using the NIS Authentication method to access the shares but the replication task was switched over.
Server A build 3518 (source for the NAS Logical Volume LV000x) using Authentication method NIS
Server B build 3518 (destination for the NAS Logical Volume LV000x) using Authentication other then NIS?
Server B was switched to be Source server and Server A was switched to Destination server.
Once this was done you were not able to see your shares?
When the replication is started only the source will be seen not the destination until it is switched over and roles are reversed.
I am willing to do a webex session to help but we will need to setup a time schedule. I am located in the EST time zone.
Thank you Todd for your offer.
With a hint from support I could find the problem.
I had some Users in our NIS with UID < 100 which were conflicting with the replication in some way.
As soon as I removed this users, the destination volume appeared in the replication task window.
Cheers
Matthias