go to post Alexander Pettitt · Sep 11 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 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 Have you tried using ^MIRROR? Remove Mirrored Databases from a Mirror
go to post Alexander Pettitt · Sep 3 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 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 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 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 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.
go to post Alexander Pettitt · Jun 4 In two really key ways multi-volumes datasets don't allow you to escape limits you might want to escape.The max size of a multi-volume dataset is the same as a single file - 34 TB (33553904 MB) for 8K database. Intersystems is working to increase the max size.An integrity check also treats it as if it was a single file. This is only going to be more of an issue as the max size increses.
go to post Alexander Pettitt · May 2 1.9Tb will be days assuming ssd storage and slower if not.I would test a small amount during a low period.
go to post Alexander Pettitt · May 2 Truncate can only remove free space from the end of the file.Compact is asking how much free space do you want at the end of the file.The free space is likely not evenly distributed.I mostly used the ^DATABASE utility.
go to post Alexander Pettitt · May 2 Since you are on Cache still make sure it is ok to compact/truncate with your version.Run an integrity check after to validate the DAT.Expect large wij growth.Do @Enrico Parisi's suggestion of a small amount first during a low utilization time.Mirror and shadow targets have to be done separately.
go to post Alexander Pettitt · Apr 29 It looks like you are missing the kill to cleanup. kill ^IRIS.TempIntegrityOutput(+$job) Something to know is you can pass a routine to IRIS but not a set. Look at the iris terminal options here.
go to post Alexander Pettitt · Apr 24 As a guess the shell is interpreting $job rather than passing it to IRIS. try this echo 'set sc=$$CheckList^Integrity(,,,,5) do Display^Integrity() kill ^IRIS.TempIntegrityOutput(+$job)' | iris session [INSTANCE] -U %sys one issue with this approach is you need to get the same IRIS session that the integrity check ran in.
go to post Alexander Pettitt · Mar 18 An instance name is not guarantied to be unique.hostname/ip + instance is.For example the instance name of our failover primary and backup is the same they are just on different hosts.We use DNS name not IP addresses though so we have DNS/instance for SystemName. Mirroring Configurations within a Single Data Center, Computer Room, or Campus
go to post Alexander Pettitt · Mar 15 I would ask your vendor what they develop on so you don't have to listen to an excuse around a support issue.
go to post Alexander Pettitt · Mar 10 I would check that your iris.key file exists and has not expired. Not sure where messages.log is on Windows but I would look at that over a Windows log.
go to post Alexander Pettitt · Mar 4 Guessing the upgrade did iris start [instance] nostu to not run any user code on startup.iris help start **** iris usage ****Syntax: iris start <instance name> [parameters]Description: Run the instance's irisstart procedure to bring InterSystems IRIS up.Optional parameters: quietly -> non-interactive, with minimal dialog nostu -> don't run startup routine (^STU) help -> list supported parameters EmergencyId=username,password -> start up in emergency mode Any other value is taken as a configuration file name with '.cpf' appended. If a configuration file is not specified, the file 'iris.cpf' is used.Example: iris start mystuff quietly <- uses file 'mystuff.cpf'Notes: Some instances might not have support for a particular parameter, or a new parameter could have been added. For a list of supported parameters for a specific instance, type: iris start <instance name> help
