This post is more than 5 years old
4 Posts
0
862
September 10th, 2009 22:00
Source and Destination are NAS
HI all,
We are testing replistor 6.3, on 2 hosts hosting
OS Windows 2003 Storage Server R2 Std Edition
OS Win server 2003 R2 STD.
the source and destination are both a NAS share, ie UNC path
Is it supported???
We are testing replistor 6.3, on 2 hosts hosting
OS Windows 2003 Storage Server R2 Std Edition
OS Win server 2003 R2 STD.
the source and destination are both a NAS share, ie UNC path
Is it supported???
0 events found
No Events found!
jschrade1
2 Intern
•
106 Posts
0
September 18th, 2009 07:00
In general, if you register the UNC Path (Maintenance > Options > NAS Admin) make sure you have used the UserID and Password which had full permissions to the NAS Device in the dialog box for that UNC path. That needs to be done on both the Source and Target nodes of RepliStor.
Best practice is to Sync the files between two Windows Servers (Source and Target). You can then register the UNC path on the Source machine to the NAS device on the same LAN segment as the NAS server. Then on the Target you register the other NAS server's UNC path. That way you are replicating between two RepliStor nodes.
As mentioned, most NAS storage devices use a SAMBA 3.x protocol which presents itself as an NTFS CIFS Share on the network. However, since it is not "fully" NTFS compatible, you will actually have Linux type permissions. These are not as detailed as an Active Directory CIFS Share which can have very specific permissions assigned to the share as well as each file and folder. Since RepliStor normally looks up the NTFS Permissions from the AD controller and then replicates these same privileges to the Target node, the attempt to assign advanced permissions on the Target NAS device will fail.
If you use Explorer to look at the actual permissions of the individual files, you should see Linux type permissions. Therefore, you need to use the None option in the specifications. Doing that will apply make the NAS device to apply the permissions that it is configured to use.
Another thing to consider is that VSS snapshots cannot be performed on a UNC path connection. Also, in most cases, Mirroring of file changes is not supported. Therefore scheduled syncs are required to keep the files the same between the Source and Target paths. That is because RepliStor cannot control the access to the files directly. The NAS storage device will allow anyone access to the files and RepliStor cannot prevent that access. Therefore, a user can modify a file without RepliStor knowing about it. This can result in loss of file updates unless the user only accesses the files from one machine's share only and frequent syncs are performed.
Even with the restrictions of using this configuration, it can be a good DR alternative for some environments.
I would also recommend you upgrade to RepliStor 6.4 since there have been some significant enhancements in how RepliStor works with UNC path connections on the Source and Target nodes.
yito1
262 Posts
1
September 17th, 2009 19:00
It is possible.
JoshiParag
4 Posts
0
September 17th, 2009 21:00
There is another complex problem .
The NAS is Linksys NMH300, which is a basically home media storage box, It has only workgroup properties, it cannot be configured in a domain,
So How can we configure the source as a NAS which is having workgroup properties?
When we tested it the files were blocked , giving Acess Denied error.
yito1
262 Posts
1
September 17th, 2009 21:00
Will not the OS of this NAS be Linux?
And, I think the shared folder by Samba to be being offered.
Please try the following.
Specification---Option---Propagate---permissions as ----> None
OOPS
Specification---Option---Propagate---Attributes --->exclude a check
Specification---Option---Propagate---Shares --->exclude a check
Message was edited by:
Yoshinobu Ito
JoshiParag
4 Posts
0
September 18th, 2009 21:00
I will be trying to implement this on Monday.
Will keep u informed
Thanks
JoshiParag
4 Posts
0
September 25th, 2009 23:00
Due to some reasons we are not going ahead with the NAS
No the setup is
Two branches(Suppose A and B) having server each hosting replistor,
Both are distant, and are connected by leased line,
Both have different Domains,
the data is same on both servers, now we have to Synchronise and demonstrate failover between them.
IS failover across different domains possible????
What are the procedures ??? or where can i get the guide for them????
jschrade1
2 Intern
•
106 Posts
0
September 29th, 2009 13:00
RepliStor could be used to create an Alias and users could connect to that based on which machine is hosting the Alias. As far as them being in different Domains and/or locations that is more problematic but possible.
When setting up the Sites list you will need to use the credentials that are specific to the Domain. Then you need to use a CNAME record instead of an A record in the Alias because the two sites will most likely be in different sub-nets. Finally the DNS updates need to be replicated between all the different DNS controllers. That can take 15-30 minutes in most cases. These updates can be forced for the DNS controllers as well as the client nodes.
If you can be more specific on what you are trying to do I can maybe help further. Also remember that any firewalls need to pass through ports 7144 & 7145 for both TCP and UDP.