Create New lvol.

[brian_31]

Hi Team:

We want to create a 5 gig logical volume on /dev/vg04(18 gig capacity). No issues in capacity. This is for veritas backup software. Is it ok if we create a logical volume

/dev/vg04/lvveritas and mount it as /veritas. I have attached the bdf output. Please let me know your valuable opinions. Also the netbackup is currently installed in /usr. Are there any gotchas for moving it to new logical volume?? Please advice.

Thanks
Brian.

[Hai Nguyen_1]

Brian,

I do not see any problem with your approach to creating the new lvol since based on bdf output, you have just used roughly 2GB for a filesystem.

Hai

[S.K. Chan]

If you're talking strictly about creating a 5GB LV and mounting it as /veritas then no problem there. Just take note if you want your FS to support largefiles make sure you use "-o largefiles" option in your newfs command or if you're using SAM, check the "largefiles" option. Are you saying you're migrating "netbackup" (eg: /usr/netbackup) to /veritas ? If that is the case why don't you mount your 5GB LV on /usr/netbackup instead ? Another option I suppose is using symbolic links but I'd rather mount the new LV onto a FS the way I wanted it to avoid using symbolic link.

[Joseph C. Denman]

Hi again Brian,

I don't think the creation of the lvol is the issue. That part is easy. I think the real question your asking is can you move the veritas software to a new filesystem and will it work properly. My answer would be, I'm not sure, but it is worth a try.

You could copy the software to the new file system and leave the old software untouched until you have verified that it is functioning properly.

1. create the new lvol and fs
2. mount the new lvol on /veritas
3. cd /usr/veritas
4. find . | cpio -pdmuxvl /veritas


Hope this helps.

...jcd...

[James R. Ferguson]

Hi Brian:

You could create your new logical volume and a new mountpoint '/usr/netbackup'. That is, you can have '/usr/ mounted as it is, and '/usr/netbackup' (or whatever it's called) mounted on your new logical volume.

You are wise to keep the the operating system software isolated and pure in vg00. This makes upgrades and/or updates to software easier.

Regards!

...JRF...

[George Petrides_1]

With the suggestion of moving the veritas directory from /usr to /veritas you might want link the old directory in usr with the new one e.g.
ln -s /veritas /usr/netbackup, but personally I like more the solution of mounting the filesystem under /usr/netbackup since it's cleaner. However, before you mount it to /usr/netbackup, mount it to /usr/NETBACKUP_TMP and use the find...cpio command suggest to move things from the /usr filesystem to the new /usr/netbackup filesystem. Then unmount it from /usr/NET..._TMP and mount it to /usr/netbackup. Whatever works for you...

[Steven Mertens]

hi,

I don't think it will give problems because
all the netbackup related binaries,
catalog information (netbackup master), ...
are normally under the same directory.
Maybe the start/stop scripts to start
the netbackup daemons (if it is master or
mediaserver ) should be altered because of
the path to the binaries changed.
If it's a client the related netbackup
entries in /etc/inetd.conf must also be
changed.

If, after the change there are problems you
can simply mount the lv at the orignal
location.

Like mentioned above , creating a link
is also a solution.

regards.

Steven

[Misa]

I may not be remembering right, but it seemed to me that there were a bunch of symbolic links in the Veritas installation, created at install time.

I like the idea of making a new LV and mounting it on /usr/netbackup.

--M????a

[Fragon]

There is no problem in your bdf output.
I think the only thing you must care is that when use "newfs" to create file system, please issue "-o largefiles" to enable over 2GB large file support.

ux

[brian_31]

Hi Team:

Thanks a lot. So here are the steps..
1. Make sure the -0 largefiles is used with the newfs command
(I am not sure here why i should use this. Are we not just creating a filesystem OR is there a possibility of a single file of size > 2gb created??). I did not understand this suggestion at all.

2. find .|cpio stuff
3.changing the /etc/inetd.conf file
Are there any other points to be considered??

Thanks once again,

Brian.

[Peter Kloetgen]

Hi Brian,

you need the -o largefiles option only, if you want to use single files bigger than 2 GB in the new filesystem. You asked, if you are simply not creating a file system....

--> you do, if you create the logical volume with SAM, he asks you for usage. You can give the largefiles option here also, look at file system properties...

