Quote:
Originally Posted by
shockneck
Ouch.... does that mean, that you don't have any backup of your server at all? Isn't there any other server that could export a filesystem to your server to write an mksysb onto?
Yes, I know. It is painful trying to manage this system in its current state. The only backup is tarballs of the application data that are ftp'd to another site. There is no backup of the operating system or the application binaries.
I know that I can create a mksysb backup on an NFS filesystem, but I thought that you had to have a NIM server to restore from this type of backup. Is that not correct?
Quote:
Originally Posted by
shockneck
Ouch again. Don't get me wrong - I am a big fan of the "never change a running system" idea but running 5.2 ML1 has disadvantages for reasons of security and (probably more interesting in your case) in virtual memory handling. With ML1 you don't have the option to let LRUD sort out how to divide the RAM between program cache and data cache.
I would love to upgrade this system, but I will not do so until I get a good mksysb. See previous question.
Thanks for the suggestions regarding SLAs and IOPs. I will see what information of this type I can gather and present to the higher-ups.
I don't think this system uses a "real" database. I believe the cobol programs merely read and write data files.
I will check with the software vendor and see if their application supports AIO.
Yes, most of the filesystems are still using JFS, not JFS2. I would love to create new filesystems and "migratepv" their applications to the new pv's, but I don't have any space to do so right now.
This system is hurting. I am just trying to make a convincing argument to fix it the "right" way, and all of your suggestions have been most helpful!
I'll post an update and let you know how it goes.
Thanks again! The only outstanding question I have right now is the one above regarding the mksysb backups.