(Come on, one of you guys must be able to help? – Suz.)
Hi
I will be upgrading one of our servers currently running 5.0.8.
It has 414gb of databases on it, and I would like to leave the ODS at 41 if possible, and then run fixup, compact and updall at the weekend to bring everything up to 43.
The time window for completing this task is short (4 hours), so in order to save time I need to know if I disable compaction in the NOTES.INI, will the server still attempt to upgrade everything, or even worse, retain ODS 41 and build extra indexes in all the dbs meaning we run out of disk space (maybe panicking a bit here, 172gb remains free on the drive).
If you don’t run Compact yourself, the server won’t do it automatically on you.
Typically, instead of running compact from the NOTES.INI I run mine from a program document. It makes it easier for me to schedule it, add options, etc.
Compact only processes one database at a time so unless you have a database that will take up more than 172GB by itself, space shouldn’t be an issue while you’re doing a copy-style compact.
I think 4 hours for running fixup, compact and updall on 414GB of data might be a little ambitious unless you’re running some scary fast hardware. It’s been over a year since I upgraded my servers from R5 to R6 but I’m pretty sure it took a couple hours to do that and my biggest server at the time was somewhere between 100-150GB. Hardware wasn’t anything special…Dell 2650’s.
Thanks for that Scott. My main concern is that users will get slow response upon first opening databases the morning after the upgrade, due to the recreation of indexes (as leaving the ODS at 41 causes the server to create 2 versions of every view index).
If nobody else here has flagged this as a problem, then I’ll stop worrying about it
