Any advice?

Duplication jobs are failing with a 129, insufficient space on our DR Data 
Domain.
We have over 17tb of free space at least.
What is causing this?
________________________
Joseph Armenti Jr.
NCC
Associate Production Support Engineer
Lord, Abbett & Co. LLC
90 Hudson Street
Jersey City, NJ 07302-3973
T. 201-827-4194
F. 201-827-5194
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Rusty Major
Sent: Wednesday, September 12, 2012 1:37 PM
To: Justin Piszcz; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Moving NBU install directory in Linux

Hey Justin,

Haven't done this with 7.x, but have done it on 6.x without issues.
Our steps are a bit different than yours as we don't do a catalog restore. We 
shutdown NBU and copy it over to the new location with the link already in 
place.

As I write this, I want to say that we tried moving NBU to another location on 
a live system and it caused issues (Solaris). I want to say the issues were 
related to packages, so we ended up having problems with patching down the 
line, but it's been about 2 or 3 years so it's a bit fuzzy. My recommendation 
would be to start the new server with the /usr/openv link to the new location 
already in place and then do your catalog restore.

Good Luck!
-Rusty

From: 
veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>]
 On Behalf Of Justin Piszcz
Sent: Tuesday, September 11, 2012 6:48 AM
To: veritas-bu@mailman.eng.auburn.edu<mailto:veritas-bu@mailman.eng.auburn.edu>
Subject: [Veritas-bu] Moving NBU install directory in Linux

Hello,

Need advice on moving /usr/openv elsewhere, why am I doing this?
We have to migrate off of an old server, its running out of space.
The new server will have space, but due to the way provisioning works, we will 
not be using the same path (in the end).

Steps:
0. The current install /usr/openv is a symlink to -> /mypath1/openv
1. Take catalog backup to nfs directory on master1 (since it has no more room 
and disk recovery is faster than tape).
2. We remove the master1 from the rack and turn it off.
3. We put in new server, initial recovery (catalog recovery) to the new system 
with the same hostname to /mypath1/openv again, this is so the catalog recovery 
doesn't break, I've tested it before where I pointed it to the new directory 
before the catalog recovery and it will fail.
4. Then, we will stop netbackup, mv /mypath/openv /new_path/openv and change 
the symlink from /usr/openv to the new path: /new_path/openv.
5. We will then start netbackup and we will be done.

I've done this before many times but this was in the 5.x-6.5.x days, I just 
want to make sure there are no issues doing this now with 7.1-7.5.

Anyone run into any issues with 7.1 or 7.5 while moving the install path?

Justin.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to