Hi,

Please execute the following command.

rep_srv cmd specexport c：\spec
rep_srv cmd specimport c：\spec

rep_srv cmd configexport c：\config
rep_srv cmd configimport c：\config

Please read the administrator's guide.

cheers.

got the admin guide infront of me.

nothing in the contents that says anything about migrating config to new OS

another question if i may.

will there be any issue with the rep_srv export/import since i'm upgrading from 32bit to 64bit OS?

Hi,

There is no issue.

hello,

it's been a while since i posted this but we've finally got around to performing the change to rebuild the server but the only problem we've encountered is that they wanted the server renamed.

so since then we've had to put a C name record in DNS for the old name to point to the new one and i can see the remote sites have attached themselves back to replistor server but now when i attempt to run a sync they just hang.

not sure if this is related to the sites pointing to the old name but being connected to the new replistor server or an underlying issue.

would it be simpler to maybe dettach the sites and re-attach to the new server so they're connecting with the correct name instead of still referencing the old name.  ie aunr-rstor-01 is the old server and the new one is audc-rstor-01 which is in preparation to move it to another phsyical site.

i assume it's the target site as all the sites sync there data to this server and it also has "Source Sites" then all the remote sites are listed under it.

I've since rebooted the server and performed a data directory clean and it seems to be working now.

strange, thanks anyway

Hi,

Are you the target server has been upgraded to Windows2008?

Or,　Source and Target?

Hi,

You check again. I'm not familiar with your environment.

Did you such a name change?

auad-net-01(Source) ---> aunr-rstor-01(Target)

                                       Change Name

                                                |

                                               V

auad-net-01(Source) ---> audc-rstor-01(Target)

In this case, please change your site in the Target Tab of the Specification.

Tripoint Operations,

Are you doing any Alias Failover operations? I do not see any Alias in the enclosed screen captures but I may have missed something. As far as changing the name of the server it should “generally” make no difference to RepliStor. However there are a couple of things that you should check and confirm.

· When you installed RepliStor did you have the installer add a record into the Active Directory?

· Did you remove the old Active Directory record before installing RepliStor on the renamed server?

· Do you have the Site information manually configured to a specific IP Address?

· How do the client nodes connect to the old name versus the new name?

· Does the new server host an application like SQL Server, that users connect to using the old server name?

There are enough questions above and some that I did not list for me to recommend you open a Support case with EMC to make sure we understand the entire configuration.

In general, just changing the name of the server should pose no problems to RepliStor. However, if the old name is still in the Active Directory it should be removed using Adsiedit.msc or AD Users and Computers. If the old and new name exist for the same IP address that “might” cause some confusion. Also, if you have edited the Site List IP address entry for the old/new RepliStor site it could also cause some confusion. Finally if there is an Alias configured, which I did not see listed, that may cause DNS confusion.

The main issue is whether all the clients attaching to the old server name, using a Windows Share name, for example, would need to change the share name from
OldServerName\ShareName
OldServerName\ShareName> to
NewServerName\ShareName
NewServerName\ShareName>. It appears you may have solved this by adding a CNAME record in the DNS server. While that is not a bad solution for a short term workaround, I would recommend that the users map directly to the new server’s name and share name. The reason is that over time you may end up with some using the old name and some with the new name. If for some reason the CNAME record was removed, some users would lose connectivity. You could possibly use an Alias to get around this as well but that is also not a great solution. You could also permanently add a name to the new server so that it would always answer to both the new and old name. That would require a registry entry and a reboot.

All of the above workarounds have advantages and disadvantages. For example if you are also running SQL Server or some other application to which client nodes connect, that must also be considered.

The bottom line is without more specific information it is difficult to propose a solid, permanent recommendation. For that reason, I recommend you open a Support case with EMC. Once the entire environment is understood, a recommendation can be made.

One more thing should be considered. RepliStor is now considered End of Service Life (EOL/EOSL). It is still supported until the end of the 1st quarter of 2013 but after that it will no longer be supported. For that reason, we are notifying customers to begin planning a new long term strategy. EMC does not have a direct replacement for RepliStor. The current recommendation is EMC RecoverPoint, which is an IP based external hardware solution. There are other host based products offered by non-EMC companies.

Thanks…JS

Hello,

As we don't have shares for each site we actually have a SAN presented disk for each site so we just un-attached the disk.  Performed the rep_srv export of the spec/config.  Blew away the Replistor server.  Rebuilt it from Windows 2003 to Windows 2008 R2.  Presented the SAN disk back.  Installed same version of Replistor (6.3 SP2 - the latest i think).  Then ran the rep_srv import of the spec/config.

The reason it works at the moment is because of the CName record that points the old name to the new name as we are usign the same IP address.

What i want to do now is change the target for all the sites to point to the new name.  As all sites still have the old name as their target but they're actually connecting to the new server via the CNAME record.

Should i just log a call with EMC since we have support

sorry i got my version wrong.. we are using 6.4.2.9 which is the latest

thanks for the help i will just log a support call

Hi, JS

The PowerLink does not exist 6.4SP2HF6.

Please upload.

I would recommend that and I would also recommend you update to the latest version of RepliStor. The current version is 6.4.SP2.HF6. The main reason is that 6.3.x does not fully support Reparse Points (Hard Links) which are commonly used in Windows 7, 2008 and 2008,R2. If you are running 6.3.x it is a simple upgrade. You can download the install components from Powerlink.

Although the upgrade is simple I would still recommend you open a Service Request. The Support Engineer can Webex into your server(s) and make sure we understand the overall configuration. Changing the Specifications should be pretty simple but I would certainly recommend someone just cross checks the change to the Specifications.

Thanks…JS

Great…JS

You can find the files at the following ftp site. As you know the files are purged after a couple of days and they are hidden so you need to paste this link into Explorer.

ftp://ftp.emc.com/outgoing/replistor/rep.6.4.SP2.HF6.exe

ftp://ftp.emc.com/outgoing/replistor/rep.6.4.SP2.HF6_x64.exe

JS