New post

#Backup

6

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.

Documentation.

Hi, Community!

Check the second Developer Community Video of the week:

Backup and Restore for Federated Systems

https://www.youtube.com/embed/045ub0q3Bqc
[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]

1 0
0 361

Hi, Community!

Please welcome a new session recording from Global Summit 2017:

Backup Essentials - Protecting Your Data

https://www.youtube.com/embed/TBPWbW4pADE
[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]

2 0
0 300

Hi,

Is there a way you can limit the amount of physical memory Cache uses?

During Cache backup it appears that all the available memory on the server is being used.

We are running Ensemble 2016.1 on Windows Server 2008 R2 with 32GB of RAM.

The database we are backing up is about 300GB.

Thanks,

Graham

0 3
0 559
Question
· Dec 14, 2016
Intergity test for cbk files

Hi, Community!

We have our internal backup system which produces *.cbk files for Full, Incremental and Cumulative backup modes.

Does anyone have an automation procedure to restore this files on some target testing system, check the integrity and mark the files as "restorable"?

Please, share?

Thank you in advance!

0 2
0 438

We are finally planning to migrate some ancient Caché applications that are run on Caché 5.0.21 to a new server with Caché 2016.2.0 or so.

I wonder if we could use Shadowing between those to keep the data on the new server up to date?

We would copy the Caché backup from the old environment to the new and do a RESTORE there and then start shadowing.

I know than 5.0.21 is no more officially supported by ISC.

0 5
0 716

The goal of this writing was to illustrate how to restore backup before the patch would be applied. The alert notes that:

The risk can be avoided by applying journals from the beginning of the journal file that was switched to at the start of the backup, rather than accepting the default of starting from the journal marker position.

Having non-patched Caché 2015.1.4, I ran sample database backup and restore just to get where I should answer "No". Collecting journal info from the backup log:

5 0
0 385

InterSystems has corrected a defect that may result in missing updates when utilizing Caché online backup.

This defect is present in all Caché and Ensemble versions 2015.1.x, 2015.2.x and 2016.1.x, and all HealthShare distributions based on those versions. It affects all platforms and operating systems except backups of OpenVMS cluster databases.

2 0
0 367

C:\data\backup.bat :

C:\InterSystems\Ensemble\bin\cache -s"C:\InterSystems\Ensemble\Mgr" -U%%SYS ##Class(Backup.General).ExternalFreeze() <C:\data\login.scr

echo %ERRORLEVEL%

rem note that we need to check errorlevel from highest to lowest here....

if errorlevel 5 goto OK

2 0
0 1.9K