As Alexander said, I would not recommend deleting journals from the OS. Worst case you make mirror syncing or transactions fail, or less bad but annoying you can orphan journals from the instance's record.

Journals are an important part of backup recovery as well (though a mirror covers some of that recovery role). How many days of journals are you keeping such that you fill your disk?

What kind of processes? Most user processes will need to be restarted on the other member. The mirror has some mechanisms to allow for, for example, productions to start automatically on failover, but for any given random process you probably need to handle that manually. You can use ZMIRROR.

https://docs.intersystems.com/iris20221/csp/docbook/DocBook.UI.Page.cls?KEY=GHA_mirror_set_config#GHA_mirror_set_tunable_params_zmirror_routine

Hi Paul,

This depends on the details of how your web server and gateway were set up. Are you unable to log in to the gateway management page? That would normally tell you where the gateway is installed (and thus where the event log and so on are).

Do you have a /webgateway folder under /opt?

https://docs.intersystems.com/iris20221/csp/docbook/DocBook.UI.Page.cls?KEY=GCGI_altApUnix

Hi Roger,

The latest InterSystems product is IRIS, but in the Caché documentation you can find various chapters on converting from MSM > Caché.

https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GMSM

I'd suggest reaching out to the InterSystems sales department as they may be able to assist you or point you in a direction for moving off MSM onto something more modern.

https://www.intersystems.com/contact-us

John should be on the right track here, but to elaborate here are the relevant docs:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GHA_mirror_set_config#GHA_mirror_set_configecp

A mirrored ECP connection will try to connect to the primary, but your message is telling you that you don't have an active primary mirror member. You should investigate the mirror status / messages.log.

Hello Ephraim,

This seems like a better question for InterSystems Support / WRC who can look at the full log and system to try and determine what's happening.

From a file system disk space perspective, the database is almost filling the disk, but there is free space WITHIN the database from the IRIS perspective.

Regarding the performance side of things, what did you check such that it looks fine? CPU / memory / disk? When did the warnings start and are they ongoing? What's being done on the system, anything abnormal?

Hello Mark,

That's a HealthShare Information Exchange / Unified Care Record specific task. The "standard" mirroring docs don't cover it for that reason. As you gleaned from its code, it makes sure the HealthShare mirror agent is running. To be honest, I don't know all the details of what that agent does.

I'd suggest reaching out to the WRC to investigate what happened to cause the task to fail, and they can probably give more details on what the task does. While you're at it, you could also ask why it isn't documented, and poke on why it's listed as a user type task - though I see that many of the HealthShare-specific tasks are "user"-typed, so perhaps that is intended.