Can you compact and truncate only on shadow server 2022.1 (Build 209U)

Question

Question

Mark OReilly · Feb 16, 2023

#Databases #InterSystems IRIS for Health

Hi we have started to get rid of orphaned data and would like to soon compact and truncate the database as will have about 40gb free to return to filesystem after the few weeks of running the new task.

The idea would be to do this on the shadow server first of mirror rather than primary.

Is there any reason this is a bad idea? Considering this needs done on both servers of mirrored db? As idea would be to do this on shadow server before we failover to the server a few days afterwards. And do the same for the month afterwards.

Also note we have tested our compact and truncate against a non production environment that has been a restore of the live backup db to be able to test this before we do this truncating.

Product version: IRIS 2022.1

Discussion (3)1

Log in or sign up to continue

Dmitry Maslennikov · Feb 16, 2023

I've done a similar task, with much bigger databases. And it was quite good. Mirroring working with data itself, not the on the block level. So, there should not be an issue, if you do not change data stored there.

2 0

score 0 · Answer 1 · 2023-02-16T10:10:07-05:00

Thank you, it is a 700gb database, good to know this is ok thought this would be the case so will go with this strategy of truncating

score 0 · Answer 2 · 2023-02-20T01:01:38-05:00

Hi Mark,

there is no issue doing this on a Primary mirror. I have done this multiple times for customers. The system impact with IRIS is negligible. Just remember to do this on all mirror members as DB activities are not replicated only data is.

Just to be on the save side though always check a valid backup is available before you start.