kalariviswa
New Member.
427 views

Adding disk space process to existing ED replica server

Hi ,

I have a existing ED tree. Where we have a 1 master and some replicas in it. The eDirectory - DIB is under /var partition. Since the size of the partition is less. We are planning to increase the same on the replica servers.

I would to clarify on the best practice for doing this. .

1. After stopping ED on the replica server, can I directly request the Server team to increase the size of the /var partition without removing the server from Replica ring. (or)

2. After stopping the ED, is it good to - remove the server from Replica ring and then increase the partition space and then add the server back to ring, and start the ED and allow the DIB to sync with master.

Thanks in advance.
Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: Adding disk space process to existing ED replica server

On 07/11/2018 10:54 AM, kalariviswa wrote:
>
> I have a existing ED tree. Where we have a 1 master and some replicas in
> it. The eDirectory - DIB is under /var partition. Since the size of the
> partition is less. We are planning to increase the same on the replica
> servers.
>
> I would to clarify on the best practice for doing this. .


Best practice would be to have a filesystem dedicated to the DIB. Even if
you make it bigger, the system's logs, core files, etc. can eventually
cause the filesytsem to fill, then impacting eDirectory negatively and
needlessly.

> 1. After stopping ED on the replica server, can I directly request the
> Server team to increase the size of the /var partition without removing
> the server from Replica ring. (or)


Yes, exactly that. Removing the server form the replica ring, or doing
anything else, would be pointless.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.