Hello all.
I'm still struggling with this dang upgrade issue.
To run APPBACKUP successfully, do all indexes (or just relational indexes) need to be turned off first? I cannot get APPBACK to successfully backup my in-development 3.4 application so that I might upgrade to 3.7.2 (and ever upwards).
Every time I try to run APPBACKUP I get an FS100 msg on every one of my files (they all have indexing).
Please, can someone give me a clue?
Thx,
Fr. Mike
Mike,
In one of year earlier posts it seemed that you had your data tables stored in Datavol. Is this correct?
I would strongly advise that the data for that application be segregated into one or more vols (subdirectories). Thus you will not have to appbackup the application data when transfering from one system to another. This then makes deployment much simpler.
Richard Bright
Richard,
Thanks for the reply. So are you saying that I should not use DATAVOL or allow the dicts and whatnot to be in DATAVOL but the actual database records be in some other volume entirely? Is this similar to the ARev thing where it was better to have my entire app in a completely segregated subdirectory apart from the DATAVOL or REVBOOT branches??
If so, that I understand. My next question then becomes, if I have my app in a discreet, segregated subdirectory, install the lastest and greatest OI version, move my app subdirectory tree (or merely "map" to it in OI), how does the app itself become upgraded to the higher version if we're bypassing APPBACKUP (which is what I'm assuming you're implying)?
Thanks,
Mike
Mike,
Richard told you to move the data tables. You must still APPBACKUP the app.
Hope you succeed. I don't think I can be of much help. I've only used APPBACKUP a couple of times, and the last time was many years ago. I've read your posts, and checked my notes to see if I could find anything of relevance to your case. But I came up with nothing.
- Oystein -
I confirm that you segregate your data into separate volume(s). This enables you to have portability with the data.
Unlike AREV you cannot segregate the forms, stored proceedures, reports etc in the same way; that is they are stored in the repository - and are in the revboot vol. That is where Appbackup comes to play. Appbackup simply extracts all your bits and pieces from the application - en mass - and dumps it into a global account in a way that it can then deploy back into a repository in an Appbackup restore. Please note that this is not intended to replace the RDK modules - but does something similar in a bulk way.
So your proceedure to transfer MyApp application from one OI System to another would be to run Appbackup to extract your application forms, routines etc. Copy mydata vol to new location plus mybackup being the appbackup vol. Create MyApp in the new system. Restore the application in the new system via appbackup and establish entry point for the application. You MAY need to re-establish the database quick-attach image ie in Database Manager go File | Add (select vol\tables) and Database | Save. Check on this before re-establishing.
Please note that it is very rare that you will need to worry about 'updating' the application components due to a version update.
The only issues that you may need to think about is where you have special external dlls declared or where the application you are restoring inherits components from a higher order application eg you may have constructed the system with a TOOLS application below SYSPROG, and you have positioned MYAPP to inherit from TOOLS.
Richard Bright
BrightIdeas New Zealand
r.bright@ark.co.nz
Hello Oystein and everyone,
Here's the latest:
I did a fresh install of 3.7.2, to which I applied the .3 and .4 upgrades, then installed OIPI. I did all of this on my local drive.
Since I began my development in 3.4 and was relatively unhappy with several of the paths I had chosen, I figured I might as well start from scratch in 3.7.4. This is fine, since 3.4 was acting a little funny and I could never seem to get APPBACKUP to like my app. I hadn't taken into account the practice of completely isolating a dedicated app from DATAVOL, so I took that into consideration on the redesign. Perhaps now everything will work right (he said quasi-confidently).
So here I am, rebuilding all of my DICTs and using a little bit more common sense this time. Nothing will be lost, I hope, as I will make the adjustments in the DICTs that I was thinking I should have done from the start and will simply IMPORT/EXPORT myself silly moving the data from the wretched little system to this newer install.
One question, however, does remain with regard to APPBACKUP: Do indexes need to be turned off before running this? I only seek to clarify this because of the repeated failures and FS100 msgs on all of the !filename tables.
Thanks to all of you for your patience with me. I seem to be not only rusty but complety and thoroughly oxidized!
Fr. Mike
Mike-
Appbackup, with Data Tables, will copy all indexes EXCEPT for relationals.
Hope it helps-
Mike Ruane