I will be out of the office from April 2nd through April 7th.
>>> veritas-bu 04/02/09 08:27 >>>
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. Exchange 2007 fails status 5 for NBU 6.5.3 (Todd Jackxon)
2. Re: Vaulting from disk storage groups (Peters, Devon C)
3. Re: (no subject) (Harpreet SINGH)
4. cannot add new tapes into volume in media server (footsoldier)
5. Re: Vaulting from disk storage groups (Scott Jacobson)
6. Re: cannot add new tapes into volume in media server (Patrick)
7. NBU 6.5.3.1 Drive limit (Clooney, David)
8. BMR (mohamed fathy)
9. BMR (mohamed fathy)
----------------------------------------------------------------------
Message: 1
Date: Wed, 1 Apr 2009 17:46:40 -0400
From: Todd Jackxon <netbackup.info AT gmail DOT com>
Subject: [Veritas-bu] Exchange 2007 fails status 5 for NBU 6.5.3
To: veritas-bu AT mailman.eng.auburn DOT edu
Message-ID:
<f7e0214e0904011446ra282cbbi45915b6d98077141 AT mail.gmail DOT com>
Content-Type: text/plain; charset="windows-1252"
Hello All,
This problem is really beating me. We have Netbackup 6.5.3 on a Windows
Master
and the Exchange 2007 client server. I am using the virtual name
(shortname)
to back
up the client. I can restore the client in one location but in two other
locations the job fails
with a status 5. All 3 locations are close to the same setup. I am
attaching
a tar log of a failed client.
The Exchange Admins are setting up the RSG correctly.
It appears that some data is restoring but it will not pull the Logs. It
fails before restoring the logs.
A few facts
1- using virtual name of cluster to back up Exchange data
2- Using an authorized domain administrative and Exchange administrative
user for NBU service.
NOTE: Just tested that 1st location and it now fails. The time it
succeeded
we restored SG01 .. all other attempts have
been to SG02 or SG03 .. strange
Thanks
Todd
*Detailed status info from some failure jobs*
==============================
* You must restore the logs from the last backup set for Microsoft
Information Store:\xxx01-SG03\ by itself for proper recovery.
*(tar did not find all the files to be restored(185)); restore time
00:03:46
* unable to create object for restore: Microsoft Information
Store:\xxx01-SG03\Log files_1238392377 (BEDS 0xE000032F: The restore
failed
because a connection could not be made to the Microsoft Extensible
Storage
Engine (ESE) to load the restore environment. Make sure that there are
no
other restore operations in process, and then try this operation again.)
*unable to create object for restore: Microsoft Information
Store:\xxx01-SG03\FRD01-DB03 (BEDS 0xE000FF00: Unable to restore some
Microsoft Exchange components because one or more of the databases are
currently mounted or because the Recovery Storage Group is not properly
configured. Use the Exchange System Manager to check the configuration
of
the Recovery Stora)
=====================================================================================
==================================================================================================
*TAR LOG*
1:12:51.986 PM: [6524.9500] <4> tar_base::keepaliveThread: INF -
keepalive
thread is active with an interval of 30 seconds
1:14:29.330 PM: [6524.8984] <2> ov_log::V_GlobalLogEx: ERR -
beds_ese_access::V_OpenForWrite() FS_EXTENDED_ERROR on FS_CreateObj()
Result:0xE000FF00 Action:0x1 Error_id:0x3EAD
1:14:29.330 PM: [6524.8984] <2> tar_base::V_vTarMsgW: ERR - unable to
create
object for restore: Microsoft Information Store:\xxx01-SG03\xxx01-DB03
(BEDS
0xE000FF00: Unable to restore some Microsoft Exchange components because
one
or more of the databases are currently mounted or because the Recovery
Storage Group is not properly configured. Use the Exchange System
Manager to
check the configuration of the Recovery Stora)
1:14:53.111 PM: [6524.8984] <2> ov_log::V_GlobalLogEx: ERR -
beds_ese_access::V_OpenForWrite():FS_CreateObj() Failed! (0xE000032F:The
restore failed because a connection could not be made to the Microsoft
Extensible Storage Engine (ESE) to load the restore environment.
Make sure that there are no other restore operations in process, and
then
try this operation again.
)
1:14:53.111 PM: [6524.8984] <2> tar_base::V_vTarMsgW: ERR - unable to
create
object for restore: Microsoft Information Store:\xxxx01-SG03\Log
files_1238502346 (BEDS 0xE000032F: The restore failed because a
connection
could not be made to the Microsoft Extensible Storage Engine (ESE) to
load
the restore environment.
Make sure that there are no other restore operations in process, and
then
try this operation again.
)
1:14:59.174 PM: [6524.8984] <2> tar_base::V_vTarMsgW: INF - Commit is
set,
but no log files are included in this restore request. Log files are
required to perform Exchange database recovery.
1:14:59.174 PM: [6524.8984] <2> tar_base::V_vTarMsgW: WRN - You must
restore
the logs from the last backup set for Microsoft Information
Store:\xxx01-SG03\ by itself for proper recovery.
1:14:59.174 PM: [6524.8984] <2> tar_base::backup_finish: TAR - restore:
4
files
1:14:59.174 PM: [6524.8984] <2> tar_base::backup_finish: TAR - restore:
file
data: 620538040 bytes
1:14:59.174 PM: [6524.8984] <2> tar_base::backup_finish: TAR - restore:
image data: 620544512 bytes
1:14:59.174 PM: [6524.8984] <2> tar_base::backup_finish: TAR - restore:
elapsed time: 128 secs 4848004 bps
1:14:59.174 PM: [6524.8984] <8> tar_restore::processStateEOT: WRN -
processStateEOT before keepalive
1:14:59.174 PM: [6524.9500] <4> tar_base::keepaliveThread: INF -
keepalive
thread terminating (reason: WAIT_OBJECT_0)
1:14:59.174 PM: [6524.8984] <4> tar_base::stopKeepaliveThread: INF -
keepalive thread has exited. (reason: WAIT_OBJECT_0)
1:14:59.174 PM: [6524.8984] <2> tar_base::V_Close:
1:14:59.174 PM: [6524.8924] <2> ov_log::V_GlobalLog: INF - BEDS_Term()
Enter
InitFlags:0x1
1:14:59.299 PM: [6524.8984] <4> OVStopCmd: INF - EXIT - status = 0
1:14:59.299 PM: [6524.8984] <4> OVShutdown: INF - Finished process
1:14:59.299 PM: [6524.8984] <4> WinMain: INF - Exiting C:\Program
Files\VERITAS\NetBackup\bin\tar32.exe
1:15:01.299 PM: [6524.8984] <4> ov_log::OVClose: INF - Closing log file:
C:\Program Files\VERITAS\NetBackup\logs\TAR\033109.LOG
6:03:24.799 PM: [9876.8408] <4> ov_log::OVInit: INF - Starting log file:
C:\Program Files\VERITAS\NetBackup\logs\TAR\033109.LOG
6:03:24.799 PM: [9876.8408] <4> ov_log::OVInit: GENERAL Log Level: 0
6:03:24.799 PM: [9876.8408] <4> ov_log::OVInit: TCP Log Level: 0
6:03:24.799 PM: [9876.8408] <4> ov_log::OVInit: INF - the log mutex: 764
TAR NetBackup TAR 6.5GA [Oct 30 2008]
Copyright 1993 - 2007 VERITAS Software Corporation
All Rights Reserved.
6:03:24.799 PM: [9876.8408] <2> WinMain: DAT - _pgmptr = 'C:\Program
Files\VERITAS\NetBackup\bin\tar32.exe'
6:03:24.799 PM: [9876.8408] <2> WinMain: DAT - lpCmdLine = '-x -v -Y -p
-P
-I 1238536976 -U 16 -k -Q -J clnt_lc_messages=en -J clnt_lc_time=en -J
clnt_lc_ctype=en -J clnt_lc_collate=en -J clnt_lc_numeric=en -J
restoreid=182529.001 -J job_total=1 -J client=xxxxxxxxxxxx -J
requesting_client=xxxxxxxxxxxx -J browse_client=xxxxx -J commit=1 -J
dir_byte_count=7 -J temp_dir=/C/temp -J mount_database=1 -J
backup_time=1238502346 -L
/D/Program??
Files/VERITAS/NetBackup/logs/user_ops/c-a_t000/logs/NBWIN007 -f
- '
6:03:24.799 PM: [9876.8408] <2> date_debug: DAT - timezone: Eastern
Standard
Time, offset=18000, dst: Eastern Daylight Time
6:03:24.799 PM: [9876.8408] <2> date_debug: DAT - current time:
1238537004,
3/31/2009 6:03:24 PM
6:03:24.799 PM: [9876.8408] <2> date_debug: DAT - 01/01/94 UCT:
757382400,
12/31/1993 8:00:00 PM
6:03:24.799 PM: [9876.8408] <2> date_debug: DAT - 07/01/94 UCT:
773020800,
6/30/1994 8:00:00 PM
6:03:25.783 PM: [9876.8408] <2> WinMain: DAT - standard input handle =
736
6:03:25.783 PM: [9876.8408] <2> WinMain: DAT - standard output handle =
732
6:03:25.783 PM: [9876.8408] <2> WinMain: DAT - standard error handle =
728
6:03:25.783 PM: [9876.8408] <4> backup_list: INF - creating restore
object
6:03:25.783 PM: [9876.8408] <4> tar_restore_tfi::create: INF -
dwJobData:
ffffffff
6:03:25.783 PM: [9876.8408] <4> tar_restore_tfi::create: INF - dwJob:
ffffffff
6:03:25.783 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - restore privileges enabled, previous = 0
6:03:25.783 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - backup privileges enabled, previous = 0
6:03:25.783 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - security privileges enabled, previous = 0
6:03:25.783 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - create token privileges enabled, previous = 0
6:03:25.783 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - take ownership privileges enabled, previous = 0
6:03:25.893 PM: [9876.8408] <4> OVGetRestoreToken: INF - successfully
wrote
restore information to named pipe
6:03:25.893 PM: [9876.8408] <4>
base_restore::tfs_enable_restore_privileges:
INF - no access token: server directed restore
6:03:25.924 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - BEDS_Init()
Enter
InitFlags:0x0
6:03:25.955 PM: [9876.9116] <2> ov_log::V_GlobalLog: WRN - BEDS_Init()
Microsoft Exchange Messaging API and Collaboration Data Objects package
is
required for Mailbox level backup and restore. This package can be found
on
the Microsoft Web Site.
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: C:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: D:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: E:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: F:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: Q:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: R:
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: Microsoft Terminal Services
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: Microsoft Windows Network
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: Web Client Network
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: \\xxxxxail01\Microsoft <file://xxxxxail01/Microsoft>
Exchange
Mailboxes
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: \\xxxxxxail01\Microsoft <file://xxxxxxail01/Microsoft>
Exchange
Public Folders
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: Shadow?Copy?Components
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - DumpDleInfo()
DLE
Device Name: \\xxxxxx01\Microsoft <file://xxxxxx01/Microsoft>
Information
Store
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxx\Microsoft<file://xxxxxx/Microsoft>Information
Store\FRD01-SG01
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxil01\Microsoft<file://xxxxxxil01/Microsoft>Information
Store\FRD01-SG02
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxil01\Microsoft<file://xxxxxxil01/Microsoft>Information
Store\FRD01-SG03
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxxil01\Microsoft<file://xxxxxxxil01/Microsoft>Information
Store\FRD01-SG04
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxxxl01\Microsoft<file://xxxxxxxxl01/Microsoft>Information
Store\FRD01-SG05
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\fxxxxxxx1\Microsoft<file://fxxxxxxx1/Microsoft>Information
Store\FRD01-SG06
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\fxxxxxxxxx01\Microsoft<file://fxxxxxxxxx01/Microsoft>Information
Store\FRD01-SG07
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxxxxx\Microsoft<file://xxxxxxxxxx/Microsoft>Information
Store\FRD01-SG08
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxx\Microsoft<file://xxxxxx/Microsoft>Information
Store\FRD01-SG09
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxxx1\Microsoft<file://xxxxxxxx1/Microsoft>Information
Store\FRD01-SG10
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxx1\Microsoft<file://xxxxxxx1/Microsoft>Information
Store\FRD01-SG11
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\fxxxxxxxl01\Microsoft<file://fxxxxxxxl01/Microsoft>Information
Store\FRD01-SG12
6:03:34.049 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF -
DumpChildDleInfo() Child DLE Device Name:
\\xxxxxxxx01\Microsoft<file://xxxxxxxx01/Microsoft>Information
Store\Recovery Storage Group
6:03:34.893 PM: [9876.8408] <4> windows_restore::V_Initialize: INF -
Exchange Restore - Disabling Rename If Exists.
6:03:34.893 PM: [9876.5052] <4> tar_base::keepaliveThread: INF -
keepalive
thread is active with an interval of 30 seconds
6:05:14.408 PM: [9876.8408] <2> ov_log::V_GlobalLogEx: ERR -
beds_ese_access::V_OpenForWrite() FS_EXTENDED_ERROR on FS_CreateObj()
Result:0xE000FF00 Action:0x1 Error_id:0x3EAD
6:05:14.408 PM: [9876.8408] <2> tar_base::V_vTarMsgW: ERR - unable to
create
object for restore: Microsoft Information Store:\xxxx01-SG03\FRD01-DB03
(BEDS 0xE000FF00: Unable to restore some Microsoft Exchange components
because one or more of the databases are currently mounted or because
the
Recovery Storage Group is not properly configured. Use the Exchange
System
Manager to check the configuration of the Recovery Stora)
6:05:38.330 PM: [9876.8408] <2> ov_log::V_GlobalLogEx: ERR -
beds_ese_access::V_OpenForWrite():FS_CreateObj() Failed! (0xE000032F:The
restore failed because a connection could not be made to the Microsoft
Extensible Storage Engine (ESE) to load the restore environment.
Make sure that there are no other restore operations in process, and
then
try this operation again.
)
6:05:38.330 PM: [9876.8408] <2> tar_base::V_vTarMsgW: ERR - unable to
create
object for restore: Microsoft Information Store:\xxxx01-SG03\Log
files_1238502346 (BEDS 0xE000032F: The restore failed because a
connection
could not be made to the Microsoft Extensible Storage Engine (ESE) to
load
the restore environment.
Make sure that there are no other restore operations in process, and
then
try this operation again.
)
6:05:44.408 PM: [9876.8408] <2> tar_base::V_vTarMsgW: INF - Commit is
set,
but no log files are included in this restore request. Log files are
required to perform Exchange database recovery.
6:05:44.408 PM: [9876.8408] <2> tar_base::V_vTarMsgW: WRN - You must
restore
the logs from the last backup set for Microsoft Information
Store:\xxxx01-SG03\ by itself for proper recovery.
6:05:44.408 PM: [9876.8408] <2> tar_base::backup_finish: TAR - restore:
4
files
6:05:44.408 PM: [9876.8408] <2> tar_base::backup_finish: TAR - restore:
file
data: 620538040 bytes
6:05:44.408 PM: [9876.8408] <2> tar_base::backup_finish: TAR - restore:
image data: 620544512 bytes
6:05:44.408 PM: [9876.8408] <2> tar_base::backup_finish: TAR - restore:
elapsed time: 130 secs 4773419 bps
6:05:44.408 PM: [9876.8408] <8> tar_restore::processStateEOT: WRN -
processStateEOT before keepalive
6:05:44.408 PM: [9876.5052] <4> tar_base::keepaliveThread: INF -
keepalive
thread terminating (reason: WAIT_OBJECT_0)
6:05:44.408 PM: [9876.8408] <4> tar_base::stopKeepaliveThread: INF -
keepalive thread has exited. (reason: WAIT_OBJECT_0)
6:05:44.408 PM: [9876.8408] <2> tar_base::V_Close:
6:05:44.408 PM: [9876.9116] <2> ov_log::V_GlobalLog: INF - BEDS_Term()
Enter
InitFlags:0x1
6:05:44.533 PM: [9876.8408] <4> OVStopCmd: INF - EXIT - status = 0
6:05:44.533 PM: [9876.8408] <4> OVShutdown: INF - Finished process
6:05:44.533 PM: [9876.8408] <4> WinMain: INF - Exiting C:\Program
Files\VERITAS\NetBackup\bin\tar32.exe
6:05:46.533 PM: [9876.8408] <4> ov_log::OVClose: INF - Closing log file:
C:\Program Files\VERITAS\NetBackup\logs\TAR\033109.LOG
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090401/8aff28e8/attachment-0001.htm
------------------------------
Message: 2
Date: Wed, 1 Apr 2009 16:55:43 -0700
From: "Peters, Devon C" <Peters.Devon AT con-way DOT com>
Subject: Re: [Veritas-bu] Vaulting from disk storage groups
To: "veritas-bu AT mailman.eng.auburn DOT edu"
<veritas-bu AT mailman.eng.auburn DOT edu>
Message-ID:
<11893698C5A8C84EA0B5484DEB54E375014AFCCFAF AT DCXPRCL018.cnf.prod.cnf
DOT com>
Content-Type: text/plain; charset="us-ascii"
You can't use storage unit groups as the source, and I don't think Vault
will let you use a storage unit group as a duplication destination - you
wouldn't want that anyway since the duplications would probably end up
going over the network.
You'll want to setup the vault profile to choose all the backup images
you want to duplicate (however you decide to choose them). Then in the
duplication tab use the "advanced configuration" and add an entry for
each media server - just be sure that the destination for each server is
a storage unit on that same media server.
-devon
------------------------------
Date: Sat, 28 Mar 2009 20:06:51 -0400
From: jketter <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] Vaulting from disk storage groups
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Message-ID: <1238285211.m2f.302465 AT www.backupcentral DOT com>
Hi Guys,
Can someone please explain the best way to vault from disk storage
units?
I have got a 5 media servers enabled with the advanced disk option, all
with local disk, contained within a storage unit group.
I have also got the media servers connect to multiple tape drives with
SSO.
The backup images will be spread over all storage units.
My question is about vaulting from the disk storage unit to tape.
When configuring the vault profile to vault to tape, should I point the
source at the disk storage unit (as you cant point directly to Storage
unit group), and the destination to the tape storage group?
Or, point the vault to all storage units, and destination to individual
tape drives connected to the media servers?
I am running 6.5.3.
Any help appreciated
Jai
+----------------------------------------------------------------------
|This was sent by
georgeandsylvia AT iinet.net DOT au<mailto:georgeandsylvia AT iinet.net DOT au>
via
Backup Central.
|Forward SPAM to
abuse AT backupcentral DOT com<mailto:abuse AT backupcentral DOT com>.
+----------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090401/f335fd72/attachment-0001.htm
------------------------------
Message: 3
Date: Thu, 2 Apr 2009 08:16:02 +0800
From: Harpreet SINGH <harpreet_singh AT ctl.creative DOT com>
Subject: Re: [Veritas-bu] (no subject)
To: "Daniel Otto" <dan_otto AT symantec DOT com>
Cc: veritas-bu-bounces AT mailman.eng.auburn DOT edu,
veritas-bu AT mailman.eng.auburn DOT edu, "McDonald II, James
F."
<JAMES.F.MCDONALD.II AT saic DOT com>
Message-ID:
<OFF2CC9B75.219C94E1-ON4825758C.00013A7E-4825758C.000177F6 AT
ctl.creative DOT com>
Content-Type: text/plain; charset=US-ASCII
Dear Daniel,
I have 3 Redhat 5 clients and my master/media server is on Redhat 2.4.6.
I had the same issue. Then Support has recommended for below action.
From
that day it is working fine for me.
http://seer.entsupport.symantec.com/docs/290148.htm
chcon -t textrel_shlib_t /usr/openv/lib/libnbmangle.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBXCommon.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBX.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxPBXVxSS.so
chcon -t textrel_shlib_t /usr/openv/lib/libvxVxSSIOP.so
chcon -t textrel_shlib_t /usr/openv/lib/libnbservice.so
=======
You can try this one and let me know.
With Warm Regards
=-=-=-=-=-=-=-=-=-=-=-=-=-
Harpreet Singh Chana
Phone : (O) 6895 - 4326
Fax : (O) 6895 - 4991
=-=-=-=-=-=-=-=-=-=-=-=-=-
Notice
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying or distribution of the message, or
any action taken by you in reliance on it, is prohibited and may be
unlawful. If you have received this message in error, please delete it
and contact the sender immediately. Thank you.
"Daniel Otto"
<dan_otto@symante
c.com>
To
Sent by: "McDonald II, James F."
veritas-bu-bounce <JAMES.F.MCDONALD.II AT saic DOT com>,
s AT mailman.eng DOT aub
<veritas-bu AT mailman.eng.auburn DOT edu>
urn.edu
cc
Subject
04/01/2009 09:25 Re: [Veritas-bu] (no subject)
PM
See if this helps-
STATUS CODE 58: "Can't connect to client" Troubleshooting procedures for
Status 58 errors.
http://support.veritas.com/docs/321172
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of McDonald
II, James F.
Sent: Wednesday, April 01, 2009 7:34 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] (no subject)
We are trying to get Red Hat Enterprise Linux 5.0 and NBU 6.5 to
connect/talk. We have installed a NBU Linux client from the Symantec
download site and xinetd, but the two (Linux & NBU) do not see each
other.
Do you need to configure the client service a certain way on the Linux
box,
other than the typical, straight-forward install? Since xinetd is for
on-demand services, is there a config file that needs to be altered to
run
correctly and start the NBU client? Does the NBU 6.5 Linux client even
support REHL 5.0?
I have seven Linux boxes I need to connect to NBU, and they are used
daily
by developers, so they are the most important ones. I created the
backup
policies on my backup server (running W2K3 server), but when I try to
specify the folders/directories to be backed up NBU is unable to connect
to
the Linux box._______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
ForwardSourceID:NT000D0FE2
------------------------------
Message: 4
Date: Wed, 01 Apr 2009 20:17:37 -0400
From: footsoldier <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] cannot add new tapes into volume in media
server
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Message-ID: <1238631457.m2f.302897 AT www.backupcentral DOT com>
hi Patrick,
yes i am using a 60-slot HP MSL library..i am just trying to add 4 or 5
tapes with new volume labels...running "Vmupdate -rt -tld -rn 1 "command
from the command line..i will get this error :
Update failed: could not add new media ID '9UD034' into slot 50
Insert media failed:
network protocol error (39)
One last time baby...
Unable to obtain database handle: Could not connect to vmd on host
stmes11bkup (70)
...the vmd daemon will then hang, and i have to restart my Netbackup
services..unless i delete 5 or more existing volumes from my database,
this operation will always hit this error...
+----------------------------------------------------------------------
|This was sent by garrick_ck AT yahoo.com DOT sg via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
------------------------------
Message: 5
Date: Wed, 01 Apr 2009 19:41:16 -0600
From: "Scott Jacobson" <SJACOBSO AT novell DOT com>
Subject: Re: [Veritas-bu] Vaulting from disk storage groups
To: "Devon C Peters" <Peters.Devon AT con-way DOT com>,
"veritas-bu AT mailman.eng.auburn DOT edu"
<veritas-bu AT mailman.eng.auburn DOT edu>
Message-ID: <49D3C35C0200003E00089FDF AT lucius.provo.novell DOT com>
Content-Type: text/plain; charset="iso-8859-15"
Devon,
In 6.5.1+, you can use and define a storage unit group as the source -
then within the Duplication Tab, selecting Advanced configuration,
you'll need to define each storage unit source with unique read/write
drive configuration and volume pool information. If the destination
media sever(s) are local (LAN), no problem. If not local, this is when
SSO and remote media/disk storage unit configuration options can
possibly help with your issue.
Scott
>>> "Peters, Devon C" <Peters.Devon AT con-way DOT com> 4/1/2009 5:55 PM >>>
You can*t use storage unit groups as the source, and I don*t think
Vault will let you use a storage unit group as a duplication destination
* you wouldn*t want that anyway since the duplications would probably
end up going over the network.
You*ll want to setup the vault profile to choose all the backup images
you want to duplicate (however you decide to choose them). Then in the
duplication tab use the *advanced configuration* and add an entry for
each media server - just be sure that the destination for each server is
a storage unit on that same media server.
-devon
------------------------------
Date: Sat, 28 Mar 2009 20:06:51 -0400
From: jketter <netbackup-forum AT backupcentral DOT com>
Subject: [Veritas-bu] Vaulting from disk storage groups
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Message-ID: <1238285211.m2f.302465 AT www.backupcentral DOT com>
Hi Guys,
Can someone please explain the best way to vault from disk storage
units?
I have got a 5 media servers enabled with the advanced disk option, all
with local disk, contained within a storage unit group.
I have also got the media servers connect to multiple tape drives with
SSO.
The backup images will be spread over all storage units.
My question is about vaulting from the disk storage unit to tape.
When configuring the vault profile to vault to tape, should I point the
source at the disk storage unit (as you cant point directly to Storage
unit group), and the destination to the tape storage group?
Or, point the vault to all storage units, and destination to individual
tape drives connected to the media servers?
I am running 6.5.3.
Any help appreciated
Jai
+----------------------------------------------------------------------
|This was sent by georgeandsylvia AT iinet.net DOT au via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090401/56fb8237/attachment-0001.htm
------------------------------
Message: 6
Date: Thu, 2 Apr 2009 10:49:23 +0100
From: "Patrick" <netbackup AT whelan-consulting.co DOT uk>
Subject: Re: [Veritas-bu] cannot add new tapes into volume in media
server
To: <VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU>
Message-ID:
<!&!AAAAAAAAAAAYAAAAAAAAAPXpe8FycJRGunX7KLBpRMDCgAAAEAAAADytuEsM5YtBsOwya3KRu6sBAAAAAA==@whelan-consulting.co.uk>
Content-Type: text/plain; charset="iso-8859-1"
Why do you not use the GUI? When you say "delete 5 or more..." what do
you
mean by delete? Are these tapes empty? If so, why do you need to add
more,
if not how can you delete them?
Regards,
?
Patrick Whelan
VERITAS Certified NetBackup Support Engineer for UNIX.
VERITAS Certified NetBackup Support Engineer for Windows.
netbackup AT whelan-consulting.co DOT uk
-----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
footsoldier
Sent: 02 April 2009 01:18
To: VERITAS-BU AT MAILMAN.ENG.AUBURN DOT EDU
Subject: [Veritas-bu] cannot add new tapes into volume in media server
hi Patrick,
yes i am using a 60-slot HP MSL library..i am just trying to add 4 or 5
tapes with new volume labels...running "Vmupdate -rt -tld -rn 1 "command
from the command line..i will get this error :
Update failed: could not add new media ID '9UD034' into slot 50
Insert media failed:
network protocol error (39)
One last time baby...
Unable to obtain database handle: Could not connect to vmd on host
stmes11bkup (70)
...the vmd daemon will then hang, and i have to restart my Netbackup
services..unless i delete 5 or more existing volumes from my database,
this
operation will always hit this error...
+----------------------------------------------------------------------
|This was sent by garrick_ck AT yahoo.com DOT sg 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
------------------------------
Message: 7
Date: Thu, 02 Apr 2009 12:48:59 +0100
From: "Clooney, David" <david.clooney AT bankofamerica DOT com>
Subject: [Veritas-bu] NBU 6.5.3.1 Drive limit
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID:
<94462EC4A32D6C4DB34699EF631CC78C04BF9BDD AT ex2k.bankofamerica DOT com>
Content-Type: text/plain; charset="us-ascii"
Hi All
Anyone aware of NBU 6.5.3.1 having a limit on the number of drives in an
environment.
When trying to add more than 200, we are getting
Already configured the max number drives for this version
Adding this drive would exceed the maximum allowed
Surely 200 is pretty minimal, or possibly a licensing issue?
Regards
David Clooney
Enterprise Storage Services
Notice to recipient:
The information in this internet e-mail and any attachments is
confidential and may be privileged. It is intended solely for the
addressee. If you are not the intended addressee please notify the
sender immediately by telephone. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted to
be taken in reliance on it, is prohibited and may be unlawful.
When addressed to external clients any opinions or advice contained in
this internet e-mail are subject to the terms and conditions expressed
in any applicable governing terms of business or client engagement
letter issued by the pertinent Bank of America group entity.
If this email originates from the U.K. please note that Bank of America,
N.A., London Branch, Banc of America Securities Limited and MBNA Europe
Bank Limited are authorised and regulated by the Financial Services
Authority. For all U.K. corporate disclosures, please refer to
www.bankofamerica.com/ukcompanies
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090402/703122c7/attachment-0001.htm
------------------------------
Message: 8
Date: Thu, 2 Apr 2009 05:24:55 -0700 (PDT)
From: mohamed fathy <esk_elgamal AT yahoo DOT com>
Subject: [Veritas-bu] BMR
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <226987.97063.qm AT web110705.mail.gq1.yahoo DOT com>
Content-Type: text/plain; charset="us-ascii"
Hello All
after creating SRT and configure apolicy for the client ,how can i take
afull image of solaris sparc machine ,and can i restore the image on
anew hardware or not ,could any one please tell me ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090402/2e1253a7/attachment-0001.htm
------------------------------
Message: 9
Date: Thu, 2 Apr 2009 05:27:04 -0700 (PDT)
From: mohamed fathy <esk_elgamal AT yahoo DOT com>
Subject: [Veritas-bu] BMR
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID: <64597.89130.qm AT web110702.mail.gq1.yahoo DOT com>
Content-Type: text/plain; charset="us-ascii"
Hello All
after creating SRT and configure apolicy for the client ,how can i take
afull image of solaris sparc machine ,and can i restore the image on
anew hardware or not ,could any one please tell me ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20090402/ba2e31fb/attachment.htm
------------------------------
_______________________________________________
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 36, Issue 3
*****************************************
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
