topic Re: Disk space crunch. in Operating System - HP-UX

Disk space crunch.

joe_91 — Fri, 18 Oct 2002 16:42:19 GMT

Team:

We are upgrading Omniback on 10.20. we have only 150 meg on /opt and our upgrade requires more space. Is it possible to install this on say /opt/master (it is a seperate file system which has the required space) and then link it to /opt/omni? we install the omniback as a fileset (swpackaged). The whole idea is to get rid of the space issue in /opt and we cannot free any space there.

Best Regards
Joe.

Re: Disk space crunch.

John Poff — Fri, 18 Oct 2002 16:58:28 GMT

Hi,

It sounds like it should work. As long as the permissions are all correct, I don't see how OmniBack and swinstall could complain. Do you have enough room to make a new LV & filesystem for /opt/omni? It probably will work just as well, and it might be less confusing.

JP

Re: Disk space crunch.

OneNeck UNIXSA — Fri, 18 Oct 2002 17:07:15 GMT

You won't have any problems. If I remember the steps right, you swremove the OmniBack that you have which preserves the DB and then install the new one. Remember to print out you license keys. I split out my DB on a seperate filesystem /var/opt/omni/db40.

Re: Disk space crunch.

joe_91 — Fri, 18 Oct 2002 17:11:19 GMT

Hi:

Thanks. Can someone help with the steps please.

Best Regards
Joe.

Re: Disk space crunch.

John Poff — Fri, 18 Oct 2002 17:25:12 GMT

Hi again,

Which steps? For the OmniBack 4.0 upgrade? Or for making the LV and filesystem? By the way, Thomas is right. We made separate /var/opt/omni/db40 filesystems for the systems we upgraded to OB 4.0.

JP

Re: Disk space crunch.

joe_91 — Fri, 18 Oct 2002 17:47:51 GMT

Hi John:

Thanks. I mean the steps to install in /opt/master(where we have space) and then link to /opt/omni so that it works fine. we already made the package for the upgrade. We just have to swinstall it.

Thanks
Joe.

Re: Disk space crunch.

A. Clay Stephenson — Fri, 18 Oct 2002 18:00:13 GMT

Just to give you another way of looking at your problem - there is no rule that says that /opt must be in vg00. In fact, the only guys that MUST be on the boot drive are /stand, /, and primary swap. One alternative would be to make a new filesystem on another VG and copy everything in /opt over to /tempopt and then mount the new /opt.

Re: Disk space crunch.

joe_91 — Fri, 18 Oct 2002 18:47:31 GMT

Thanks clay:

Good option. But we cannot create a seperate VG. The reason is this package would be installed in multiple sites and in all the sites we have crunch on /opt but /opt/master is OK. Given this situation what would be the best option.

Thanks
Joe.

Re: Disk space crunch.

John Poff — Fri, 18 Oct 2002 19:06:11 GMT

Joe,

I agree with Clay, but if you really want to use your /opt/master mount, here is one way to try it (assuming you have a good backup copy of everything before you start):

1. Stop OmniBack.

/sbin/init.d/omni stop

2. Move all your existing /opt/omni files over to /opt/master/omni (emptying out the old /opt/omni so you can reclaim the space)

mv /opt/omni /opt/master

3. Create a symlink for /opt/omni to point to /opt/master/omni

ln -s /opt/master/omni /opt/omni

4. Restart OmniBack and try your upgrade.

/sbin/init.d/omni start

These steps will stop OmniBack, move everything in /opt/omni to /opt/master/omni, and restart OmniBack. I think you'll need to do that rather than trying to swinstall it directly into /opt/master/omni.

Good luck!

JP