nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Highly available Portal - Standby Server DB issues

rajeshc

Hi,

We have a Highly available setup of Portal for ArcGIS 10.6.1 with one Primary and one Standby server each. The OS is Wiondows Server 2016. We are running into Disk space issues on the standby server due to numerous DB folders being created automatically under the portal installation path C:\arcgisportal. Sometimes every 2-3 minutes, a new db folder is created. This issue is appearing only on the standby server. Is this behavior normal for the product?

Thanks,

Rajesh C

PortalHA_issue.png

PortalLog.xlsx

タグ付けされた投稿をもっと見る

Accepted answers

JonathanQuinn

The promote.dat file is the trigger file used to tell the software to promote the database to primary. This shouldn't be in the db directory on the primary and is likely the reason for the behavior you're seeing. Delete the promote.dat file and see if that improves things.

All comments

JonathanQuinn

Yes, you can delete the dbXXXX folders.

rajeshc

By deleting the promote.dat file from the Primary Server's db directory seems to solve the issue so far. Now is it safe to delete those unwanted dbxxxxx folders ?

Thanks

rajeshc

We have deleted the promote.dat file from the db directory on the primary server. I will update on the effect later.

It is neither present on the secondary. Curious to know how the promotion will work if this file is not present..

Thanks

JonathanQuinn

rajeshc

Hi Jonathan,

Our setup was a fresh installation and new site, there was no site import operation.

The primary db directory contains a promote.dat file with zero bytes.

I have added the portal log to the main post as an excel file.

Thanks for the reply.

JonathanQuinn

No, that's not expected behavior. The only time a dbXXXX folder will be created is when the standby comes back from a failure or when you run importSite on Portal. During normal operation, it shouldn't create those folders.

It seems like it is continually thinking the standby is coming back from a failure. Can you set the logs to at least Verbose and then post the logs? Feel free to scrub the machine names out of them. Do you see a promote.dat file within the db directory on primary?

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.