In information technology, a backup, or the process of backing up, refers to the copying and archiving of computer data so it may be used to restore the original after a data loss event.
In InterSystems Data Platform backup means procedures for backing up data in database files and all the related procedures which assure that no any application data is being lost during backup and recovery.
I am looking for experience of people running Veeam with Caché databases.
Tips/Tricks/General questions like; what Veeam features are you using, what your backup cycle looks like, where does your data end up, what recovery/integrity checks you do, what sort of compression/dedupe you get.
Also what questions _you_ have and what problems you might be trying to solve.
Working in support, I usually get asked how many days I should keep journals. Should it be two days or after two backups? More? Less? Why two?
The correct answer (for most of the environments) is that you should keep the journals since the last validated Backup. I.e., until you don't check if a Backup is valid (restoring the file and checking with the Integrity utility), you can't be sure there is a good copy of your data and can't purge the journals safely.
I hope you can help me because this is a very serious that I can't wait to resolve... Our back-up is currently taking 3 up to 4 Gb per day and we don't know why. We had 270 Gb yesterday and we are today at 274.3 Gb. We keep a computer history of the messages for only 50 days. Here is a picture of what's currently taking the most data place in our healtshare system:
(don't forget that our DB is also connected to the back-up, maybe it is related, I don't know)
https://www.youtube.com/embed/5mCQ5q9bdAE [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
I have been revisiting our backup strategy, and spotted that IRIS supports VSS (Volume Shadow Copy Service) in Windows. This is quite attractive as an approach, as it automatically calls the external freeze and thaw commands.
However when calling these manually, there's quite a few parameters that can be set, and the documentation around VSS only states that the freeze/thaw commands are called.
Is there a way of controlling the parameters used, or at the very least know what the defaults are?
Currently running on limited hardware, Online Backups are becoming a bottleneck for our system.
For now, we are exploring an option to backup individual databases, or groups of them, thus reducing RAM requirements per individual backup task. To do that, however, we'd need a separate Backup List for our Backup Tasks. We did not find an option to do so in web portal, so currently we are looking at inheriting from system backup tasks and Backup.General classes to generate Backup List before backing up and then performing the backup as normal.
Despite the fact that InterSystems has long recommended using external backup tools, many users have opted to use the internal Online Backup facility, which is included in all distributions of InterSystems products (IRIS Data Platform, Caché, etc.). The reasons why are quite obvious:
Database systems have very specific backup requirements that in enterprise deployments require forethought and planning. For database systems, the operational goal of a backup solution is to create a copy of the data in a state that is equivalent to when application is shut down gracefully. Application consistent backups meet these requirements and Caché provides a set of APIs that facilitate the integration with external solutions to achieve this level of backup consistency.
My project need to restore the previous part of the log, and I use the rountine "^JRNRESTO" and filter. After recovery completed, the table structure is restored, but the table data is not restored， also unable to insert data into the table.
We are currently implementing the Data Innovations Instrument Manager product. In setting up our backup process we are wanting to use Veam snapshots. The application runs in a Caché 2016.1/Windows Server 2016 instance. We are running an HA primary/secondary/arbiter config. The statement below is from DI. I am curious to see what others that have implemented the DI Instrument Manager in the same or similar config have in place for backup.
"DI recommends is recommending that we not perform snapshots, but if you do choose to do so, here is some important information to consider.
Greetings community. I would like to know how to migrate a BD in production to a local environment. When I have a system in production (BD Sql Server) what we do is mount a local copy to do the analysis with the data and not occupy resources of the system in production. My question is: How do you do it with Intersystems technology?
For I=1:1:200 Set ^ABC(I)="" For I=1:1:200 Set ^XYZ(I)="" For I=1:1:100 Kill ^ABC(I)
2. create ZJRNFILT
ZJRNFILT(jid,dir,glo,type,restmode,addr,time) /*Filter*/ Set restmode=1 /*Return 1 for restore*/ If glo["^ABC",type="K" Set restmode=0 /*except if a kill on ^ABC*/ Quit ;
I am new to InsterSystems Cache - having a SQL Server background. However I am dealing with a Third Party who use InterSystems Cache to hold some of our data. To do some analysis I need to view a backup of the database. They are prepared to send me a backup.
My question is - how can I view this backup ( would this be the CACHE.dat file?).
Do I effectively need to have an installation of CACHE on my machine to be able to view this? Is it possible to view it from SQL Server?
We are currently using Ensemble on AIX. We are on 2015.2.2. If I install Field Test on a windows desktop, is it possible that I can import the Cache.dat from my AIX server, so I can do some Proof of Concept development?
This article was written as an attempt to share the experience of installing the InterSystems Caché DBMS for production environment.
We all know that the development configuration of a DBMS is very different from real-life conditions.
As a rule, development is carried out in “hothouse conditions” with a bare minimum of security measures, but when we publish our project online, we must ensure its reliable and uninterrupted operation in a very aggressive environment.
Let's say you have about 100TB of data in multiple CACHE.DAT. The biggest one is about 30TB but mostly more than 1TB. You have limited time for maintenance during a day, and it is only a few hours at night. You have to check Integrity as much often as possible. And of course backup it.
I asked previously about the DR server in the cloud but actually, I'm curious about the backup server to use as analytics server more than for recovery in DR case.
There is a recommended practice to use an async mirror as a server for BI (InterSystems Analytics, DeepSee)
The question is if I have PRIMARY in the cloud (AWS, Google, Azure, etc) "how far" should async mirror member be placed? Same cloud, same private cloud or it doesn't matter at all for analytics purposes?
We are trying to migrate all our production to new IRIS servers. To test everything is working fine, and to be able to script the process, we want to import the data into new IRIS servers using a backup file (created with ^BACKUP). But we've found that IRIS doesn't recognize Ensemble backups so we can't import it using ^DBREST :-O
Any of you know how to import in IRIS an Ensemble backup file?
I was understanding the cluster configuration supported by the Cache. Have couple of queries around that:
1. In Cache version 2018.2, there is a shrading concept which splits the data of a Master Data server into multiple small data server which store shraded data.
By update
Open Exchange app
I was understanding the cluster configuration supported by the Cache. Have couple of queries around that:
1. In Cache version 2018.2, there is a shrading concept which splits the data of a Master Data server into multiple small data server which store shraded data.