Increase disk size on OS side on the fly


Login or Register to Reply

 
Thread Tools Search this Thread
# 8  
@edfair

I will have to read entire documentation. I've installed BackupEDGE and left default settings and in RecoverEDGE the only option that appeared to me to have recovery image created was floppy drive, no ISO or anything other.

I need to have a second look at it, as I'm struggling with migration from physical to virtual server. Physical got tar of all directories and I tried to untar them on physical, but of course after reboot it crashed. Eventually I got to point where I excluded /etc /opt/{K,P} /var/opt/K directories and was able to relink kernel with only one error and succesfuly boot, but I'm not sure if services that were on physical were started fine (no erros during boot, but still).

@rbatte1

I will check it for sure. Thanks!

Thank you for the input, hopefully I will manage to solve my problems with that difficult (for me) Unix.
# 9  
The system will not run without /opt; it is the operating system. The files in /usr/bin and /bin, are only links to /opt/K....
Code:
-bash-3.2# cd /usr/bin                                                          
-bash-3.2# ls -li tar                                                           
32410 lrwxrwxrwx    1 root     sys         35 Feb 15  2013 tar -> /opt/K/SCO/Unix/6.0.0Ni/usr/bin/tar                                                           
-bash-3.2#

The kernel is built from files in /etc/conf.
The system documentation is here if you did not install it.
DocView: Access to SCO OpenServer Documentation
You did not say if your lack of disk space is a result of incremental file growth, or not allocating enough space to start with.
If the former, the following are places to look.
/usr/spool/mail, for unread system email (if empty, the location of mail boxes is stored in /usr/mmdf/mmdftailor.
/usr/adm/messages
/usr/adm/syslog
/usr/spool/lp/logs
/usr/tmp
# 10  
Entire case started with project for p2v migration of old SCO machines. One of the machines had entire directory tar'ed and then we had to deploy virtual one. OVF eventually was deployed, but after comparison of disk setup of Physical with Virtual I though that root partition should be extended, as physical one had 2GB of space more. That's why the question in that thread. Eventually I'v noticed that Physical one has only 4GB of space used so Virtual machine is fine, I just needed another partition, and that was easy task.

Then, having virtual machine deployed i started restoring backed up tar files and restoring them on virtual as it is. I was prepared for some configs to be modified (/etc/fstab, etc.). But it turned out that partition table got messed up, so I tried and tried. Eventually I'v got to the point I described, I've noticed that actually all important things are in /opt/{K,P}, so I've first tar'ed those directories on virtual machine, restored physical machine tars, and overwritten what I previously tared on virtual one. And that allowed me to boot the machine without one error during boot procedure. But I don't know if that's proper way to migrate (for sure not) and if all services that supposed to start started (I a assume no errors means something).

Maybe you already know better procedure for doing such migration in diy way, without use of enterprise software. If teams that will test it tell me that I doeasn't work as it should I'll start reading documentation for Backup/RestoreEDGE and other software that was posted here.

Still thanks for all help, and If you have more suggestions I will be glad to read them.

Last edited by goldenboy; 11-03-2016 at 11:16 AM.. Reason: typos
# 12  
If you used tar to backup the entire system, you would need to put it back the data on a system with appropriate filesystems already mounted, that way tar will write them to the correct slice of disk.

If you are planning to restore everything and the backup was made with tar -cvf device / then you can only restore to the exact path. You will also need to make sure you don't overwrite OS critical files or your machine may not boot or fail to work properly.

Can you elaborate more on how you did the copy?

Again, Storix would be an excellent tool here (if it supports your OS version) and it would allow you to take a backup of your physical server that you can use to create a virtual server and update the disk allocations at the same time. It will help you go P2P, P2V, V2V & V2P.

I have to confirm that I have no financial interest in it, I just think it's a very good product. There are others available, but this one seems to do far more in a far more useful way. To be honest it exceeds what HP-UX's Ignite and AIX's mysysb do by adding in the ability to adjust various things (storage, network etc.) when you start the recovery. Take the free trial, watch the videos and choose for yourself.

Also have a look at the IBM view of it IBM - Storix System Backup Administrator (SBAdmin) for AIX



Kind regards,
Robin
(Never employed, contracted or bribed by Storix or IBM)
# 13  
I was not doing that copy by myself, my colleague did, the result is each directory under root has own tar file - /dev was excluded. He said that he used option to preserve file attributes.

At first I've extracted it as it was - hoping that it will work, as on Linux it would, but when I used 'scoadmin' to reconfigure network it didn't let me relink/recompile kernel because it couldn't find some devices. Also partition table was changed, so it seems that it keeps partition table in some file... it was really strange for me.

Eventually, I found that SCO keeps system specific files in those K and P folders so I did like this:
  1. tar /etc/ /usr/SCO/K,P on virtual server
  2. untar backup files (all subfolders of /) from physical server on virtual
  3. overwrite /etc /usr/SCO/K,P with tar file done in first step

Surprisingly after such operation relink of kernel was fine, and boot was fine also, I'm not sure if it works as on production if all services are fine.

The reason I did it that way, I thought that everything that was on physical one will be transferred but overwriting crucial directories with virtual machine default ones (those after installation) will solve the issue with drivers, partition setup, but still services in rc.d (transferred from physical) will be there and will be able to start and will have their configuration files.

So, It would be good to know if such procedure is reliable or if there are some directories that should be included in first step, so that files from new virtual machine are kept same as they were after the installation.

Last edited by rbatte1; 11-07-2016 at 11:43 AM.. Reason: Converted to formatted number-list
# 14  
I would be inclined to do a fresh install in order to create the virtual system.
Install all the maintenance patches.
Install all the additional software.
Use 'ap' to transfer all the user accounts.
Use the following:
Code:
cd /usr/bin
ls -ltr |grep -v "@"
cd /bin
ls -ltr |grep -v "@"

This will list all the files in those two directories that are not part of the OS, and you can check the files that have dates significantly more recent that either the OS media date, or the original install date.
Copy the contents of /etc/rc?.d along with /usr/spool/cron/crontabs.
Assuming you are using SYSV printing and not CUPS, copy the contents of /usr/spool/lp/admins/lp/interfaces from the old system, after you have re-created all local printers on the new system.
Copy /etc/hosts, and /etc/resolv.conf from the old system.
If you use the same OS license on the new system, you will have to keep the systems on different tcp subnets, otherwise one of the systems will shut down.
Login or Register to Reply

|
Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Increase disk size of guest domain
apmcd47
Host System: SPARC S7-2 Server; 2x8-core CPUs; 128Gb RAM; 2x600Gb HDD. running Solaris 11.3. Last login: Tue Sep 19 14:42:42 2017 from xxx.xxx.xxx Oracle Corporation SunOS 5.11 11.3 June 2017 $ uname -a SunOS sog01 5.11 11.3 sun4v sparc sun4v $ Original physical systems: Sun...... Solaris
0
Solaris
Delete syslog but size disk can't increase
edydsuranta
Hi Experts, I have a problem wih /var. Disk /var is full. After i investigate, i found file /var/log/syslog.0 is growing rapidly. The size is 4.3G. I tried to move syslog.0 to another disk and file was moved successfully. My question is why size /var can't increase? used space still 100%. ...... Solaris
7
Solaris
Increase size to sd[b-c]
kopper
hi guys I am working on my vmware workstation. I have a /dev/sdb which is 5GB. I am using LVM. Now I increase /dev/sdb 2 more GB. fdisk -l shows 7 GB but pvscan still shows 5GB. how do I make my system recognize the new 7GB added and be able to add those to my physical volumen and...... UNIX for Dummies Questions & Answers
1
UNIX for Dummies Questions & Answers
How to increase Virtual Disk size
kishorbhede
Hello, I am working AIX VIO server and extended Virtual Disk of one of the Partition with 10GB. After starting partition, i am not able to see increased size of disk. Can you please help me what I need to do to increase the size of virtual disk from partition? Thanks Kishor ...... AIX
7
AIX
increase size
jyoti
Hi All, one of the mount point in Hp ux server has reached 95% its a data base file and can not be deleted. so i want to know how to increase the size of mount point i am new to unix ,please help me... HP-UX
1
HP-UX

Featured Tech Videos