07-04-2011 11:52 AM
Hi,
I decided to write this message because I can't find any solutions for my problem.
I have implemented NBAC in required mode on Master Server and client's. It works fine when I run a scheduled backups of files.
But when I try to run an Application Backup - Oracle, I have a problem, it doesn't work.
Below some useful information:
Client: NetBackup-RedHat2.6 7.0
Server: Win2k3R2Ent 32bit NetBackup 7.0
[root@oracle1 ~]# bpnbat -WhoAmI
Name: ADMINISTRATOR
Domain: SERVER_NAME
Issued by: /CN=broker/OU=root@SERVER_NAME/O=vx
Date: Jul 3 19:35:39 2011 GMT
Authentication method: Microsoft Windows
Operation completed successfully.
[root@oracle1 ~]# su - oracle
[oracle@oracle1 ~]$ bpnbat -WhoAmI
Name: ADMINISTRATOR
Domain: SERVER_NAME
Issued by: /CN=broker/OU=root@SERVER_NAME/O=vx
Date: Jul 3 19:36:49 2011 GMT
Authentication method: Microsoft Windows
Operation completed successfully.
[oracle@oracle1 ~]$
Bp.conf on client
SERVER = SERVER_NAME
CLIENT_NAME = oracle1.example.local
AUTHENTICATION_DOMAIN = SERVER_NAME "ADDED AUTOMATICALLY" WINDOWS SERVER_NAME 0
AUTHORIZATION_SERVICE = SERVER_NAME 0
#USE_VXSS = AUTOMATIC
USE_VXSS = REQUIRED
VERBOSE = 5
Oracle backup attemp:
RMAN Script:
run {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
send "NB_ORA_CLIENT=oracle1.example.local";
send "NB_ORA_SERV=SERVER_NAME";
send "NB_ORA_POLICY=oracle";
send "NB_ORA_SCHED=Default-Application-Backup";
backup INCREMENTAL LEVEL=0 FORMAT 'bk_%s_%p_%t' DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
BACKUP
filesperset 20
FORMAT 'al_%s_%p_%t'
ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
BACKUP
FORMAT 'cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
}
Script output:
[oracle@oracle1 ~]$ rman target / catalog rman/12qwas@rvcat @manual.rman
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jul 4 12:52:38 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORADB1 (DBID=2099765450)
connected to recovery catalog database
RMAN> run {
2> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
3> send "NB_ORA_CLIENT=oracle1.example.local";
4> send "NB_ORA_SERV=SERVER_NAME";
5> send "NB_ORA_POLICY=oracle";
6> send "NB_ORA_SCHED=Default-Application-Backup";
7> backup INCREMENTAL LEVEL=0 FORMAT 'bk_%s_%p_%t' DATABASE;
8> sql 'alter system archive log current';
9> RELEASE CHANNEL ch00;
10> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
11> BACKUP
12> filesperset 20
13> FORMAT 'al_%s_%p_%t'
14> ARCHIVELOG ALL DELETE INPUT;
15> RELEASE CHANNEL ch00;
16> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
17> BACKUP
18> FORMAT 'cntrl_%s_%p_%t'
19> CURRENT CONTROLFILE;
20> RELEASE CHANNEL ch00;
21> }
22>
starting full resync of recovery catalog
full resync complete
allocated channel: ch00
channel ch00: sid=132 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
sent command to channel: ch00
sent command to channel: ch00
sent command to channel: ch00
sent command to channel: ch00
Starting backup at 04-JUL-11
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00001 name=/oradata/oradb1/oradb1/system01.dbf
input datafile fno=00003 name=/oradata/oradb1/oradb1/sysaux01.dbf
input datafile fno=00005 name=/oradata/oradb1/oradb1/example01.dbf
input datafile fno=00002 name=/oradata/oradb1/oradb1/undotbs01.dbf
input datafile fno=00004 name=/oradata/oradb1/oradb1/users01.dbf
channel ch00: starting piece 1 at 04-JUL-11
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 07/04/2011 12:53:39
ORA-19506: failed to create sequential file, name="bk_28_1_755614364", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: unexpected message received
Recovery Manager complete.
Attemp of User Backup:
[root@oracle1 ~]# bpbackup /home/oracle
EXIT STATUS 116: VxSS authentication failed
[root@oracle1 ~]# bpnbat -login
Authentication Broker [SERVER_NAME is default]:
Authentication port [0 is default]:
Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd) [WINDOWS is default]:
Domain [SERVER_NAME is default]:
Login Name [Administrator is default]: Administrator
Password:
Operation completed successfully.
[root@oracle1 ~]# bpbackup /home/oracle
[oracle@oracle1 ~]$ bpbackup /home/oracle
EXIT STATUS 116: VxSS authentication failed
[oracle@oracle1 ~]$ bpnbat -login
Authentication Broker [SERVER_NAME is default]:
Authentication port [0 is default]:
Authentication type (NIS, NISPLUS, WINDOWS, vx, unixpwd) [WINDOWS is default]:
Domain [SERVER_NAME is default]:
Login Name [Administrator is default]:
Password:
Operation completed successfully.
[oracle@oracle1 ~]$ bpbackup /home/oracle
Attemp Oracle Backup after bpnbat -login:
[oracle@oracle1 ~]$ rman target / catalog rman/12qwas@rvcat @manual.rman
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jul 4 13:25:52 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ORADB1 (DBID=2099765450)
connected to recovery catalog database
RMAN> run {
2> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
3> send "NB_ORA_CLIENT=oracle1.example.local";
4> send "NB_ORA_SERV=SERVER_NAME";
5> send "NB_ORA_POLICY=oracle";
6> send "NB_ORA_SCHED=Default-Application-Backup";
7> backup INCREMENTAL LEVEL=0 FORMAT 'bk_%s_%p_%t' DATABASE;
8> sql 'alter system archive log current';
9> RELEASE CHANNEL ch00;
10> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
11> BACKUP
12> filesperset 20
13> FORMAT 'al_%s_%p_%t'
14> ARCHIVELOG ALL DELETE INPUT;
15> RELEASE CHANNEL ch00;
16> ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
17> BACKUP
18> FORMAT 'cntrl_%s_%p_%t'
19> CURRENT CONTROLFILE;
20> RELEASE CHANNEL ch00;
21> }
22>
allocated channel: ch00
channel ch00: sid=132 devtype=SBT_TAPE
channel ch00: Veritas NetBackup for Oracle - Release 7.0 (2010010419)
sent command to channel: ch00
sent command to channel: ch00
sent command to channel: ch00
sent command to channel: ch00
Starting backup at 04-JUL-11
channel ch00: starting incremental level 0 datafile backupset
channel ch00: specifying datafile(s) in backupset
input datafile fno=00001 name=/oradata/oradb1/oradb1/system01.dbf
input datafile fno=00003 name=/oradata/oradb1/oradb1/sysaux01.dbf
input datafile fno=00005 name=/oradata/oradb1/oradb1/example01.dbf
input datafile fno=00002 name=/oradata/oradb1/oradb1/undotbs01.dbf
input datafile fno=00004 name=/oradata/oradb1/oradb1/users01.dbf
channel ch00: starting piece 1 at 04-JUL-11
released channel: ch00
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch00 channel at 07/04/2011 13:25:57
ORA-19506: failed to create sequential file, name="bk_30_1_755616354", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSAValidateFeatureId: Failed with error:
Server Status: unexpected message received
Recovery Manager complete.
Messages from BPRD:
17:17:09.619 [4020.3840] <2> logconnections: BPRD ACCEPT FROM 192.168.253.2.13222 TO 192.168.253.253.13724
17:17:09.619 [4020.3840] <2> process_request: setsockopt SO_LINGER on 3596 succeeded.
17:17:09.619 [4020.3840] <2> connected_peer: Connection from host oracle1.example.local, 192.168.253.2, on non-reserved port 13222
17:17:09.619 [4020.3840] <2> nb_is_valid_master_server: checking if oracle1.example.local is a valid server
17:17:09.619 [4020.3840] <2> nb_is_valid_master_server: *** host oracle1.example.local is NOT a valid server
17:17:09.619 [4020.3840] <2> nb_is_valid_master_server: h_name is oracle1.example.local
17:17:09.619 [4020.3840] <2> nb_is_valid_master_server: ip address is 192.168.253.2 (0x2fda8c0)
17:17:09.619 [4020.3840] <2> db_valid_master_server: oracle1.example.local is not a valid server
17:17:09.619 [4020.3840] <2> vnet_check_vxss_server_magic: ../../libvlibs/vnet_vxss_helper.c.494: VxSS magic: 329199 0x000505ef
17:17:09.619 [4020.3840] <2> vnet_check_vxss_server_magic: ../../libvlibs/vnet_vxss_helper.c.495: remote_vxss: 72 0x00000048
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1046: host_cache_size: 200 0x000000c8
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1047: cache_time: 3600 0x00000e10
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1061: host_failed_cache_size: 40 0x00000028
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1062: cache_time: 3600 0x00000e10
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1046: host_cache_size: 200 0x000000c8
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1047: cache_time: 3600 0x00000e10
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1061: host_failed_cache_size: 40 0x00000028
17:17:09.619 [4020.3840] <2> init_cache: ../../libvlibs/vnet_hosts.c.1062: cache_time: 3600 0x00000e10
17:17:09.619 [4020.3840] <2> host_file_match: ../../libvlibs/vnet_vxss.c.2407: match: SERVER_NAME
17:17:09.619 [4020.3840] <2> vnet_get_credential_path: ../../libvlibs/vnet_vxss.c.694: machine credential path: C:\Program Files\Veritas\NetBackup\var\vxss\credentials\SERVER_NAME
17:17:09.619 [4020.3840] <2> VssSetLogLevel: ++++ ENTERING ++++
17:17:09.619 [4020.3840] <4> VssSetLogLevel: (../../libVnbat/vss_auth.cpp,4798): Setting VSSLOG level to 5.
17:17:09.619 [4020.3840] <2> VssSetLogLevel: ---- EXITING ----
17:17:09.619 [4020.3840] <2> vnet_check_vxss_server_magic: ../../libvlibs/vnet_vxss_helper.c.529: Client ignores/server requires VxSS auth: 38 0x0000002617:17:09.619 [4020.3840] <2> process_request: vnet_check_vxss_server_magic() failed: 38
17:17:10.447 [3716.2168] <2> VssCredentialCache::~VssCredentialCache(): ++++ ENTERING ++++
17:17:10.447 [3716.2168] <2> VssCredentialCache::~VssCredentialCache(): (../../libVnbat/vss_credentialcache.cpp,74): Clearing the cache
17:17:10.447 [3716.2168] <2> VssIdentityCleanup: ++++ ENTERING ++++
17:17:10.447 [3716.2168] <2> VssIdentityCleanup: ---- EXITING ----
17:17:10.447 [3716.2168] <2> VssCredentialCache::~VssCredentialCache(): ---- EXITING ----
17:17:11.087 [3284.3704] <2> VssCredentialCache::~VssCredentialCache(): ++++ ENTERING ++++
17:17:11.087 [3284.3704] <2> VssCredentialCache::~VssCredentialCache(): (../../libVnbat/vss_credentialcache.cpp,74): Clearing the cache
17:17:11.087 [3284.3704] <2> VssIdentityCleanup: ++++ ENTERING ++++
17:17:11.087 [3284.3704] <2> VssIdentityCleanup: ---- EXITING ----
17:17:11.087 [3284.3704] <2> VssCredentialCache::~VssCredentialCache(): ---- EXITING ----
17:17:11.634 [4020.3840] <2> VssCredentialCache::~VssCredentialCache(): ++++ ENTERING ++++
17:17:11.634 [4020.3840] <2> VssCredentialCache::~VssCredentialCache(): (../../libVnbat/vss_credentialcache.cpp,74): Clearing the cache
17:17:11.634 [4020.3840] <2> VssIdentityCleanup: ++++ ENTERING ++++
17:17:11.634 [4020.3840] <2> VssIdentityCleanup: ---- EXITING ----
17:17:11.634 [4020.3840] <2> VssCredentialCache::~VssCredentialCache(): ---- EXITING ----
Messages from dbclient on client:
17:19:15.740 [12102] <2> bprd_get_features: Cannot parse product and feature IDs from EXIT STATUS 193
17:19:15.740 [12102] <8> bsa_checkFeatureId: bprd_get_features() failed, retrying
17:19:15.740 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4052: connect in progress: 0 0x00000000
17:19:15.780 [12102] <2> version_connect: ../../libvlibs/vnet_vnetd.c.1834: *actual_version: 5 0x00000005
17:19:15.780 [12102] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
17:19:15.780 [12102] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bprd
17:19:15.986 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4238: in progress connect: 0 0x00000000
17:19:15.986 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4241: connect: async CONNECT FROM 192.168.253.2.14374 TO 192.168.253.253.13724 fd = 23
17:19:15.986 [12102] <2> logconnections: BPRD CONNECT FROM 192.168.253.2.14374 TO 192.168.253.253.13724
17:19:15.987 [12102] <2> vnet_check_vxss_client_magic_with_info: ../../libvlibs/vnet_vxss_helper.c.840: VxSS not supported: 0 0x00000000
17:19:16.378 [12102] <2> bprd_get_features: Cannot parse product and feature IDs from EXIT STATUS 193
17:19:16.378 [12102] <8> bsa_checkFeatureId: bprd_get_features() failed, retrying
17:19:16.378 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4052: connect in progress: 0 0x00000000
17:19:16.416 [12102] <2> version_connect: ../../libvlibs/vnet_vnetd.c.1834: *actual_version: 5 0x00000005
17:19:16.416 [12102] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2054: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
17:19:16.416 [12102] <2> vnet_vnetd_service_socket: ../../libvlibs/vnet_vnetd.c.2068: service: bprd
17:19:16.533 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4238: in progress connect: 0 0x00000000
17:19:16.533 [12102] <2> vnet_async_connect: ../../libvlibs/vnet_vnetd.c.4241: connect: async CONNECT FROM 192.168.253.2.13222 TO 192.168.253.253.13724 fd = 23
17:19:16.533 [12102] <2> logconnections: BPRD CONNECT FROM 192.168.253.2.13222 TO 192.168.253.253.13724
17:19:16.533 [12102] <2> vnet_check_vxss_client_magic_with_info: ../../libvlibs/vnet_vxss_helper.c.840: VxSS not supported: 0 0x00000000
17:19:16.925 [12102] <2> bprd_get_features: Cannot parse product and feature IDs from EXIT STATUS 193
17:19:16.925 [12102] <16> bsa_checkFeatureId: unable to check if feature <36> is licensed
17:19:16.925 [12102] <16> bsa_checkFeatureId: Server exit status = 43: unexpected message received
17:19:16.925 [12102] <2> xbsa_ProcessError: INF - entering
17:19:16.925 [12102] <2> xbsa_ProcessError: INF - leaving
17:19:16.925 [12102] <16> xbsa_ValidateFeatureId: ERR - VxBSAValidateFeatureId: Failed with error:
Server Status: unexpected message received
17:19:16.925 [12102] <2> xbsa_ValidateFeatureId: INF - leaving (3)
I'm confused.
Anybody have any ideas?
Leonid
Solved! Go to Solution.
07-04-2011 10:38 PM
Hi,
According to the Symantec netbackup 7.0 additional operational notes manual does NBAC not support the netbackup database agents, please lookup page 25.
Where it says
The use of NetBackup database agents with NBAC was not implemented in this NetBackup release.
http://www.symantec.com/business/support/index?page=content&id=TECH76770
I hope this helps.
/Oddy
07-04-2011 12:16 PM
First question, if you turn off NBAC does it work?
Please post your policy with bppllist POLICYNAME -U
Also check this note http://www.symantec.com/docs/TECH42956 (I know its old, but just check if its not ticked for some strange reason)
07-04-2011 12:27 PM
First question, if you turn off NBAC does it work? - YES
In this case, a solution provided by technote dont work.
C:\Documents and Settings\Administrator>bppllist oracle -U
------------------------------------------------------------
Policy Name: oracle
Policy Type: Oracle
Active: yes
Effective date: 07/02/2011 00:58:49
Block Incremental: no
Mult. Data Streams: no
Client Encrypt: no
Checkpoint: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR info: no
Residence: d1
Volume Pool: NetBackup
Server Group: *ANY*
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Granular Restore Info: no
Ignore Client Direct: no
HW/OS/Client: Linux RedHat2.6 oracle1.example.local
Include: /usr/openv/netbackup/bin/hot_database_backup.sh
Schedule: Default-Application-Backup
Type: Application Backup
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 3 (1 month)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
niedziela 00:00:00 --> niedziela 24:00:00
poniedzia 00:00:00 --> poniedzia 24:00:00
wtorek 00:00:00 --> wtorek 24:00:00
sroda 00:00:00 --> sroda 24:00:00
czwartek 00:00:00 --> czwartek 24:00:00
piatek 00:00:00 --> piatek 24:00:00
sobota 00:00:00 --> sobota 24:00:00
Schedule: F
Type: Automatic Full Backup
Frequency: every 7 days
Maximum MPX: 1
Synthetic: 0
PFI Recovery: 0
Retention Level: 1 (2 weeks)
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
07-04-2011 10:38 PM
Hi,
According to the Symantec netbackup 7.0 additional operational notes manual does NBAC not support the netbackup database agents, please lookup page 25.
Where it says
The use of NetBackup database agents with NBAC was not implemented in this NetBackup release.
http://www.symantec.com/business/support/index?page=content&id=TECH76770
I hope this helps.
/Oddy
07-05-2011 03:58 AM
You learn something everyday, thanks Oddy.
07-05-2011 04:33 AM
Oddy,
Thank you very much!!!
I'm surprised that not placed in Security Guide.
Regard's
Leonid
07-05-2011 04:42 AM
Agree, that information is well hidden. It should be in the security guide.
/Oddy
07-20-2011 05:00 AM
Does Netbackup 7.0.1 or 7.1 release supports the Netbackup Database agents through NBAC????
07-22-2011 12:06 AM
I do not think it is implemented in netbackup 7.0.1.
But there is a note in the Netbackup 7.1 release notes on page 16 where it says,
The Authorization Service’s Database is now integrated with the NetBackup databases. And with this feature comes the addition of the NBAZDB database.
Link to the release notes to netbackup 7.1,
http://www.symantec.com/business/support/index?page=content&id=DOC3643
I hope this helps.
/Oddy