make the entry in bp.conf
BPDBJOBS_COLDEFS = Media 6 true
BPDBJOBS_COLDEFS = client 6 true
and write one script to capture the values from bpdbjobs output.
Rgds
A D
Email : abhishek.dhin...@in.ibm.com
Joseph Despres
Sent by: veritas-bu-boun...@mailman.eng.auburn.edu
08/12/2010 07:28 PM
To
Bpdbjobs is the most easy way to do it, but if you want something else run
the command
bperror |grep "successfully wrote backup id" |awk '{print $9""$5"
"$15}'|sort |uniq
if you are using windows Google and find awk sort and uniq for dos. Or a
Unix like dos flavor.
stefanos
From
Hey Stefanos..
That did it!
Thanks!
Joe Despres
Backup Engineer
CSC
3521 Ribcowski Ct Raleigh, NC 27616
GIS | (o): 1.919.266.1799 | (c): 1.919.931.9674 |
jdesp...@csc.com | www.csc.com
https://c3.csc.com/groups/netback
This is a PRIVATE message. If you are not the intende
List,
I'm planning a Netbackup server upgrade from Solaris 8 sparc to Solaris 10
on CMT (T5120) and I wondered if anyone might have a check list or plan that
might have been used to do a similar upgrade? The master is the only server
in the environment.
At a high level I know I need to do the fol
Looks like I opened my mouth and stuck my foot in it.
bperror doesn't look back 1 week...
Joe Despres
Backup Engineer
CSC
3521 Ribcowski Ct Raleigh, NC 27616
GIS | (o): 1.919.266.1799 | (c): 1.919.931.9674 |
jdesp...@csc.com | www.csc.com
https://c3.csc.com/groups/netback
On Fri, Aug 13, 2010 at 12:35 PM, Joseph Despres wrote:
>
> Looks like I opened my mouth and stuck my foot in it.
>
> bperror doesn't look back 1 week...
>
It can but the default is 3 days I think. For longer-term reporting, look
at OpsCenter or a 3rd party reporting tool.
Ed Wilts, RHCE,
Bperror keeps the logs by default for 28 days and is following the "general"
log retention.
If you change the "days to keep logs" to 3, then bperror logs will be
deleted after 3 days.
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behal
so if you use the "-hoursago 168" option then it should show you 7 days
worth...
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of stefanos
Sent: Friday, August 13, 2010 12:57 PM
To: 'Ed Wilts'; 'Joseph
This is a basic list of what I've done this in the past:
1) Configure new server to match your old server as much as possible and
where applicable (interface configuration, filesystems, NBU patch level,
tape config, etc.).
2) Shut down NBU on original
3) Tar up the entire /usr/openv directory
4)
No.
You have to go to Host properties -> master server -> cleanup and change the
"keep logs for" parameter accordingly. Be aware that if someone had change
it from the default value (28 days) to something lower, then if you raze it
you may fill up the disk space.
stefanos
From: veritas-
Check this:
It works with the database, so no worry about logs.
It also works for up to 4 backup copies.
Change the hoursago value
bpimagelist -hoursago 24|awk '
BEGIN {
FRAG=""
IMAGE=""
}
/IMAGE / {
FRAG=""
Hey Stefanos..
Now this is getting real close!
Here's a snippet of the output ::--->
IMAGE ignsvsnwk001bck_1281646864 AS1028 cscbk06
IMAGE ignsvsnwk001bck_1281697264 AS1098 cscbk06
IMAGE ignsvsnwk002bck_1281646866 AS1028 cscbk06
IMAGE ignsvsnwk002bck_1281697266 AS1098 cscbk06
IM
Hi,
I did this in the past and got bitten a little bit, a couple of the FIBER
HBA's were legacy and were not supported in Solaris 10, make sure your
hardawre will be supported in Solaris 10.
Probably not a problem for a T5120 but definitely an issue for an old
V440.
Justin.
On Fri, 13 Aug
I've used the method of swinging the SAN attached /usr/openv/ over to the new
server and it worked perfectly. TAR will have the same affect.
As other have mentioned... Make sure you new system has NetBackup installed
before hand, Test out the new server to make sure everything works on it
bef
I have done something similar several times in our environment for either lease
returns or to perform a "fail safe" upgrade. What we have done is as follows...
1. Build out the replacement server as close to the original
2. Present a LUN to the old server and copy /usr/openv to the new LUN
3. St
Sorry my mistake.
Use this. It will give you the client, backupID, mediaID and media server.
If you need only the client and the media server, delete the $6 from the
(IMAGE=$2" "$6) and if you do not want the tape delete the $9 from every
(FRAG=$9" "$10).
bpimagelist -hoursago 24|awk '
BEGI
About the licenses.
The licenses are encrypted at /usr/openv/var directory and contains the name
of the master server. If you copy the entire /usr/openv, then you will have
no problem.
This command will help you to extract the licenses, if you want them
bpminlicense -list_keys [-verbose ]
stefanos
17 matches
Mail list logo
