R
RichardWalsh
Guest
Prior to using Rollbase my experience is with the Progress Openedge database for back-office systems usually hosted on a server. In order to take backup we used (or use) a variety of methods. Sometimes we use probkup to take an online backup of the database. Sometimes we close the Openedge server and copy the physical database files. Sometimes we copy all the programs. Sometimes we do a complete dump of the database to ascii files (dotd files) and also the database definitions as an ascii file (database.df). Using a mixture of these methods we are pretty sure that whatever happens to the client server we will be able somehow to recover. The situation seems much less clear with the hosted rollbase cloud. If we generate the application XML (which we do) this seems to be the equivalent of the database.df i.e. the database structure but without the data. We have also defined reports for all (well most) tables which we export via batch jobs and emails on a periodic basis. This we take to be the equivalent of an Openedge'database dump' (dotds) in ASCII format. If there was some kind of disaster in the cloud do I have enough to allow me (or Rollbase Support) to build a new 'cloud instance' ? If not what should I be doing. I think it would be very useful to be able to define a procedure which backed up absolutely everything you need, frozen at a point in time, saved in a single downloadable file. Thanks, Richard
Continue reading...
Continue reading...