10. Run the BAR user interface to restore the remaining image database
if the DR image is a result of an incremental backup.
we have had issues with this step attempting to recover the catalog without the
DR file...
Nathan Schmidt
Veritas Certified Professional
Nathan.Schmidt AT shell DOT com
Houston Texas
713-546-6813
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]On Behalf Of
veritas-bu-request AT mailman.eng.auburn DOT edu
Sent: Wednesday, March 12, 2008 7:55 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Veritas-bu Digest, Vol 23, Issue 21
Send Veritas-bu mailing list submissions to
veritas-bu AT mailman.eng.auburn DOT edu
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
or, via email, send a message with subject or body 'help' to
veritas-bu-request AT mailman.eng.auburn DOT edu
You can reach the person managing the list at
veritas-bu-owner AT mailman.eng.auburn DOT edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Veritas-bu digest..."
Today's Topics:
1. Re: Anyone restore a 6.0 environment from catalog backup?
(Robert Griffin)
2. 6.0 MP4: Number of jobs shown in activity monitor (echum)
3. Re: Lets hear about your upgrade experience! 5.x - 6.5 (Tony T.)
4. NBU 6.0 MP5 - Jobs queued, not going active (Chris_Millet)
5. 6.0 MP4: Number of jobs shown in activity monitor (Chris_Millet)
6. bpexpdate Could not deassign .. could not deassign media
(Chris_Millet)
7. ndmp error 99 - block size (Chris_Millet)
8. Re: 6.0 MP4: Number of jobs shown in activity monitor
(Mellor, Adam A.)
9. Re: Media Server with multiple NICS] (Esson, Paul)
10. Upgraded Solaris 9 to 10: scsi command failed, may be
timeout, scsi_pkt.us_reason = 4 (Alexander Skwar)
11. oracle policy with compression turned on (mark wragge)
12. Re: Media Server with multiple NICS] (Travis Kelley)
13. Re: Anyone restore a 6.0 environment from catalog backup?
(Jared.Seaton AT mylanlabs DOT com)
14. Re: oracle policy with compression turned on
(Jared.Seaton AT mylanlabs DOT com)
15. Vault failure after upgrade from 6.0MP4 to 6.5.1
(netbackup AT whelan-consulting.co DOT uk)
16. Re: NBU 6.0 MP5 - Jobs queued, not going active
(Marianne Van Den Berg)
----------------------------------------------------------------------
Message: 1
Date: Tue, 11 Mar 2008 16:39:28 -0500
From: Robert Griffin <rmg AT ua DOT edu>
Subject: Re: [Veritas-bu] Anyone restore a 6.0 environment from
catalog backup?
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID: <9C0F4732-AAE7-4271-A6D2-86FD1CD49824 AT ua DOT edu>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Haven't tested this either, but NBU certainly gives the impression
that it *could* be done without the DR file. For the sake of
discussion, here are the instructions that 6.0MP4 includes in an
email with our DR file. Note 4 steps with versus 14 without:
Disaster Recovery Procedure using the DR Image File
In the event of a catastrophic failure, use the following procedure
to rebuild
the previous NetBackup environment.
Note: If new hardware is required, make sure that the devices contain
drives
capable of reading the media and that the drive controllers are
capable of
mounting the drives.
1. Install NetBackup.
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Make sure that the master server can access the attached DR image
file.
Start the NetBackup Recovery Wizard from the NetBackup Administration
Console. Or, start the wizard from a command line by entering
bprecover -wizard.
Disaster Recovery Procedure without the DR Image File
NOTE: ONLY ATTEMPT THIS AS A LAST RESORT
If you do not have the attachment included with this email, use the
following
instructions to recover your catalog:
1. Install NetBackup.
2. Configure the devices necessary to read the media listed above.
3. Inventory the media.
4. Run:
bpimport -create_db_info [-server name] -id X01234
5. Go to the following directory to find the DR image file
xxpolicy_1205238288_INCR:
/usr/openv/netbackup/db/images/xxmaster/1205000000/tmp
6. Delete the other files in the directory.
7. Open xxpolicy_1205238288_INCR file and find the BACKUP_ID
(for example: xxmaster_1205238288).
8. Run:
bpimport [-server name] -backupid xxmaster_1205238288
9. Run:
bprestore -T -w [-L progress_log] -C xxmaster -t 35 -p xxpolicy
-X -
s 1205238288 -e 1205238288 /
10. Run the BAR user interface to restore the remaining image database
if the DR image is a result of an incremental backup.
11. To recover the NetBackup relational database, run:
bprecover -r -nbdb
12. Stop and Start NetBackup
13. Configure the devices if any device has changed since the last
backup.
14. To make sure the volume information is updated, inventory the media
to update the NetBackup database.
Robert Griffin
Unix Systems Administrator
OIT, Enterprise Technology
The University of Alabama
<rmg AT ua DOT edu> | 205-348-0177
On Mar 11, 2008, at 15:32, veritas-bu-request AT mailman.eng.auburn DOT edu
wrote:
> Message: 7
> Date: Tue, 11 Mar 2008 15:12:59 -0500
> From: Rusty.Major AT sungard DOT com
> Subject: Re: [Veritas-bu] Anyone restore a 6.0 environment from
> catalog backup?
> To: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
> Cc: veritas-bu AT mailman.eng.auburn DOT edu,
> veritas-bu-bounces AT mailman.eng.auburn DOT edu
> Message-ID:
> <OF9AFB3BF8.8833A6D9-
> ON85257409.006EFBE5-86257409.006F0DB0 AT sungard DOT com>
>
> Content-Type: text/plain; charset="utf-8"
>
> My impression is that you need the DR file. Period. I haven't
> tested it so
> I can't say, though.
>
> Rusty Major, MCSE, BCFP, VCS ? Sr. Storage Engineer ? SunGard
> Availability Services ? 757 N. Eldridge Suite 200, Houston TX 77079 ?
> 281-584-4693
> Keeping People and Information Connected? ?
> http://availability.sungard.com/
> P Think before you print
> CONFIDENTIALITY: This e-mail (including any attachments) may contain
> confidential, proprietary and privileged information, and unauthorized
> disclosure or use is prohibited. If you received this e-mail in
> error,
> please notify the sender and delete this e-mail from your system.
>
>
>
> Justin Piszcz <jpiszcz AT lucidpixels DOT com>
> Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> 03/11/2008 11:48 AM
>
> To
> veritas-bu AT mailman.eng.auburn DOT edu
> cc
>
> Subject
> [Veritas-bu] Anyone restore a 6.0 environment from catalog backup?
>
>
>
>
>
>
> With < 6.0x you bprecover -r and you're pretty much all set;
> however, for
> 6.0 it also writes out a DR file, has anyone done recovery testing
> both
> WITH and WITHOUT the DR file?
>
> Justin.
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
------------------------------
Message: 2
Date: Tue, 11 Mar 2008 19:00:04 -0400
From: echum <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] 6.0 MP4: Number of jobs shown in activity
monitor
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <1205276404.m2f.267181 AT www.backupcentral DOT com>
By default, the GUI will only show the last 3 days of backup jobs. Use the
bpdbjobs command to change this value:
/usr/openv/netbackup/bin/admincmd/bpdbjobs -clean -keep_days <number of days>
See technote below for more info
http://seer.entsupport.symantec.com/docs/291075.htm
+----------------------------------------------------------------------
|This was sent by enoch.chum AT stantec DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 3
Date: Tue, 11 Mar 2008 21:10:06 -0500
From: "Tony T." <rollthebones AT gmail DOT com>
Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x
- 6.5
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID:
<262f880c0803111910l129a97acn1fbdb4bdb306527c AT mail.gmail DOT com>
Content-Type: text/plain; charset="iso-8859-1"
On Mon, Mar 10, 2008 at 3:46 PM, rascal <rascal1981 AT gmail DOT com> wrote:
> ok, so we found an interesting issue now with our upgrades. Right now our
> master/media server is experiencing issues with hot catalog backups (to
> tape). Here are some interesting, fun facts:
>
> 1. our master server is an aix box with multiple interfaces
> 2. its an upgrade from 5.1mp5 to 6.5.1
> 3. everything BUT catalog works just peachy
> 4. Error codes in include 252 (800), and 134.
>
I have not seen that, but our upgrade is nothing short of a nightmare.
We ran the NBCC tool again, and there was one error that we sent to support
and they had us run a command to fix it. So we started the
upgrade...*everything* took like an hour; after clicking "setup", the status
bar didnt move and just about the time we were going to give up it
finished.
Then the dreaded "nbpushdata" command produced an error. Sent that into
support, after about 5 hours of back and forth running various commands
nothing is working. NBU wont start, it generates all sorts of errors.
Support finally said we should roll back to 5, but didn't tell us how. They
said instead we could just patch it to 6.5.1. Well that had the predictable
result of just hanging for an hour, then finally spitting back an error
along the lines of "Setup was interupted before it could finish"
What a comedy of errors this is...I don't even know where to begin, support
had us run so many things that are not listed in their 20 page "Upgrade Doc"
that I would not feel comfortable ever doing this again.
In fact the next time I hear the word upgrade I am going to suggest getting
new equipment, since NBU is obviously not stable enough to withstand an in
place upgrade.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20080311/039bba5b/attachment.html
------------------------------
Message: 4
Date: Wed, 12 Mar 2008 00:46:03 -0400
From: Chris_Millet <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] NBU 6.0 MP5 - Jobs queued, not going active
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <1205297163.m2f.267194 AT www.backupcentral DOT com>
Marianne, could you share the resolution to this issue? We also see this
problem on a new environment where we are attempting to do just standard
filesystem backups on several thousand clients. The master server has plenty
of horsepower (16GB, 8 core T2000) but I wonder if Netbackup keeps getting hung
up when juggling that many client jobs. Our environment we are seeing this in
is also v6.0_MP5.
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 5
Date: Wed, 12 Mar 2008 02:08:58 -0400
From: Chris_Millet <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] 6.0 MP4: Number of jobs shown in activity
monitor
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <1205302138.m2f.267196 AT www.backupcentral DOT com>
echum wrote:
> By default, the GUI will only show the last 3 days of backup jobs. Use the
> bpdbjobs command to change this value:
>
> /usr/openv/netbackup/bin/admincmd/bpdbjobs -clean -keep_days <number of days>
>
> See technote below for more info
> http://seer.entsupport.symantec.com/docs/291075.htm
I think alternatively you can also put in the registry (for windows) or the
bp.conf (for UNIX) the KEEP_JOBS_HOURS and KEEP_JOBS_SUCCESSFUL_HOURS since
bpdbjobs -clean is busted on Windows in v6.0_MP4.
http://seer.entsupport.symantec.com/docs/296104.htm
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 6
Date: Wed, 12 Mar 2008 02:14:51 -0400
From: Chris_Millet <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] bpexpdate Could not deassign .. could not
deassign media
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <1205302491.m2f.267197 AT www.backupcentral DOT com>
See this technote. We see this most commonly in our environment due to the
tape being assigned for a backup before it can be fully returned to Scratch.
Just a timing thing.
http://seer.entsupport.symantec.com/docs/294805.htm
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 7
Date: Wed, 12 Mar 2008 02:22:51 -0400
From: Chris_Millet <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] ndmp error 99 - block size
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <1205302971.m2f.267198 AT www.backupcentral DOT com>
My understanding is that NUMBER_DATA_BUFFERS and SIZE_DATA_BUFFERS_NDMP only
apply if you are doing "Remote NDMP" 3-way backup through a Netbackup media
server. If the tape device is attached to the NDMP host itself, than those
variables have to be set on the NDMP host. See your vendor documentation.
You can read more details about those touch files in the Backup Planning and
Performance Tuning Guide.
As for that error, you may want to open a support case regarding that. The
bptm process performs a simple calculation after completing the writing of the
backup, confirming that the number of bytes written is divisible by 512. If it
is, it passes on an exit 0 (success) and ends the job. If the number is not
divisible by 512, some amount of bytes did not make it thru, and the job fails.
You can also get more detail in the ndmpagent log by doing:
vxlogview -i ndmpdagent -d T,s,x,p | grep PID:10276
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 8
Date: Wed, 12 Mar 2008 15:43:00 +0900
From: "Mellor, Adam A." <Adam.Mellor AT woodside.com DOT au>
Subject: Re: [Veritas-bu] 6.0 MP4: Number of jobs shown in activity
monitor
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Message-ID:
<55A93A8FDF17844FBD201175FB138CC6056DA472 AT permls07.wde.woodside.com
DOT au>
Content-Type: text/plain; charset="us-ascii"
I previously (pre 6.x) had this set to "a couple of weeks" it may have
even been a month.
Never had any issues with it, although I do aknologe the java gui did
get slow.
If you are using VBR under 6.5 (I never ran 6.0, it may be the same) The
agent would timeout after 15 minutes, and the bpdbjobs command it ran
took over 25 minutes.
I received a patch from nbu support for the java VBR agent to enable me
to set a timeout value for the agent.
Something to be aware of.
Adam.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
Chris_Millet
Sent: Wednesday, 12 March 2008 3:09 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 6.0 MP4: Number of jobs shown in activity monitor
echum wrote:
> By default, the GUI will only show the last 3 days of backup jobs. Use
the bpdbjobs command to change this value:
>
> /usr/openv/netbackup/bin/admincmd/bpdbjobs -clean -keep_days <number
> of days>
>
> See technote below for more info
> http://seer.entsupport.symantec.com/docs/291075.htm
I think alternatively you can also put in the registry (for windows) or
the bp.conf (for UNIX) the KEEP_JOBS_HOURS and
KEEP_JOBS_SUCCESSFUL_HOURS since bpdbjobs -clean is busted on Windows in
v6.0_MP4.
http://seer.entsupport.symantec.com/docs/296104.htm
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.
------------------------------
Message: 9
Date: Wed, 12 Mar 2008 07:45:30 -0000
From: "Esson, Paul" <Paul.Esson AT Redstor DOT com>
Subject: Re: [Veritas-bu] Media Server with multiple NICS]
To: "Travis Kelley" <rhatguy AT gmail DOT com>,
<veritas-bu AT mailman.eng.auburn DOT edu>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Travis,
Very good point! I was neglecting the network routing aspect. So if I
create multiple SERVER= entries for my Media Servers with the
appropriate hostnames (resolving back to the correct IP addresses) and
put these lines in the relevant bp.conf files on the clients then the
routing should take care of the rest?
Regards,
Paul Esson
-----Original Message-----
From: Travis Kelley [mailto:rhatguy AT gmail DOT com]
Sent: 04 March 2008 16:49
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Media Server with multiple NICS]
You should be able to achieve this without anu configuration changes
to NB itself. We use multiple nics and you just have to make sure the
routing is correct. When bpcd on the media server connects to the
client the client will then connect back to that same ip (assuming
that ip is allowed in the bp.conf on the client). So make sure you
route traffic out the proper interface and the client will send data
back through that interface. You do not need multiple storage units.
The storage unit is not tied to the interface the data came in on.
Hope this helps.
Travis
- Original message -
Yes, appears so, I'd like to know what you find. Regards Carl ...
On 3/4/08, Travis Kelley <travis.kelley AT etrade DOT com> wrote:
>
--
Sent from Gmail for mobile | mobile.google.com
------------------------------
Message: 10
Date: Wed, 12 Mar 2008 10:21:50 +0100
From: Alexander Skwar <alexanders.mailinglists+nospam AT gmail DOT com>
Subject: [Veritas-bu] Upgraded Solaris 9 to 10: scsi command failed,
may be timeout, scsi_pkt.us_reason = 4
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID: <2785188.mpscyFdaGs AT schmarck DOT cn>
Content-Type: text/plain; charset=us-ascii
Hello.
Time to revive an old problem that I have.
I updated SunFire V240 system from Solaris 9 to Solaris 10 U4. I'm
using NetBackup 5.1 MP4 on this system. After I updated this machine,
using Live Upgrade (lu) if that matters, I get the following messages
shown on the console:
Mar 12 03:03:47 fhids01 avrd[3567]: [ID 753170 daemon.notice] st.conf
configuration for HPUltrium2-SCSI0 (device 0), name [HP Ultrium LTO 2], vid [HP
Ultrium 2*], typ
e 0x3b, block size 0, options 0x18619 (see st(7D) man page)
Mar 12 03:04:02 fhids01 scsi: [ID 107833 kern.warning] WARNING:
/pci@1e,600000/scsi@2,1 (mpt1):
Mar 12 03:04:02 fhids01 Connected command timeout for Target 5.
Mar 12 03:04:02 fhids01 scsi: [ID 107833 kern.warning] WARNING:
/pci@1e,600000/scsi@2,1 (mpt1):
Mar 12 03:04:02 fhids01 Target 5 reducing sync. transfer rate
Mar 12 03:04:02 fhids01 mpt: [ID 795936 kern.warning] WARNING:
ID[SUNWpd.mpt.sync_wide_backoff.6014]
Mar 12 03:04:03 fhids01 avrd[3567]: [ID 832037 daemon.error] scsi command
failed, may be timeout, scsi_pkt.us_reason = 4
Mar 12 03:04:03 fhids01 avrd[3567]: [ID 794471 daemon.error] log sense failed
on HPUltrium2-SCSI0 (device 0, /dev/rmt/0cbn): Error 0 (0)
Mar 12 03:04:03 fhids01 tldcd[3572]: [ID 832037 daemon.error] scsi command
failed, may be timeout, scsi_pkt.us_reason = 4
Mar 12 03:04:21 fhids01 scsi: [ID 107833 kern.warning] WARNING:
/pci@1e,600000/scsi@2,1 (mpt1):
Mar 12 03:04:21 fhids01 Connected command timeout for Target 0.
Mar 12 03:04:21 fhids01 tldcd[3572]: [ID 832037 daemon.error] scsi command
failed, may be timeout, scsi_pkt.us_reason = 4
Mar 12 03:04:21 fhids01 tldcd[3572]: [ID 359089 daemon.error] TLD(0) mode_sense
ioctl() failed: No such file or directory
Mar 12 03:04:21 fhids01 tldd[3564]: [ID 320639 daemon.error] TLD(0)
unavailable: initialization failed: Unable to sense robotic device
Mar 12 03:04:25 fhids01 ntpd[4150]: [ID 702911 daemon.notice] ntpd
[email protected] Tue Jan 18 10:19:49 EST 2005 (1)
Mar 12 03:04:36 fhids01 sg: [ID 686534 kern.notice] VERITAS SCSA Generic
Revision: 3.4d
Because of this, NetBackup does not work.
When I go to the ok-prompt of the system, I get:
{1} ok probe-scsi-all
/pci@1c,600000/scsi@2,1
/pci@1c,600000/scsi@2
Target 0
Unit 0 Disk SEAGATE ST373307LSUN72G 0507
Target 1
Unit 0 Disk SEAGATE ST373307LSUN72G 0507
/pci@1e,600000/scsi@3,1
Target 0
Unit 0 Disk SUN StorEdge 3310 0325 1144856576 Blocks, 559012 MB
/pci@1e,600000/scsi@3
/pci@1e,600000/scsi@2,1
Target 0
Unit 0 Removable Device type 8 ADIC FastStor 2 G12r
Target 5
Unit 0 Removable Tape HP Ultrium 2-SCSI F67A
/pci@1e,600000/scsi@2
When I boot the system, /dev/rmt/0cbn is:
bash-3.00# ls -la /dev/rmt/0cbn
lrwxrwxrwx 1 root other 47 Aug 29 2005 /dev/rmt/0cbn ->
../../devices/pci@1e,600000/scsi@2,1/st@5,0:cbn
When I re-activate the S9 boot environment, there are no timeout
messages reg. this device (or any device at all). Ie. NetBackup
works fine again.
I searched sunsolve for
HP Ultrium 2, but only found references to an updated firmware in document
ID 116622-03. When I run "tload" from this firmware update tool, it
scans the system and displays the supported/attached devices:
bash-3.00# ./tload
ATTACHED DEVICES:
Device Supplier Product Rev Serial Number Device State
-------------- -------- ---------------- ---- ------------- -------------
1:0ln HP Ultrium 2-SCSI F67A HUL5E02510 Available
Doesn't that mean, that the system can communicate with the tape drive?
But why do I get "Connected command timeout" messages?
Thanks,
Alexander
------------------------------
Message: 11
Date: Wed, 12 Mar 2008 10:26:29 +0000 (GMT)
From: mark wragge <mark_t_wragge AT yahoo DOT ie>
Subject: [Veritas-bu] oracle policy with compression turned on
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID: <49914.95315.qm AT web28001.mail.ukl.yahoo DOT com>
Content-Type: text/plain; charset="iso-8859-1"
How does the compression option on an Oracle policy function? Is it the same as
turning on compression on a standard filesystem backup OR is this a compression
feature specific to oracle database backups?
I am considering turning on compression on a Virtual Tape Librayr and on the
oracle policy. Should i just turn it on on the VTL (EMC EDL).
Thanks.
Send instant messages to your online friends http://uk.messenger.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20080312/dfc6e5df/attachment.htm
------------------------------
Message: 12
Date: Wed, 12 Mar 2008 08:38:21 -0400
From: "Travis Kelley" <rhatguy AT gmail DOT com>
Subject: Re: [Veritas-bu] Media Server with multiple NICS]
To: "Esson, Paul" <Paul.Esson AT redstor DOT com>,
veritas-bu AT mailman.eng.auburn DOT edu
Message-ID:
<87c0fb330803120538h612fe31eyeb0fce77b21052e0 AT mail.gmail DOT com>
Content-Type: text/plain; charset=ISO-8859-1
Exactly. We have SERVER entries for each of our media servers nics in
or clients bp.conf so then we just route traffic OUT whichever nic we
want on the media server and the client connects back and sends data
to that nic.
I'm not sure why you would want to have different storage units on the
same media server for its different virtual hostnames. We write data
to the same tape stu no matter which nic it rides in on. Maybe I'm
understanding some of the other posts on this thread wrong?
- Original message -
Travis, Very good point! I was neglecting the network rou...
On 3/12/08, Esson, Paul <Paul.Esson AT redstor DOT com> wrote:
> Travis,
>
> Very good point! I was neglecting the network routing aspect. So if I
> create multiple SERVER= entries for my Media Servers with the
> appropriate hostnames (resolving back to the correct IP addresses) and
> put these lines in the relevant bp.conf files on the clients then the
> routing should take care of the rest?
>
> Regards,
>
> Paul Esson
> -----Original Message-----
> From: Travis Kelley [mailto:rhatguy AT gmail DOT com]
> Sent: 04 March 2008 16:49
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Media Server with multiple NICS]
>
> You should be able to achieve this without anu configuration changes
> to NB itself. We use multiple nics and you just have to make sure the
> routing is correct. When bpcd on the media server connects to the
> client the client will then connect back to that same ip (assuming
> that ip is allowed in the bp.conf on the client). So make sure you
> route traffic out the proper interface and the client will send data
> back through that interface. You do not need multiple storage units.
> The storage unit is not tied to the interface the data came in on.
> Hope this helps.
>
> Travis
> - Original message -
> Yes, appears so, I'd like to know what you find. Regards Carl ...
>
>
>
> On 3/4/08, Travis Kelley <travis.kelley AT etrade DOT com> wrote:
> >
>
> --
> Sent from Gmail for mobile | mobile.google.com
>
>
--
Sent from Gmail for mobile | mobile.google.com
------------------------------
Message: 13
Date: Wed, 12 Mar 2008 08:41:14 -0400
From: Jared.Seaton AT mylanlabs DOT com
Subject: Re: [Veritas-bu] Anyone restore a 6.0 environment from
catalog backup?
To: "Robert Griffin" <rmg AT ua DOT edu>
Cc: veritas-bu AT mailman.eng.auburn DOT edu,
veritas-bu-bounces AT mailman.eng.auburn DOT edu
Message-ID:
<OFB83D1717.910FAA32-ON8525740A.0044882D-8525740A.0045B1BB AT MYL DOT
COM>
Content-Type: text/plain; charset="us-ascii"
You have to have the DR File to recover from an 'online' catalog backup.
Whether that means you use the DR file that is email/stored somewhere, or
the method described by Robert.
I have done a recovery using both methods. In the case below where you
have to retrieve the DR File, I stopped at step 8 and then used the
Catalog Recovery Wizard and pointed it to the dr file and everything
worked fine.
Jared M. Seaton
Recovery Administrator
Mylan Inc.
304-554-5926
304-685-1389 (Cell)
"Robert Griffin" <rmg AT ua DOT edu>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
03/11/2008 05:48 PM
To
veritas-bu AT mailman.eng.auburn DOT edu
cc
Subject
Re: [Veritas-bu] Anyone restore a 6.0 environment from catalog backup?
Haven't tested this either, but NBU certainly gives the impression
that it *could* be done without the DR file. For the sake of
discussion, here are the instructions that 6.0MP4 includes in an
email with our DR file. Note 4 steps with versus 14 without:
Disaster Recovery Procedure using the DR Image File
In the event of a catastrophic failure, use the following procedure
to rebuild
the previous NetBackup environment.
Note: If new hardware is required, make sure that the devices
contain
drives
capable of reading the media and that the drive controllers are
capable of
mounting the drives.
1. Install NetBackup.
2. Configure the devices necessary to read the media
listed above.
3. Inventory the media.
4. Make sure that the master server can access the
attached DR image
file.
Start the NetBackup Recovery Wizard from the NetBackup
Administration
Console. Or, start the wizard from a command line by
entering
bprecover -wizard.
Disaster Recovery Procedure without the DR Image File
NOTE: ONLY ATTEMPT THIS AS A LAST RESORT
If you do not have the attachment included with this email, use the
following
instructions to recover your catalog:
1. Install NetBackup.
2. Configure the devices necessary to read the media
listed above.
3. Inventory the media.
4. Run:
bpimport -create_db_info [-server name]
-id X01234
5. Go to the following directory to find the DR image
file
xxpolicy_1205238288_INCR:
/usr/openv/netbackup/db/images/xxmaster/1205000000/tmp
6. Delete the other files in the directory.
7. Open xxpolicy_1205238288_INCR file and find the
BACKUP_ID
(for example: xxmaster_1205238288).
8. Run:
bpimport [-server name] -backupid
xxmaster_1205238288
9. Run:
bprestore -T -w [-L progress_log] -C
xxmaster -t 35 -p xxpolicy -X -
s 1205238288 -e 1205238288 /
10. Run the BAR user interface to restore the remaining
image database
if the DR image is a result of an incremental backup.
11. To recover the NetBackup relational database, run:
bprecover -r -nbdb
12. Stop and Start NetBackup
13. Configure the devices if any device has changed since
the last
backup.
14. To make sure the volume information is updated,
inventory the media
to update the NetBackup database.
Robert Griffin
Unix Systems Administrator
OIT, Enterprise Technology
The University of Alabama
<rmg AT ua DOT edu> | 205-348-0177
On Mar 11, 2008, at 15:32, veritas-bu-request AT mailman.eng.auburn DOT edu
wrote:
> Message: 7
> Date: Tue, 11 Mar 2008 15:12:59 -0500
> From: Rusty.Major AT sungard DOT com
> Subject: Re: [Veritas-bu] Anyone restore a 6.0 environment from
> catalog backup?
> To: Justin Piszcz <jpiszcz AT lucidpixels DOT com>
> Cc: veritas-bu AT mailman.eng.auburn DOT edu,
> veritas-bu-bounces AT mailman.eng.auburn DOT edu
> Message-ID:
> <OF9AFB3BF8.8833A6D9-
> ON85257409.006EFBE5-86257409.006F0DB0 AT sungard DOT com>
>
> Content-Type: text/plain; charset="utf-8"
>
> My impression is that you need the DR file. Period. I haven't
> tested it so
> I can't say, though.
>
> Rusty Major, MCSE, BCFP, VCS ? Sr. Storage Engineer ? SunGard
> Availability Services ? 757 N. Eldridge Suite 200, Houston TX 77079 ?
> 281-584-4693
> Keeping People and Information Connected? ?
> http://availability.sungard.com/
> P Think before you print
> CONFIDENTIALITY: This e-mail (including any attachments) may contain
> confidential, proprietary and privileged information, and unauthorized
> disclosure or use is prohibited. If you received this e-mail in
> error,
> please notify the sender and delete this e-mail from your system.
>
>
>
> Justin Piszcz <jpiszcz AT lucidpixels DOT com>
> Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> 03/11/2008 11:48 AM
>
> To
> veritas-bu AT mailman.eng.auburn DOT edu
> cc
>
> Subject
> [Veritas-bu] Anyone restore a 6.0 environment from catalog backup?
>
>
>
>
>
>
> With < 6.0x you bprecover -r and you're pretty much all set;
> however, for
> 6.0 it also writes out a DR file, has anyone done recovery testing
> both
> WITH and WITHOUT the DR file?
>
> Justin.
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted
with it may contain legally privileged, proprietary and/or confidential
information intended solely for the use of the addressee. If you are not the
intended recipient, you are hereby notified that any review, dissemination,
distribution, duplication or other use of this message and/or its attachments
is strictly prohibited. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original message and
its attachments. Thank you.
==============================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20080312/5f7a9344/attachment.html
------------------------------
Message: 14
Date: Wed, 12 Mar 2008 08:51:08 -0400
From: Jared.Seaton AT mylanlabs DOT com
Subject: Re: [Veritas-bu] oracle policy with compression turned on
To: "mark wragge" <mark_t_wragge AT yahoo DOT ie>
Cc: veritas-bu AT mailman.eng.auburn DOT edu,
veritas-bu-bounces AT mailman.eng.auburn DOT edu
Message-ID:
<OF91A98118.830B993D-ON8525740A.0045D4CF-8525740A.0046996A AT MYL DOT
COM>
Content-Type: text/plain; charset="us-ascii"
We get unbelievable compression on our EMC CDL on tapes that are used for
DB backups. I would recommend turning on compression only at the CDL/EDL
level.
An example:
(A 100 GB max virtual tape, with compression enabled on the CDL)
>>From NetBackup Media:
Media ID images kilobytes
AXB009 HCART 00_003_TLD AIX 30 <snip> <snip> 5
2150450784 0 Full 0
>>From CDL Report:
Name,VID,Barcode,Current:Allocation:(MB),Location,Maximum:Capacity:(MB),Used:Size:(MB),Data:Written:(MB),Compression:Ratio,
VirtualTape-01075,1075,AXB009,100352,In Slot:
11,100352,100177,2100050,20:1,
That is 20:1, and I've actually seen it higher on different backups.
Jared M. Seaton
Recovery Administrator
Mylan Inc.
304-554-5926
304-685-1389 (Cell)
"mark wragge" <mark_t_wragge AT yahoo DOT ie>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
03/12/2008 06:34 AM
To
veritas-bu AT mailman.eng.auburn DOT edu
cc
Subject
[Veritas-bu] oracle policy with compression turned on
How does the compression option on an Oracle policy function? Is it the
same as turning on compression on a standard filesystem backup OR is this
a compression feature specific to oracle database backups?
I am considering turning on compression on a Virtual Tape Librayr and on
the oracle policy. Should i just turn it on on the VTL (EMC EDL).
Thanks.
Send instant messages to your online friends
http://uk.messenger.yahoo.com
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
==============================================================================
CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted
with it may contain legally privileged, proprietary and/or confidential
information intended solely for the use of the addressee. If you are not the
intended recipient, you are hereby notified that any review, dissemination,
distribution, duplication or other use of this message and/or its attachments
is strictly prohibited. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original message and
its attachments. Thank you.
==============================================================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20080312/bfe0c034/attachment.htm
------------------------------
Message: 15
Date: Wed, 12 Mar 2008 13:53:33 +0100
From: netbackup AT whelan-consulting.co DOT uk
Subject: [Veritas-bu] Vault failure after upgrade from 6.0MP4 to 6.5.1
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Message-ID:
<6576079.2056261205326413340.JavaMail.servlet@kundenserver>
Content-Type: text/plain; charset=UTF-8
Hello everyone,
Has anyone seen a problem when upgrading a windoze server running NBU 6.0MP4 to
6.5.1. The problem we are seeing appears to be related to the catalog backup
part of a vault schedule. We are getting an error that NBU cannot write to a
log file. The odd thing is the "Program File" portion has a strange character
after the "m". I cannot find a configuration file anywhere that uses this name,
nor can I find an entry in the registry. I have exhausted my limited windoze
knowledge and am hoping someone has seen this or something similar. All
suggestions welcomed.
Regards,
Patrick Whelan
------------------------------
Message: 16
Date: Wed, 12 Mar 2008 14:54:24 +0200
From: "Marianne Van Den Berg" <mvdberg AT stortech.co DOT za>
Subject: Re: [Veritas-bu] NBU 6.0 MP5 - Jobs queued, not going active
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Message-ID:
<6CCC4CB928E64542B366288176DEB0BD9A099B AT sts2.stortech.co DOT za>
Content-Type: text/plain; charset="us-ascii"
Hi
To cut a long story short - NBU 6.0 MP6!
I've received a number of suggestions from list members - stop/start
nbrb, stop/start nbemm, etc. Nothing worked. We spent 3 days with
Symantec 'level 4' engineers on the phone and webex sessions, passed
every 8 hours to the next country, sending gigabytes of logs with NO
solution/action plan from them....
We saw a couple of fixes for nbrb in MP6 README. Support did not believe
that it would solve the problem (they tried for 2 day to convince us
that we have device or device config problems before admitting there
SEEMS to be a problem with nbrb...)
We eventually installed MP6 - backups have been running fine for more
that 24 hours!
Marianne
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
Chris_Millet
Sent: 12 March 2008 06:46
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] NBU 6.0 MP5 - Jobs queued, not going active
Marianne, could you share the resolution to this issue? We also see
this problem on a new environment where we are attempting to do just
standard filesystem backups on several thousand clients. The master
server has plenty of horsepower (16GB, 8 core T2000) but I wonder if
Netbackup keeps getting hung up when juggling that many client jobs.
Our environment we are seeing this in is also v6.0_MP5.
+----------------------------------------------------------------------
|This was sent by cmillet AT qualcomm DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------------------------------
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
End of Veritas-bu Digest, Vol 23, Issue 21
******************************************
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
