Unsolved
This post is more than 5 years old
1 Message
0
1874
November 9th, 2011 14:00
Upgrading Replistor from 6.3.1.3 to 6.4 SP2 HF5
Can Replistor 6.3 be upgraded to 6.4 using the same license i.e. without a charge?
No Events found!
Unsolved
This post is more than 5 years old
1 Message
0
1874
November 9th, 2011 14:00
Can Replistor 6.3 be upgraded to 6.4 using the same license i.e. without a charge?
Top
yito1
262 Posts
0
November 9th, 2011 16:00
Hi,
I'm sorry.
I forgot to write the procedure.
How to change the registry value.
a) Please stop the service.
- RepliStor Server Service
- RepliStor Control Service
b) Change Registory value
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ RepliStorControl \ Parameters:
DirEntrySplitLimit
100000 (decimal) ---> 1000 (decimal)
c) Please start the service
- RepliStor Server Service
- RepliStor Control Service
yito1
262 Posts
0
November 9th, 2011 16:00
Hi,
Yes, it is possible.
However, the following caveats.
1) Change the registry value
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ RepliStorControl \ Parameters:
DirEntrySplitLimit
100000 (decimal) ---> 1000 (decimal)
2) Change DiskSpace Monitor value
Warning Size 500 ---> 2000
Stop Size 100 ---> 1000
Interval Size 50 ---> 100
jschrade1
106 Posts
0
November 10th, 2011 05:00
jimtsmith ,
As mentioned by Ito, the upgrade from 6.3.x to 6.4.x does not require a change of license. The changes that Ito recommended are not related to licensing but are recommended because of some changes between version 6.3 and 6.4. For example, the change in size of the Kernel logs from 1 MB to 100MB can cause the early warning of free space to be too late to prevent OS issue. Hence the recommendation to change the Warning Size from 500 to 2000. This means that RS will post a Warning when the free space on the Data Directory drive reaches 2000. That gives you more time to react to a low free space condition before RS stops mirroring and forwarding. The change to the Stop size is when RS stops mirroring and forwarding to prevent the OS from running out of disk space on the system disk since that can cause a bluescreen if the Data Directory is located on the system (C:\) drive.
The other change of the DirEntrySplitLimit is to prevent the size of the list of files to be sync’ed from over-running a buffer size. Changing the size prevents this by splitting it at a smaller size. This is really dependent on what you are replicating. If you replicate a smaller number of large files it may not be necessary to change it but if you have a large number of small files it can prevent issues. In my opinion it will not hurt to make the change as it will not hurt anything if you have a smaller number of files in the list.
Thanks for using the RepliStor Forum.
1 Attachment
image001.jpg
yito1
262 Posts
0
November 10th, 2011 06:00
Hi, jschrade
>For example, the change in size of the Kernel logs from 1 MB to 100MB can cause the early warning of free space to be too late to prevent OS issue.
This size has changed from Ver 6.2.
Ver 6.3 is the default 100MB.