--> if you create the volume with command line, you have to create a file system yourself!

Everything else is ok....

Allways stay on the bright side of life!

Peter

[Joseph C. Denman]

Brian,

I think you've got it. Be sure that before you make changes to the inetd.conf, you make a backup copy for fallback purposes. Also, once you make the changes, you will need to reread the conf file.

inetd -c #will do it

Good luck,

...jcd...

[Joseph C. Denman]

Sorry,

I also wanted to pointout S.K. statement about the largefiles. I don't think he was saying you really need the option. Just, if you plan on placing files larger than 2G on the fs, you will need to enable this option. Personnally, I only use this option when absolutly necessary.

Hope this helps,

...jcd...

[brian_31]

Hi:
Can someone clarify the -o largefiles requirement. I thought this was done only if you want to create a file >2GB and we are only creating a 5GB filesystem here.

Thanks
Brian.

[James R. Ferguson]

Hi Brian:

Yes, the 'largefiles' bit when set for a filesystem, enables you to create files that are larger than 2GB. For more information, have a look at this paper:

http://docs.hp.com/hpux/onlinedocs/os/lgfiles4.pdf

Regards!

...JRF...

[Hai Nguyen_1]

Brian,

After modifying /etc/inetd.conf, do not forget to run:
# /usr/sbin/inetd -c

to reflect the changes.

Hai

[Peter Kloetgen]

Hi again Brian,

you ONLY need largefiles option, if you want to create SINGLE FILES BIGGER THAN 2 GB in your new file system.

Allways stay on the bright side of life!

Peter

[Steven Mertens]

hi Brian,

Are you moving the netbackup client software
or master&media software ? Which version ?

On the systems here at my job , the software
is installed under /opt/openv and there's
a link /usr/openv -> /opt/openv. So be
sure that /usr/openv isnt a link at your
system. (ll -d /usr/openv).
Also watch out when you have oracle database
extensions installed. Because oracle uses
some libs from Veritas.

Normally there are three entries in /etc/inetd.conf

bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd
vopied stream tcp nowait root /usr/openv/netbackup/bin/vopied vopied
bpjava-msvc stream tcp nowait root /usr/openv/netbackup/bin/bpjava-msvc bpjava-msvc -transient

I think you don't need the large file option
when you create your fs.

regards,

Steven

[brian_31]

Hi Steven:

We are moving both 'coz it was installed in /usr initially and we wanted to move it out to a new volume group. Any gotchas there? we have 1 master and 4 clients.

Thanks
Brian.

[Steven Mertens · Accepted solution]

hi brian,

I have only hands on experience with netbackup veritas 3.2 and 3.4. At the moment
we are in the stadium to upgrade our
netbackup environment to 4.5, but the cdroms
didnt yet arrived.

My guess is there isnt much risk involved,
if you play it smart you can always go back.
Normally everything is installed onder the
/opt/openv direcorty (defaults), also the logs.

I would first start with moving a client, that the least risky. It is saver to
just copy the stuff first and if all
is ok , you can remove the old dir.

- make your lv & put it in /etc/fstab
- mount it :)
- make sure there arent any backups
busy while you are moving the stuff
(maybe you are scheduling backups from
within cron or maybe from in netbackup ?)
- change the inetd.conf entries.
to the new path.
- lets inetd reload its configuration
- do a test with bpbackup and watch on the
master in the job monitor if the backup
succeed.

Moving the master software can be tricky,
because when you screw up the netbackup
database ->> bye bye backups :)
Except if your netbackup is setup right
(backup the netbackup database to individuel tapes) its possible to recover
your db.

But if you first copy the soft, also change
inetd.conf and the start/stop script (
/sbin/init.d/vxnetb)
Just be sure that you stop first the
netbackup daemons on the master. You can
check this with the bpps command.
After you copied it , do a test with
one client and see if everything works.

Just see you have a good failback methode
so you can go back to the original situation.

regards,

Steven

[Steven Mertens]

Brian ,

If you can wait until the end of next week
i will try it first here at my job in a
test environment.


Steven

[brian_31]

Hi Steve:

Thanks. Sure i will wait.

Thanks once again
Brian.

[Steven Mertens]

Brian,

i havent forgotten you. Tomorrow i
will try to move a client and post
my procedure.

later

Steven