Specification Options - Propagate Shares

You are right.  I tried it in 6.2 and 6.4 and doesn't notice any difference regardless if the box is checked or not. \

Do you know what it is supposed to do?

Hi,

I tested it in RepliStor6.4SP2, but there is not a change.

This may be defect.

I will test.
If a defect is confirmed, I will create the case of this issue.

Hi,

Shares Function
Share is sent when checking it.

When the check is removed, share is not sent.

However, this function doesn't operate correctly.
I plan to open the support case with this issue.

Hi,

This function operated correctly.

It is my misunderstanding.

Reproduce

1) Create a share folder.

2) The share folder is copied to the target.

3) Disable the share in the source.

4) Share of the target disappears.

5) The option of Spec is changed.
Options Tab--Propagate--Shares disable

6) Enable the share in the source.

7) It synchronize.

8) Share is not copied to the target.

All,

The purpose of checking the Shares box in the Propagate dialog is to have RS send the Share information to the target node. This is especially useful when using it in conjunction with the Alias functionality. If use it with an Alias, then a user can connect to the
AliasName\ShareName
AliasName\ShareName> and it will not matter which machine is hosting the Share and NETBIOS name. RS will replicate the Share name and the permissions associated with that share to the Target node whenever the box is checked.

You may also check the Hidden Shares box. Checking the Hidden Shares box will propagate the share names that enc with a dollar sign ($). These are normally the Administrative Shares like C$, but you can also create share names for other purposes that do not show up in a browse of the network. For Example you might create a share named ITOnly$ and grant permission to only those login IDs who are a member of the IT group.

I've tested it without using Alias and the source and target are within one server, but it didn't replicate any share information.  I'll try again replicating between 2 servers and see if it works.  If it does, then definitely will be great because if the event of a failover to our target server, we won't need to manually share the directories in our specifications now.

You guys are right!  It does work if I replicate between two servers.  But doesn't work within one server, which makes sense because you can't have two shares with the same name within one server.

By the way, the next question i wanted to ask is, if I wanted to add a new server to be part of replication, I must install the same Replistor client, same version?  Or, I can replicate to a server without a Replistor client installed?

Hi,

Please teach the OS version that you use.
Is the environment WORKGROUP?

Hi,

Create UNC path in Option--NASAdmin Tab.

And create Specification.

Operate it according to an image.

It might be possible by this method.

Oh, interesting!  thanks for the tips. I'll give it a try tomorrow morning.  Do you know if there's any performance losses by not installing the replistor client on the target server?  

Hi,

When the NAS Admin function is used, the speed is reduced by half.

Two RepliStor used

NAS Admin used

Interesting, thanks for the research Mr. Ito!