go to post Alexander Pettitt · May 2 Are all the instances IRIS and not Cache?Maybe try ccontrol list
go to post Alexander Pettitt · Apr 10 There is this Memory and Startup Settings. Are you trying to limit process or shared memory? One issue can be just the number of processes.
go to post Alexander Pettitt · Mar 11 I would try d ALL^%SS for CPU. d ALL^%SS is used in the ^pButtons report. Due to shared memory it is hard to assign memory to much past the instance of Cache or IRIS.
go to post Alexander Pettitt · Feb 24 One thing to be aware of is if you use messages.log to track IRIS.DAT growth the shrinking of IRISTEMP either through a delete or reset will throw off those numbers. @Timo.Lindenschmid's point is a good one. Setting a max size can be done from SMP or in %SYS with ^DATABASE but that likely means you will have issues sooner.MaxIRISTempSizeAtStart documentation.
go to post Alexander Pettitt · Jan 27 iris session [INSTANCE] -U %sys ALL^%SS would give you the PID,namespace, routine, CPU and globals.
go to post Alexander Pettitt · Jan 22 As noted in the documentation the ExternalFreeze() can not last longer then 10 minutes or however long it takes you to run out of global buffers. You could use irisstat :iris stat [INSTNACE] | grep WDSUSPD # this will show you if the write daemon are suspended.iris stat [INSTNACE] -W #this will resume them. As a guess you are running out of buffers and the options are to move the snapshot to a less busy time on the system and/or increase the number of global buffers.Look at using mgstat to find a better time to do the backup.
go to post Alexander Pettitt · Nov 29, 2024 Is it possible to define aliases per IRIS instance? Looking at Aliases mentions the .iris_init but that is user wide.
go to post Alexander Pettitt · Nov 20, 2024 Searching for ConvertDateTime works for me and gives 6 results.https://docs.intersystems.com/results.html?docs%5Bquery%5D=ConvertDateTime
go to post Alexander Pettitt · Nov 20, 2024 I think for 100% certain rollback a restore by @Ben Spead suggestion would be the way to go. While maybe if you were going back to IRIS 2024.1.1 you could just rename the install directory and install the old version I would not count on that working. I think things like journal files and IRIS.DAT get upgraded so you can not go back. You could have a mirror on the old and new version and move from the old to the new but you would still lose data since you can not mirror to a downlevel version - InterSystems IRIS Instance Compatibility I would go to the WRC and ask them. Contact the WRC
go to post Alexander Pettitt · Nov 11, 2024 Some thoughts:Install it outside the rootvg so not in /usr or /optDon't bury it deep in a path. Something like /[application]/[instance]/irissys for exampleData in a separate volume group to enable snapshots and the external freeze.Journals in a separate volume group to enable snapshots and the external freeze.Keep instance names unique unless it is a failover member or DR async Look at Storage Planning
go to post Alexander Pettitt · Oct 24, 2024 You could optimize this: If F1 > 0 and F2 > 0 F1 > F2 ; positive F1 < F2 ; negative no need do the subtraction.
go to post Alexander Pettitt · Sep 11, 2024 Sounds much the same as these threads: IRIS Mirror in the cloud (AWS) My opinion: IRIS Mirror not as reliable as expected in AWS Elastic Container Service
go to post Alexander Pettitt · Sep 11, 2024 For IP address transfer/takeover to work the network has to be the same. Other clustering solutions work like this. Planning a Mirror Virtual IP (VIP) If by fake you mean not the normal OS level clustering solution that is true. It is an app specific solution. If the cost of the 2x storage is an issue maybe a deduplicating SAN would reduce the cost at the added risk not having redundant storage.
go to post Alexander Pettitt · Sep 4, 2024 Have you tried using ^MIRROR? Remove Mirrored Databases from a Mirror
go to post Alexander Pettitt · Sep 3, 2024 If at the OS layer you used LVM and XFS you could just add a LUN to the volume group and grow the filesystems. This can be done with everything up.The backup solution for me determines what a large file is. For me that is anything over 1 terabyte. We use External Backups.Most backup solutions only have one process per file. This means fewer and larger IRIS.DATs will always be slower to backup and restore than more and smaller IRIS.DATs.The growth pattern needs to be understood. If it is going to just grow forever it has to be broken apart and it will be easier while it is small.In your place I would upgrade to the 2024 version and explore Multivolume Databases.8K IRIS.DATs have a max size of 32 Tb though Intersystems is working on this.
go to post Alexander Pettitt · Aug 5, 2024 If you do performance testing the storage is going to be allocated either anyway so might as well do it upfront.
go to post Alexander Pettitt · Jul 24, 2024 I am interested in InterSystems IRIS: What’s New, What’s Next and InterSystems Data Platforms Roadmap: Leading in the Data and AI-Driven Era.
go to post Alexander Pettitt · Jun 27, 2024 I don't see that in the documentation - final classmethod CatchupDB(DBList As %String, JournalLocation As %String = "", ByRef DBErrList As %String) as %Integer
go to post Alexander Pettitt · Jun 19, 2024 A low impact way to do this would be take a SAN snapshot of production and mount the snapshot in test. Intersystems discusses this in External Backup. The easy way to retain some database is mount them from a different set of disks/filesystem. If you have a DR mirror but not a SAN you could just shutdown the DR mirror and do a cold backup. If test is a separate mirror the whole test mirror will have to be refreshed due to mirror headers. If test is part of the same mirror as production then the data is already there.
