Netbackup in ldoms
Hello:
As I understand A guest ldom cannot see a tape drive in any way so a Master/Media server from Veritas Netbackup is not possible at least for now.
But I'm wondering if Netbackup is installed in the Control domain or an I/O Domain in a SF T2000 will be ok? could this be considered something officially supported?
Veritas docs (version 6 OS compatibility Matrix from october 16, 2007, and HCL ) do not mention anything aboud Logical domains, only solaris 10. and we need something really officially supported as part of the solution.
Any input on this one?
t5240-s10u6:/opt/SUNWldm/bin# ./ldm list-devices -a io
IO
DEVICE PSEUDONYM BOUND OPTIONS
pci@400 pci_0 yes
pci@500 pci_1 yes
t5240-s10u6:/opt/SUNWldm/bin# cat /etc/path_to_inst | grep pci@500
"/pci@500" 1 "px"
"/pci@500/pci@0" 6 "pxb_plx"
"/pci@500/pci@0/pci@9" 8 "pxb_plx"
"/pci@500/pci@0/pci@9/SUNW,qlc@0" 1 "qlc"
"/pci@500/pci@0/pci@9/SUNW,qlc@0/fp@0,0" 0 "fp"
"/pci@500/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ses@w217800c0ffd5448e,0" 0 "ses"
"/pci@500/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w207000c0ffd5448e,a" 2 "ssd"
"/pci@500/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ssd@w207000c0ffd5448e,5" 0 "ssd"
"/pci@500/pci@0/pci@9/SUNW,qlc@0/fp@0,0/ses@w207000c0ffd5448e,0" 2 "ses"
"/pci@500/pci@0/pci@8" 7 "pxb_plx"
"/pci@500/pci@0/pci@8/network@0" 4 "nxge"
"/pci@500/pci@0/pci@8/network@0,1" 5 "nxge"
"/pci@500/pci@0/pci@8/network@0,2" 6 "nxge"
"/pci@500/pci@0/pci@8/network@0,3" 7 "nxge"
"/pci@500/pci@0/pci@c" 9 "pxb_plx"
"/pci@500/pci@0/pci@d" 10 "pxb_plx"
.. you can attach to ldom whole pci bus .. as you can see, i've got attached to my domain completely io separated fiber channel card, netcard, etc .. i can fully cluster primary and logical domain on t5240 ..
regards
Similar Messages
-
Netbackup Media Server on LDOM
Hi guys,
Currently, my existing tape drive connection is using fiber. If i migrate my existing media server to LDOM. How do i make my drive visiable on the LDOM? I have already done the masking and it is visible under "format" on the control domain but not on guest domain. Pls kindly advice.There is a lot of useful information in the [LDoms Community Cookbook|http://wikis.sun.com/display/SolarisLogicalDomains/LDoms+Community+Cookbook] . Note the comments about tape in [Section 1 (NEW) - Hardware|http://wikis.sun.com/display/SolarisLogicalDomains/Section+1+%28NEW%29+-+Hardware] .
have a good weekend,
Glen -
How can we move LDOM from one serve to other.
Hi,
i have an LDOM setup on a T6320 Blade with Solaris 10.
The boot image of LDOM is under a ZPool image of 32 GB.
I want to move this LDOM from T6320 to another T6340. but they don't have the shared disk or not connected to same SAN.
Sun's document talks about moving the LDOM but what i understood is it is only applicable if the virtual disks are accessable from both the servers.
Can anybody help me here ?
Thanks,
jerinHi,
You can try something like this :-
SQL> CONNECT SYS/SYS123@SERVER AS SYSDBA
Connected.
SQL> CREATE USER TEST_1 IDENTIFIED BY TEST_1;
User created.
SQL> CREATE USER TEST_2 IDENTIFIED BY TEST_2;
User created.
SQL> GRANT CONNECT,RESOURCE,DBA TO TEST_1;
Grant succeeded.
SQL> GRANT CONNECT,RESOURCE,DBA TO TEST_2;
Grant succeeded.
SQL> CONNECT TEST_1/TEST_1@SERVER
Connected.
SQL> CREATE TABLE TEST_COPY ( TEST_COL NUMBER );
Table created.
SQL> INSERT INTO TEST_COPY VALUES ( 1 );
1 row created.
SQL> INSERT INTO TEST_COPY VALUES ( 2 );
1 row created.
SQL> COMMIT;
Commit complete.
SQL> GRANT ALL ON TEST_COPY TO TEST_2;
Grant succeeded.
SQL> CONNECT TEST_2/TEST_2@SERVER
Connected.
SQL> CREATE TABLE TEST_COPY AS SELECT * FROM TEST_1.TEST_COPY;
Table created.
SQL> SELECT * FROM TEST_COPY;
TEST_COL
1
2Regards,
Sandeep -
Veritas NetBackup using backint: error -8020 Reply buffer filled
Hi All
I'm trying to configure NetBackup on one of our SAP BW 7.0 system with MaxDB 7.6.00.35 running on Linux. I followed sap help and configure the backint. But when I execute the backup I'm getting the following error.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Reply buffer filled.
following is the dbm.ebp
2007-06-26 21:35:40
Setting environment variable 'TEMP' for the directory for temporary files and pipes to default ''.
Setting environment variable 'TMP' for the directory for temporary files and pipes to default ''.
Using connection to Backint for MaxDB Interface.
2007-06-26 21:35:40
Checking existence and configuration of Backint for MaxDB.
Using configuration variable 'BSI_ENV' = '/sapdb/data/wrk/BWA/backint/config' as path of the configuration file of Backint for MaxDB.
Setting environment variable 'BSI_ENV' for the path of the configuration file of Backint for MaxDB to configuration value '/sapdb/data/wrk/BWA/backint/config'.
Reading the Backint for MaxDB configuration file '/sapdb/data/wrk/BWA/backint/config'.
Found keyword 'BACKINT' with value '/sapdb/BWA/db/bin/backint'.
Found keyword 'INPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
Found keyword 'OUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
Found keyword 'ERROROUTPUT' with value '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
Found keyword 'PARAMETERFILE' with value '/sapdb/data/wrk/BWA/backint/adapter.para'.
Found keyword 'TIMEOUT_SUCCESS' with value '600'.
Found keyword 'TIMEOUT_FAILURE' with value '300'.
Found keyword 'ORIGINAL_RUNDIRECTORY' with value '/sapdb/data/wrk/BWA/'.
Finished reading of the Backint for MaxDB configuration file.
Using '/sapdb/BWA/db/bin/backint' as Backint for MaxDB program.
Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in' as input file for Backint for MaxDB.
Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output file for Backint for MaxDB.
Using '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output file for Backint for MaxDB.
Using '/sapdb/data/wrk/BWA/backint/adapter.para' as parameter file for Backint for MaxDB.
Using '600' seconds as timeout for Backint for MaxDB in the case of success.
Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
Using '/sapdb/data/wrk/BWA/dbm.knl' as backup history of a database to migrate.
Using '/sapdb/data/wrk/BWA/dbm.ebf' as external backup history of a database to migrate.
Checking availability of backups using backint's inquire function.
Check passed successful.
2007-06-26 21:35:40
Checking medium.
Check passed successfully.
2007-06-26 21:35:40
Preparing backup.
Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
Setting environment variable 'BI_REQUEST' to value 'NEW'.
Setting environment variable 'BI_BACKUP' to value 'FULL'.
Constructed Backint for MaxDB call '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
B.in -c'.
Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out' as output for Backint for MaxDB.
Created temporary file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err' as error output for Backint for MaxDB.
Writing '/backup/BWA/BWAPIPE #PIPE' to the input file.
Prepare passed successfully.
2007-06-26 21:35:40
Creating pipes for data transfer.
Creating pipe '/backup/BWA/BWAPIPE' ... Done.
All data transfer pipes have been created.
2007-06-26 21:35:40
Starting database action for the backup.
Requesting 'SAVE DATA QUICK TO '/backup/BWA/BWAPIPE' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'BWAPIPE'' from db-kernel.
The database is working on the request.
2007-06-26 21:35:40
Waiting until database has prepared the backup.
Asking for state of database.
2007-06-26 21:35:40 Database is still preparing the backup.
Waiting 1 second ... Done.
Asking for state of database.
2007-06-26 21:35:41 Database is still preparing the backup.
Waiting 2 seconds ... Done.
Asking for state of database.
2007-06-26 21:35:43 Database has finished preparation of the backup.
The database has prepared the backup successfully.
2007-06-26 21:35:43
Starting Backint for MaxDB.
Starting Backint for MaxDB process '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/adapter.para -i /sapdb/data/wrk/BWA/backint/backint4MAXD
B.in -c >>/sapdb/data/wrk/BWA/backint/backint4MAXDB.out 2>>/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
Process was started successfully.
Backint for MaxDB has been started successfully.
2007-06-26 21:35:44
Waiting for end of the backup operation.
2007-06-26 21:35:44 The backup tool is running.
2007-06-26 21:35:44 The database is working on the request.
2007-06-26 21:35:49 The backup tool is running.
2007-06-26 21:35:49 The database is working on the request.
2007-06-26 21:35:59 The backup tool is running.
2007-06-26 21:35:59 The database is working on the request.
2007-06-26 21:36:14 The backup tool is running.
2007-06-26 21:36:14 The database is working on the request.
2007-06-26 21:36:34 The backup tool is running.
2007-06-26 21:36:34 The database is working on the request.
2007-06-26 21:36:41 The backup tool process has finished work with return code 2.
2007-06-26 21:36:41 The database has finished work on the request.
Receiving a reply from the database kernel.
Got the following reply from db-kernel:
SQL-Code :-8020
Date :20070626
Time :00213542
Database :BWA
Server :s254176rg04
KernelVersion :Kernel 7.6.00 Build 035-123-139-084
PagesTransfered :131072
PagesLeft :2847194
MediaName :BWAPIPE
Location :/backup/BWA/BWAPIPE
Errortext :end of file
Label :DAT_000000025
IsConsistent :true
FirstLogPageNo :1777329
DBStamp1Date :20070626
DBStamp1Time :00213541
BDPageCount :2978242
DevicesUsed :1
DatabaseID :s254176rg04:BWA_20070605_123955
Max Used Data Page
Converter Page Count :1604
The backup operation has ended.
2007-06-26 21:36:41
Filling reply buffer.
Have encountered error -24920:
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Constructed the following reply:
ERR
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes. The database request failed with error -8020.
Reply buffer filled.
2007-06-26 21:36:41
Cleaning up.
Removing data transfer pipes.
Removing data transfer pipe /backup/BWA/BWAPIPE ... Done.
Removed data transfer pipes successfully.
Copying output of Backint for MaxDB to this file.
Begin of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
Reading parameter file /sapdb/data/wrk/BWA/backint/adapter.para.
Using staging area /sapdb/BWA/backintstage/stage1 with a size of 1073741824 bytes.
Using staging area /sapdb/BWA/backintstage/stage2 with a size of 1073741824 bytes.
Using staging area /sapdb/BWA/backintstage/stage3 with a size of 1073741824 bytes.
Using staging area /sapdb/BWA/backintstage/stage4 with a size of 1073741824 bytes.
Using 2 file per Backint for Oracle call.
Using /sapdb/BWA/db/bin/backint as Backint for Oracle.
Using /sapdb/data/wrk/BWA/backint/initBWA.utl as parameterfile of Backint for Oracle.
Using /sapdb/data/wrk/BWA/backint/BackintHistory as history file.
Using /sapdb/data/wrk/BWA/backint/backint4Oracle.in as input of Backint for Oracle.
Using /sapdb/data/wrk/BWA/backint/backint4Oracle.out as output of Backint for Oracle.
Using /sapdb/data/wrk/BWA/backint/backint4Oracle.err as error output of Backint for Oracle.
Reading input file /sapdb/data/wrk/BWA/backint/backint4MAXDB.in.
Backing up pipe /backup/BWA/BWAPIPE.
Found 1 entry in the input file.
Starting the backup.
Starting pipe2file program(s).
Waiting for creation of temporary files.
1 temporary file is available for backup.
Calling Backint for Oracle at 2007-06-26 21:36:40.
Calling '/sapdb/BWA/db/bin/backint -u BWA -f backup -t file -p /sapdb/data/wrk/BWA/backint/initBWA.utl -i /sapdb/data/wrk/BWA/backint/backint4Oracle.in -c' .
Backint for Oracle ended at 2007-06-26 21:36:40 with return code 2.
Backint for Oracle output: Reading parameter file /sapdb/data/wrk/BWA/backint/initBWA.utl.
Backint for Oracle output:
Backint for Oracle output:
Backint for Oracle error output: No staging area is defined in the parameter file.
Backint for Oracle error output: The path of Backint for Oracle is not defined in the parameter file.
Backint for Oracle error output: The name of the history file is not defined in the parameter file.
Backint for Oracle error output: The name of the input file of Backint for Oracle is not defined in the parameter file.
Backint for Oracle error output: The name of the output file of Backint for Oracle is not defined in the parameter file.
Backint for Oracle error output: The name of the error output file of Backint for Oracle is not defined in the parameter file.
Backint for Oracle error output:
Finished the backup unsuccessfully.
#ERROR /backup/BWA/BWAPIPE
End of output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.out)----
Removed Backint for MaxDB's temporary output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.out'.
Copying error output of Backint for MaxDB to this file.
Begin of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
Backint for Oracle was unsuccessful.
End of error output of Backint for MaxDB (/sapdb/data/wrk/BWA/backint/backint4MAXDB.err)----
Removed Backint for MaxDB's temporary error output file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.err'.
Removed the Backint for MaxDB input file '/sapdb/data/wrk/BWA/backint/backint4MAXDB.in'.
Have finished clean up successfully.
Please help
Thanks
AndyHi Natalia
Thanks for the reply. Below is initBWA.utl file. At this stage The first staging file is successfully written to the tape and the backup fails after that. The problem I guess is the staging file is not getting deleted or over written after it is written to the tape. Thanks
backint parameters
switch_list: is required and is used as a control file to communicate with
BACKINT and BRBACKUP for online backups. A switch list file is created
every time BRBACKUP wants to backup a file or when it wants to indicate that
a backup is finished. The switch_list parameter must be set to a file path
that is located in: $ORACLE_HOME/sapbackup/.switch.lis.
switch_list /sapdb/BWA/backintstage/.switch.lis
switch_sem: is required and is used as a control file which is used between
BACKINT and BRBACKUP to communicate. After the switch list file has been
created and closed, BACKINT creates the switch semaphore file and waits until
it is deleted by BRBACKUP. The switch_sem parameter must be set to a file
path that is located in: $ORACLE_HOME/sapbackup/.switch.sem.
switch_sem /sapdb/BWA/backintstage/.switch.sem
switch_log: is required and is used as a control file which is used between
BACKINT and BRBACKUP to communicate. After the switch semaphore file has
been deleted, BACKINT opens and reads the switch log file to determine if
the process is successful. The switch log file is created by BRBACKUP. The
switch_log parameter must be set to a file path that is located in:
$ORACLE_HOME/sapbackup/.switch_log.
switch_log /sapdb/BWA/backintstage/.switch.log
backint_dir: is an optional parameter and must be set to a directory that is
public. BACKINT uses this directory for work space and to store files called
backint.times, which keeps track of backup information.
#backint_dir /oracle/SAP/sapscript/backint_dir
server: is an optional parameter and is the machine name of the NetBackup
Master server. The NetBackup Master server is the name of the machine that
provides most of the administration and control for Netbackup operations and
contains the NetBackup database. If BACKINT finds a $SAP_SERVER environment
variable, the server parameter's value will be overriden by the value of
$SAP_SERVER. Also, if the server parameter is not specified and there is no
environment variable then the server parameter value will default to the
SERVER option specified in the Netbackkup bp.conf file.
#server jupiter
client: is an optional parameter and must be set to a machine name that has
the NetBackup client software, an Oracle database, and a SAP environment.
In some cases the server and client machine will be the same machine. If
BACKINT finds a $SAP_CLIENT environment variable, the client parameter value
will be overriden by the assigned environment variable. If the client
parameter is not specified and there is no environment variable, then the
client parameter value will default to the CLIENT_NAME specified in the
Netbackkup bp.conf file. If the value is not in bp.conf, BACKINT uses the
value returned by the gethostname() libary function.
#client jupiter
drives: is an optional parameter and should be set to the number of
simultaneous tape drives to kickoff backup. Set NetBackup Server to support
multiple simultaneous client backups and the number of storage units/tape
drives for this backup policy. Based on the number of drives specified
BACKINT will simultaneously run the same number of bpbackup/bprestore
commands. So for example, if the drives parameter is set to 5, then 5
bpbackup/bprestore jobs will run at the same time. The drives parameter
should be set to the following rule:
drives = Number of storage units per policy X MPX number
The drives parameter value should not exceed the Set Maxium Jobs per Client
global attribute. If BACKINT finds a $SAP_DRIVES environment variable, the
drive parameter value will be overriden by the value of the $SAP_DRIVES
variable. If the drive parameter is not specified and there is no
environment variable, then BACKINT will exit with an error.
#drives 1
policy: is an optionl parameter and should be set to the name of a SAP policy
type that has been defined in Netbackup. The SAP policy must have a schedule
type of Application Backup defined in order for BACKINT to work. If BACKINT finds
a $SAP_POLICY environment variable, the policy parameter value will be
overriden by the value of the $SAP_POLICY variable. If the policy parameter
is not specified and there is no environment variable, then the policy
parameter value will default to the BPBACKUP_POLICY option in the NetBackup
bp.conf file. By default, BPBACKUP_POLICY is not in any bp.conf file, then
NetBackup uses the first SAP policy type that it finds that has the client
and a user-directed backup schedule.
policy AXON2541766-SAP
schedule: Is optional and must be set to the name of type Application Backup
schedule that is associates with a SAP policy type. The schedule can
define aspects of the backup such as how long Netbackup retains images,
maximum MPX per drive, storage unit, and volume pool. If BACKINT finds a
$SAP_SCHED environment variable, the schedule parameter value will be
overriden by the value of the $SAP_SCHED environment variable. If the
schedule parameter is not specified and there is no environment variable,
then the schedule parameter value will default to the BPBACKUP_SCHED option
in the NetBackup bp.conf file. By default BPBACKUP_SCHED is not in any
bp.conf file then, NetBackup uses the first schedule of type Application Backup
that it finds. It is higly recommended to set schedule parameter in *.utl file.
#schedule Default-Application-Backup
policy2: is optional and is the name of a policy to be used for the
secondary SAP backup. The secondary backup is performed for each SAP
database backup on files that are needed to track SAP backup information.
This option would be used to save the backup information on a different
media. If policy2 is not specified, then the policy parameter value is used.
#policy2 sap_sec_backup
schedule2: is optional and is the name of a Application Backup schedule to be
used for the secondary SAP backup. The secondary backup is performed for
each SAP database backup on files that are needed to track SAP backup
information. This option would be used to save the backup information on a
different media. If schedule2 is not specified, then the schedule parameter
value is used.
#schedule2 userbkps
sort_backup_type: [size | custom | device | drive ]
This parameter is optional and is used to specify four different backup
sort option. If sort_backup_type is not specified it will default to
the size option.
#sort_backup_type size
sort_backup_type: [image | custom | drive ]
This parameter is optional and is used to specify three different restore
sort option. If sort_restore_type is not specified it will default to
the image option.
#sort_restore_type image
custom_sort_file: is optional and is used in conjunction with the
sort_backup_type and sort_restore_type parameter. If the custom option is
specified on either the sort_backup_type or sort_restore_type parameter,
then the custom_sort_file parameter needs to be set to a valid file. The
value for this parameter must be a full path name to a custom sort file and
must have public permissions.
#custom_sort_file /oracle/SAP/sapscripts/custom_sort_file
master_time_offset: is an option parameter used to restore old backups
if there was a time difference between the master and client machines.
This option should only be used for restoring 3.0 or older backup or if a
backint restore can't find a specified backup. The master_time_offset is
specified in minutes. The value will be subtract from the start time and
added to the end time for a restore or inquire.
#master_time_offset 2
#sleep: is optional and is used to specify a sleep time to monitor the
bpbackup or bprestore logs. The default is 5 seconds. When BACKINT is
called a number of bpbackup/bprestore commands can be running at the
sametime. BACKINT monitors each command and display the information to the
-o parameter. In some cases bpbackup/bprestore information is not displayed
because of the monitoring cycle. Therefore this option is used mainly for
debug reasons.
#sleep 5
policy_log: is optional and is the name of a policy to be used for
backing up a second copy of an archive log. If this option is specified
then two backups will be performed on the same archive log. The first
backup will go to the "policy" name option and the second backup will go
to the "policy_log" name option.
#policy_log sap_archive_logs
sched_log: is optional and is the name of a schedule to create a second
backing up of an archive log. If this option is specified then two backup
will be performed on the same archive log. The first backup will go to the
"schedule" option and the second backup will be go to the "sched_log" and
option. The "sched_log" name must be a valid schedule name under the
"policy_log" name option, otherwise it must be a valid schedule name under
the "policy" name option.
#sched_log Default-Application-Backup
retry_backup: is an optional parameter and should be set to the number of
retries for a failed backup. If this option is specified BACKINT will
retry a failed bpbackup job. The number of retries is determine by the
value on the retry_backup parameter.
#retry_backup 2
fail_backup: is optional and is used to stop the backup process immediately
when an error occurs. The standard behavior of BACKINT is to continue
processing even in the event of an error and then report what files failed
and what files were successful. If this parameter is specified then BACKINT
will stop process on the first error and report failures for all the
files that were not backed up.
#fail_backup
media_notify_script: is optional and is used to call a script when a
"Waiting mount" is displayed in a bpbackup/bprestore log. The value for this
option must be the full path name to a script. The script should also have
the right file permissions and should be tested before implementation. If
the message is encountered and this optional is specified, then the
following commands will be executed from BACKINT:
MEDIA_ID=A001;export MEDIA_ID
NETBACKUP_SERVER=saturn;export NETBACKUP_SERVER
/oracle/SAP/sapscripts/sap_media_notify
#media_notify_script /oracle/SAP/sapscripts/sap_media_notify
restore_filter: is optional and is used to resolve linked file paths on a
restore. This parameter should be commented out and should be used only on
rare occassions. The following are the cases were this parameter is needed:
1) Oracle table spaces use file paths
2) The directory paths to the Oracle table spaces are linked paths
3) The linked directory paths don't exist at restore time
The value for this parmater must be a fully qualified file path name to a
script, which has the right permissions and has been tested before being
implemented. The script must have an input and output parameter and be able
to modify the contents of a text file which contains file paths. The script
is responsible for converting linked directory paths into absolute directory
paths. See /usr/openv/netbackup/ext/db_ext/sap/scripts/restore_filter for
an example.
#restore_filter /oracle/SAP/sapscripts/restore_filter.sh
bplist_filter: is optional and is used to resolve linked file passes on an
inquire. This parameter should be commented out and should be used only on
rare occassions. Like the restore_filter_script parameter this is needed
for the following cases:
1) Oracle table spaces use file paths
2) The directory paths to the Oracle table spaces are linked paths
3) The linked directory paths don't exist at restore time
The value for this option must be a fully qualified path name to a script,
which has the right file permission and has been tested before being
implemented. The script must have an input and output parameter and be able
to modify the contents of a text file, which contains file paths. The script
is responsible for converting absolute directory paths into linked directory
paths. This is just the opposite of the restore filter script. See
/usr/openv/netbackup/ext/db_ext/sap/scripts/bplist_filter for an example. -
Backup MaxDB 7.7.06.09 to Veritas Netbackup 6.5 fails
We want to backup MaxDB to Veritas Netbackup server.
According documentation found about this topic the backup is configured
by creating 3 files: bsi.env, initWDO.par (for backint for MaxDB) and
initWDO.utl (for backint for Oracle). The contents of these files are shown below.
When running the backup, it seems that backint for MaxDB ends with return code 2,
the error message received is:
-24920,ERR_BACKUPOP: backup operation was unsuccessful
The backup tool failed with 2 as sum of exit codes.
Unfortunately no further errors/warnings are shown that points in any direction
what's going wrong here.
We start the backup via the following dbmcli-command:
dbmcli -u control,****** -d WDO -uUTL control,****** backup_start BACKData_WDO
(for the time being without xuser entries, first make sure the backup is ok)
The files dbm.ebl, dbm.prt and several others do not show any additional details/hints.
It seems as if the "save data quick" to the named pipe is ok, the sql-code returns "0".
After this the backint for MaxDB should read the named pipe and write it to stage-files,
but backint (for MaxDB) ends with return code 2.
Any idea what might go wrong here?
With kind regards,
R. Hoogeveen
The Netherlands
File bsi.env:
=========
BACKINT /sapdb/WDO/db/bin/backint
INPUT /tmp/backint4maxdb_WDO.in
OUTPUT /tmp/backint4maxdb_WDO.out
ERROROUTPUT /tmp/backint4maxdb_WDO.err
PARAMETERFILE /sapdb/data/wrk/WDO/initWDO.par
TIMEOUT_SUCCESS 600
TIMEOUT_FAILURE 300
ORIGINAL_RUNDIRECTORY /sapdb/data/wrk/WDO
File initWDO.par:
=============
STAGING AREA: /tmp/stageWDO 1 GB
FILES PER BACKINT CALL: 1
BACKINT: /usr/openv/netbackup/bin/backint
PARAMETERFILE OF BACKINT: /sapdb/data/wrk/WDO/initWDO.utl
HISTORY FILE: /sapdb/data/wrk/WDO/backint_history_WDO.log
INPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.in
OUTPUTFILE FOR BACKINT: /tmp/backint4ora_WDO.out
ERRORFILE FOR BACKINT: /tmp/backint4ora_WDO.err
MAXIMAL DELAY OF BACKINT CALL: 30
File initWDO.utl:
=============
switch_list /tmp/.switch_WDO.lis
switch_sem /tmp/.switch_WDO.sem
switch_log /tmp/.switch_WDO.log
drives 1
client wdocsz01
server backfire
policy sap_WDOLars,
The /tmp/backint4maxdb.err file tells me:
Backint for Oracle was unsuccessful.
(Unfortunately that was all information in this file.)
The backint4ora.in file tells me:
/tmp/stageWDO.0
(looks ok to me, also at the time backint4ora was started the stage file was created with non-zero size)
The backint4ora.out file tells me:
ERROR: incorrect format or option in .utl file (-p)
(this seems as if the -p option is not recognized by the backint4ora executable)
When I run this executable manually as user sdb it shows me the commandline that I should use, including the -p option.
One strange thing I notice is that the order of the options is different from the commandline that is executed.
(in the usage it shows -p as almost last parameter, the command executed has -p in the middle; I will see if I can execute the backint4ora command manually, since I have the stage file available, I have copied it during the process)
The backint4ora.err file is empty.
The commandline of the dbmcli command I execute shows me another interesting error message,
this might also be the source of all problems here.
-24920,ERR_BACKUPOP: backup operation was unsuccessful
Could not get external backup ID's from the backup tool.
I tried to retrieve the external backup id's manually for medium BACKDataWDO, it show me OK without any external backup id's.
I am not sure, but I think this is correct since no successfull backup was created yet with external backup tool.
Can it also be that the parameter "history file" from the initWDO.par file is set wrong?
Currently it is set to "/sapdb/data/wrk/WDO/backint_history_WDO.log" (see above also), but I can imagine
that this should be set to the dbm.knl or dbm.ebf file ??
With kind regards,
Roger Hoogeveen -
Add Hardware in T4-2 change constraints configuration in ldom guest
The customer backup the ldom configuration before the activity but when the customer add more cpu and memory in T4-2 the ldoms GUEST
cant be initialized because they lost the original configuration , i saw in the control domain the new resorces but this modified the resorces paths in the ldom-guest
there somehow to mantain the last configuration when add more hardware without restore the ldom configuration ?
TnksHi,
this sounds like the topic described in MOS Doc 1983316.1
Install procedure for upgrading from single to dual Processor Module boards on SPARC T4-4 with secondary root domain Oracle VM configurations (Doc ID 1983316.1)
Please check also
https://docs.oracle.com/cd/E23411_01/pdf/E23415.pdfhttps://docs.oracle.com/cd/E23411_01/pdf/E23415.pdf
from page 95 on
best regards,
Alfred -
How do I create a VNIC in a 1.2 LDOM?
I have a T2000 on which I am running multiple LDOMs using version 1.2 (the newest version that supports my hardware).
# ldm -V
Logical Domain Manager (v 1.2)
Hypervisor control protocol v 1.3
Using Hypervisor MD v 1.1
System PROM:
Hypervisor v. 1.7.3. @(#)Hypervisor 1.7.3.c 2010/07/09 15:14\015
OpenBoot v. 4.30.4. @(#)OBP 4.30.4.b 2010/07/09 13:48I am running Solaris 11.1 on both the service domain & the guest domain. The guest domain will be running multiple web servers, and as such, needs multiple virtual network interfaces so I can have multiple IPs assigned to that domain.
When I try to create a VNIC in the guest domain, it fails thusly:
# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net0 Ethernet up 0 unknown vnet0
net3 Ethernet unknown 0 unknown e1000g0
net1 Ethernet unknown 0 unknown e1000g1
# dladm create-vnic -l net0 vnic254
dladm: vnic creation over net0 failed: operation failedAfter some searching, I discovered that this is not supported (creating VNICs in guest domains).
I am, however, able to create a VNIC in the service domain:
# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
e1000g0 Ethernet up 1000 full e1000g0
e1000g1 Ethernet unknown 0 unknown e1000g1
vsw0 Ethernet up 1000 full vsw0
# dladm create-vnic -l e1000g0 vnic254
# ipadm create-ip vnic254
# ipadm create-addr -T static -a 192.168.1.254/24 vnic254/v4address
# dladm show-vnic
LINK OVER SPEED MACADDRESS MACADDRTYPE VID
vnic254 e1000g0 1000 2:8:20:7d:18:d0 random 0
# ipadm show-addr vnic254/v4address
ADDROBJ TYPE STATE ADDR
vnic254/v4address static ok 192.168.1.254/24Now that I have a VNIC with a v4 IP it seems to me I ought to somehow be able to assign it to the guest domain.
Is this possible, or am I out of luck?
Would this scenario be supported if I downgraded to Solaris 10? I obviously would rather not do that, but I absolutely require the ability to have multiple IPs in my guest domain.
Thanks,
BillOK, I found one possible solution, though I don't know if it's the best (or only) one.
Instead of creating a VNIC in the service domain and assigning it to the guest, I created a new vnet for the guest.
# ldm add-vnet vnic254 primary-vsw0 guest1
# ldm ls-bindings guest1
# ldm ls-bindings guest1
(snip)
NETWORK
NAME SERVICE DEVICE MAC MODE PVID VID MTU
vnet1 primary-vsw0@primary network@0 00:14:4f:f9:42:52 1 1500
PEER MAC MODE PVID VID MTU
primary-vsw0@primary 00:14:4f:f9:49:3c 1 1500
vnet1@guest2 00:14:4f:f8:46:29 1 1500
vnic254@guest1 00:14:4f:f9:a3:80 1 1500
NAME SERVICE DEVICE MAC MODE PVID VID MTU
vnic254 primary-vsw0@primary network@1 00:14:4f:f9:a3:80 1 1500
PEER MAC MODE PVID VID MTU
primary-vsw0@primary 00:14:4f:f9:49:3c 1 1500
vnet1@guest2 00:14:4f:f8:46:29 1 1500
vnet1@guest1 00:14:4f:f9:42:52 1 1500I was then able to configure the added IP in the guest.
# dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net0 Ethernet up 0 unknown vnet0
net3 Ethernet unknown 0 unknown e1000g0
net1 Ethernet unknown 0 unknown e1000g1
net7 Ethernet unknown 0 unknown vnet1
# ipadm create-ip net7
# ipadm create-addr -T static -a 192.168.1.254/24 net7/v4address
# ipadm show-addr net7/v4address
ADDROBJ TYPE STATE ADDR
net7/v4address static ok 192.168.1.254/24
# ifconfig net7
net7: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 192.168.1.254 netmask ffffff00 broadcast 192.168.1.255
ether 0:14:4f:f9:a3:80 So it works, and I can ping it from other domains & external machines.
So is this the best solution? Is there any limit to this? Can I add 20 more IPs this way if I need to?
Thanks,
Bill -
Is there a way on maxdb to force netbackup to use different initSID.utl fil
(This thread refers to a question that was posted to a blog and where the proper location to handle it is this forum)
Is there a way on maxdb to force netbackup to use different initSID.utl files ? I have try to do it with different bsi.env file . But if i start the backup it keep on asking for the default bsi.env file in /sapdb/data/wrk/SID directory . I have set the variable BSI.ENV to the new file but it looks like it ignore it. Its on a sun solaris operating system
Due to security reasons the DBM server process does no longer inherit environment variables from its caller, e.g. dbmcli.
see PTS 1155045, as especially in the area of external backup tools inheriting environment settings seem to be rather common.
Idea is to add BSI_ENV to the dbm.cfg file with a command like:
dbmcli -d ... -u ... dbm_configset BSI_ENV
For further information please refer to this documentation section
or for Backint also here
Best regards
JörgHi Jörg,
hmmm. I'd guess there are some problem with for which user the environment variables have been defined...
Anyhow, usually it's easier not to use the environment variables but to provide the dbm-server it's own runtime variables via dbm_configset.
Check the old thread archive_stage and archive_stage_repeat to different NSR_POOLs for an example application of this.
regards,
Lars -
Error while creating zone inside Solaris 11.2 beta ldom
hi
i have installed solaris 11.2 in ldom (sparc ovm 3.1 )
and i try to create zone inside guest domain , it always give this error
Error occurred during execution of 'generated-transfer-3442-1' checkpoint.
Failed Checkpoints:
Checkpoint execution error:
Error refreshing publishers, 0/1 catalogs successfully updated:
Framework error: code: 28 reason: Operation too slow. Less than 1024 bytes/sec transfered the last 30 seconds
URL: 'http://pkg.oracle.com/solaris/beta/solaris/catalog/1/catalog.summary.C' (happened 4 times)
Installation: Failed. See install log at /system/volatile/install.3442/install_log
ERROR: auto-install failed.You might want to tune PKG_CLIENT_LOWSPEED_TIMEOUT before running "zoneadm install"
For example:
# export PKG_CLIENT_LOWSPEED_TIMEOUT=300 -
Question on Netbackup configuration
DB version : 11.2
OS platform : AIX 6.1
Netbackup version : 7
I need to configure RMAN backup to tape for my Production DB using netbackup as the MML. The instruction given to me was
Shutdown all DBs running from this Oracle Home # Missed this step
cd $ORACLE_HOME/lib
ls -lrt libobk.a
ln -s /usr/openv/netbackup/bin/libobk.a64 libobk.a
Start all DBsI did all the above steps except bringing down the DB running from this ORACLE_HOME. After the symbolic link creation I even tested backup of the Control file to tape successfully. Tonight at non-peak hours I am going to run the Full DB backup. Will there be any issue due to DB not being bounced? I can't test it now as it is production.Hi,
did all the above steps except bringing down the DB running from this ORACLE_HOME...
Will there be any issue due to DB not being bounced?Don't worry the MML installation and link creation can be done without stopping the running instances since Oracle release 9i.
From:
http://docs.oracle.com/cd/B10500_01/server.920/a96566/rcmconfg.htm#453248
You do not need to start or shut down the instance when installing the media management library.You seem to be on 11gR2 so it all should work fine.
I can't test it now as it is productionWell doing the backup now will generate extra I/O now as well....
Regards,
Tycho -
Guest LDOM disk access through multiple IO domains
Hi All,
I am working on a configuration, wherein the boot disk to the Guest LDOM is being provided through an image file hosted on a VxVM diskgroup (vmdg1). The configuration has another copy of the same image file being provided through another VxVM diskgroup (vmdg2)l through another virtual disk service.
let me clear the configuration a little more in detail
A T-5240 server having 2 IO domains configured
Primary (Control domain + IO domain + Service domain) configuration
A VxVM diskgrop (vmdg1) having a boot image file
Secondary (IO domain + Service domain) configuration
A VxVM diskgroup (vmdg2) having a copy of the boot image file
these devices are exported through their respective virtual disk services with the same mpgroup name to a guest LDOM. The vdsisk is then assigned to the guest ldom which is using the volume through the primary service.
When the guest LDOM is started it starts with the disk export through the Primary domain. All writes happen fine. When the VxVM diskgroup is deported from the Primary the Guest LDOM still remains online as starts using the disk image path through the secondary domain.
I then bring the VxVM diskgroup and the mounts back online on the Primary domain and deport the diskgroup from the secondary domain to see if it failsback to the image through the Primary domain. The Guest LDOM now is in a hung state and does not allow access through the local console or through network logins.
Has anyone see such a problem? Also is it recommended to use disk based image as a backend device in mpgroups through "ldm add-vdsdev" ?
TIA,
SudhirAs far as I know then only way to "re-balance" the I/O across the domains is to unbind/bind the guests. Not a great answer, but this could be done as part of the guests patching cycle.
I think there is an RFE to provide MPxIO-like features to guests. -
Unable to install OS into new LDOM
I've recently received two T3 servers, which are our first T3s. I've created multiple LDOMs on each one of them, but when I try to install Solaris 10u10 on to them, I get the following error.
Preparing system for Solaris install
Configuring disk (c0d0)
- Creating Solaris disk label (VTOC)
ERROR: Could not create Solaris disk label (VTOC)
ERROR: Could not label disks
ERROR: Could not update disks with new configuration
mkdir: "/a/var/sadm/launcher": Read-only file system
Could not update disks with new configuration
Fatal Error
Solaris installation program exited.
From the prompt, I can mount the drives, write to them, partition them, perform fmthard, etc.. all without issue.
This is the first instance of using Oracle VM for SPARC v2.2 as all of our other systems, T51x0 are all running LDOM 1.3. Since I'm having the issue across both servers, I'd assume either I'm doing something wrong, but I've not been able to determine where the issue is. Any help with this would be appreciated.
Below is our LDOM config.
bash-3.2# ldm list-bindings
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 4 3G 0.8% 22h 45m
UUID
584a9407-ae85-4c5b-c9d3-cb510fe5e573
MAC
00:10:e0:0c:bf:98
HOSTID
0x860cbf98
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
0 (0, 1, 2)
9 (74)
VCPU
VID PID CID UTIL STRAND
0 0 0 1.3% 100%
1 1 0 0.6% 100%
2 2 0 0.7% 100%
74 74 9 0.4% 100%
MEMORY
RA PA SIZE
0xf40000000 0xf40000000 3G
CONSTRAINT
threading=max-throughput
VARIABLES
boot-device=/pci@400/pci@1/pci@0/pci@4/scsi@0/disk@w318c9c3f9965e083,0:a disk net
keyboard-layout=US-English
nvramrc=devalias mydisk /pci@400/pci@1/pci@0/pci@4/scsi@0/disk
." ChassisSerialNumber 1226BDR021 " cr
use-nvramrc?=true
IO
DEVICE PSEUDONYM OPTIONS
pci@400 pci_0
niu@480 niu_0
pci@400/pci@1/pci@0/pci@8 /SYS/MB/RISER0/PCIE0
pci@400/pci@2/pci@0/pci@8 /SYS/MB/RISER1/PCIE1
pci@400/pci@1/pci@0/pci@6 /SYS/MB/RISER2/PCIE2
pci@400/pci@2/pci@0/pci@c /SYS/MB/RISER0/PCIE3
pci@400/pci@1/pci@0/pci@0 /SYS/MB/RISER1/PCIE4
pci@400/pci@2/pci@0/pci@a /SYS/MB/RISER2/PCIE5
pci@400/pci@1/pci@0/pci@4 /SYS/MB/SASHBA0
pci@400/pci@2/pci@0/pci@4 /SYS/MB/SASHBA1
pci@400/pci@2/pci@0/pci@6 /SYS/MB/NET0
pci@400/pci@2/pci@0/pci@7 /SYS/MB/NET2
VCC
NAME PORT-RANGE
primary-vcc0 5000-5010
CLIENT PORT
intg3@primary-vcc0 5000
intg4@primary-vcc0 5001
qualt@primary-vcc0 5002
ldom4@primary-vcc0 5003
VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw0 00:14:4f:f9:f2:8a aggr1 0 switch@0 1 1 1500 on
PEER MAC PVID VID MTU LINKPROP INTERVNETLINK
vnet0@intg3 00:14:4f:fb:2e:5b 1 1500
vnet0@intg4 00:14:4f:fa:cc:65 1 1500
vnet0@qualt 00:14:4f:fa:ad:49 1 1500
vnet0@ldom4 00:14:4f:fb:c5:c0 1 1500
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw1 00:14:4f:f8:a3:2f aggr2 1 switch@1 1 1 1500 on
PEER MAC PVID VID MTU LINKPROP INTERVNETLINK
vnet1@intg3 00:14:4f:f8:d4:95 1 224 1500
vnet1@intg4 00:14:4f:fb:7f:6b 1 224 1500
vnet1@qualt 00:14:4f:f9:43:fe 1 224 1500
vnet1@ldom4 00:14:4f:fb:97:29 1 224 1500
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 intg3_root /dev/dsk/c8t60060160F260300020A75F4CD2D1E111d0s6
intg4_root /dev/dsk/c8t60060160F260300022A75F4CD2D1E111d0s6
qualt_root /dev/dsk/c8t60060160F260300024A75F4CD2D1E111d0s6
ldom4_root /dev/dsk/c8t60060160F260300026A75F4CD2D1E111d0s6
intg3_swap /ldoms/swap/intg3
intg4_swap /ldoms/swap/intg4
ldom4_swap /ldoms/swap/ldom4
qualt_swap /ldoms/swap/qualt
cdrom /iso/sol-10-u10-ga2-sparc-dvd.iso
CLIENT VOLUME
intg3_root@intg3 intg3_root
intg3_swap@intg3 intg3_swap
intg4_root@intg4 intg4_root
intg4_swap@intg4 intg4_swap
qualt_root@qualt qualt_root
qualt_swap@qualt qualt_swap
ldom4_root@ldom4 ldom4_root
ldom4_swap@ldom4 ldom4_swap
cdrom@intg3 cdrom
VCONS
NAME SERVICE PORT
UART
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
intg3 active -n---- 5000 31 15G 0.1% 20h 32m
UUID
62740e55-f38b-ca17-8f93-de3b7a66a315
MAC
00:14:4f:fb:65:64
HOSTID
0x84fb6564
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
1 (8, 9, 10, 11, 12, 13, 14, 15)
2 (16, 17, 18, 19, 20, 21, 22, 23)
3 (24, 25, 26, 27, 28, 29, 30, 31)
4 (32, 33, 34, 35, 36, 37, 38)
VCPU
VID PID CID UTIL STRAND
0 8 1 0.3% 100%
1 9 1 0.3% 100%
2 10 1 0.1% 100%
3 11 1 0.0% 100%
4 12 1 0.0% 100%
5 13 1 0.0% 100%
6 14 1 0.0% 100%
7 15 1 0.3% 100%
8 16 2 0.0% 100%
9 17 2 0.0% 100%
10 18 2 0.0% 100%
11 19 2 0.0% 100%
12 20 2 0.0% 100%
13 21 2 0.1% 100%
14 22 2 0.0% 100%
15 23 2 0.0% 100%
16 24 3 0.1% 100%
17 25 3 0.0% 100%
18 26 3 0.0% 100%
19 27 3 0.0% 100%
20 28 3 0.0% 100%
21 29 3 0.0% 100%
22 30 3 0.0% 100%
23 31 3 0.0% 100%
24 32 4 0.0% 100%
25 33 4 0.0% 100%
26 34 4 0.0% 100%
27 35 4 0.0% 100%
28 36 4 0.0% 100%
29 37 4 0.0% 100%
30 38 4 0.0% 100%
MAU
ID CPUSET
1 (8, 9, 10, 11, 12, 13, 14, 15)
MEMORY
RA PA SIZE
0x10000000 0x20000000 15G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot?=false
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fb:2e:5b 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:f9:f2:8a 1 1500
vnet0@intg4 00:14:4f:fa:cc:65 1 1500
vnet0@qualt 00:14:4f:fa:ad:49 1 1500
vnet0@ldom4 00:14:4f:fb:c5:c0 1 1500
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw1@primary 1 network@1 00:14:4f:f8:d4:95 1 224 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw1@primary 00:14:4f:f8:a3:2f 1 1500
vnet1@intg4 00:14:4f:fb:7f:6b 1 224 1500
vnet1@qualt 00:14:4f:f9:43:fe 1 224 1500
vnet1@ldom4 00:14:4f:fb:97:29 1 224 1500
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
intg3_root intg3_root@primary-vds0 0 disk@0 primary
intg3_swap intg3_swap@primary-vds0 1 disk@1 primary
cdrom cdrom@primary-vds0 2 disk@2 primary
VCONS
NAME SERVICE PORT
intg3 primary-vcc0@primary 5000
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
intg4 bound ------ 5001 31 15G
UUID
38f810dc-0b36-4a0f-a9cb-bb9f2890e2b8
MAC
00:14:4f:fb:8a:8d
HOSTID
0x84fb8a8d
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
5 (40, 41, 42, 43, 44, 45, 46, 47)
6 (48, 49, 50, 51, 52, 53, 54, 55)
7 (56, 57, 58, 59, 60, 61, 62, 63)
8 (64, 65, 66, 67, 68, 69, 70)
VCPU
VID PID CID UTIL STRAND
0 40 5 100%
1 41 5 100%
2 42 5 100%
3 43 5 100%
4 44 5 100%
5 45 5 100%
6 46 5 100%
7 47 5 100%
8 48 6 100%
9 49 6 100%
10 50 6 100%
11 51 6 100%
12 52 6 100%
13 53 6 100%
14 54 6 100%
15 55 6 100%
16 56 7 100%
17 57 7 100%
18 58 7 100%
19 59 7 100%
20 60 7 100%
21 61 7 100%
22 62 7 100%
23 63 7 100%
24 64 8 100%
25 65 8 100%
26 66 8 100%
27 67 8 100%
28 68 8 100%
29 69 8 100%
30 70 8 100%
MAU
ID CPUSET
5 (40, 41, 42, 43, 44, 45, 46, 47)
MEMORY
RA PA SIZE
0x10000000 0x3e0000000 15G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot?=false
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fa:cc:65 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:f9:f2:8a 1 1500
vnet0@intg3 00:14:4f:fb:2e:5b 1 1500
vnet0@qualt 00:14:4f:fa:ad:49 1 1500
vnet0@ldom4 00:14:4f:fb:c5:c0 1 1500
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw1@primary 1 network@1 00:14:4f:fb:7f:6b 1 224 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw1@primary 00:14:4f:f8:a3:2f 1 1500
vnet1@intg3 00:14:4f:f8:d4:95 1 224 1500
vnet1@qualt 00:14:4f:f9:43:fe 1 224 1500
vnet1@ldom4 00:14:4f:fb:97:29 1 224 1500
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
intg4_root intg4_root@primary-vds0 0 disk@0 primary
intg4_swap intg4_swap@primary-vds0 1 disk@1 primary
VCONS
NAME SERVICE PORT
intg4 primary-vcc0@primary 5001
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldom4 bound ------ 5003 31 15G
UUID
f01e1450-7e89-cf40-b7cd-90494714c509
MAC
00:14:4f:fb:1f:44
HOSTID
0x84fb1f44
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
0 (3, 4, 5, 6, 7)
4 (39)
8 (71)
9 (72, 73, 75, 76, 77, 78, 79)
13 (111)
14 (112, 113, 114, 115, 116, 117, 118, 119)
15 (120, 121, 122, 123, 124, 125, 126, 127)
VCPU
VID PID CID UTIL STRAND
0 3 0 100%
1 4 0 100%
2 5 0 100%
3 6 0 100%
4 7 0 100%
5 39 4 100%
6 71 8 100%
7 72 9 100%
8 73 9 100%
9 75 9 100%
10 76 9 100%
11 77 9 100%
12 78 9 100%
13 79 9 100%
14 111 13 100%
15 112 14 100%
16 113 14 100%
17 114 14 100%
18 115 14 100%
19 116 14 100%
20 117 14 100%
21 118 14 100%
22 119 14 100%
23 120 15 100%
24 121 15 100%
25 122 15 100%
26 123 15 100%
27 124 15 100%
28 125 15 100%
29 126 15 100%
30 127 15 100%
MAU
ID CPUSET
0 (3, 4, 5, 6, 7)
MEMORY
RA PA SIZE
0x10000000 0xb60000000 15G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot?=false
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fb:c5:c0 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:f9:f2:8a 1 1500
vnet0@intg3 00:14:4f:fb:2e:5b 1 1500
vnet0@intg4 00:14:4f:fa:cc:65 1 1500
vnet0@qualt 00:14:4f:fa:ad:49 1 1500
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw1@primary 1 network@1 00:14:4f:fb:97:29 1 224 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw1@primary 00:14:4f:f8:a3:2f 1 1500
vnet1@intg3 00:14:4f:f8:d4:95 1 224 1500
vnet1@intg4 00:14:4f:fb:7f:6b 1 224 1500
vnet1@qualt 00:14:4f:f9:43:fe 1 224 1500
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
ldom4_root ldom4_root@primary-vds0 0 disk@0 primary
ldom4_swap ldom4_swap@primary-vds0 1 disk@1 primary
VCONS
NAME SERVICE PORT
ldom4 primary-vcc0@primary 5003
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
qualt bound ------ 5002 31 15G
UUID
b2ca331d-9885-6d58-c52b-e6684800c88d
MAC
00:14:4f:f9:dc:0d
HOSTID
0x84f9dc0d
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
10 (80, 81, 82, 83, 84, 85, 86, 87)
11 (88, 89, 90, 91, 92, 93, 94, 95)
12 (96, 97, 98, 99, 100, 101, 102, 103)
13 (104, 105, 106, 107, 108, 109, 110)
VCPU
VID PID CID UTIL STRAND
0 80 10 100%
1 81 10 100%
2 82 10 100%
3 83 10 100%
4 84 10 100%
5 85 10 100%
6 86 10 100%
7 87 10 100%
8 88 11 100%
9 89 11 100%
10 90 11 100%
11 91 11 100%
12 92 11 100%
13 93 11 100%
14 94 11 100%
15 95 11 100%
16 96 12 100%
17 97 12 100%
18 98 12 100%
19 99 12 100%
20 100 12 100%
21 101 12 100%
22 102 12 100%
23 103 12 100%
24 104 13 100%
25 105 13 100%
26 106 13 100%
27 107 13 100%
28 108 13 100%
29 109 13 100%
30 110 13 100%
MAU
ID CPUSET
10 (80, 81, 82, 83, 84, 85, 86, 87)
MEMORY
RA PA SIZE
0x10000000 0x7a0000000 15G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot?=false
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet0 primary-vsw0@primary 0 network@0 00:14:4f:fa:ad:49 1 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw0@primary 00:14:4f:f9:f2:8a 1 1500
vnet0@intg3 00:14:4f:fb:2e:5b 1 1500
vnet0@intg4 00:14:4f:fa:cc:65 1 1500
vnet0@ldom4 00:14:4f:fb:c5:c0 1 1500
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw1@primary 1 network@1 00:14:4f:f9:43:fe 1 224 1500
PEER MAC MODE PVID VID MTU LINKPROP
primary-vsw1@primary 00:14:4f:f8:a3:2f 1 1500
vnet1@intg3 00:14:4f:f8:d4:95 1 224 1500
vnet1@intg4 00:14:4f:fb:7f:6b 1 224 1500
vnet1@ldom4 00:14:4f:fb:97:29 1 224 1500
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
qualt_root qualt_root@primary-vds0 0 disk@0 primary
qualt_swap qualt_swap@primary-vds0 1 disk@1 primary
VCONS
NAME SERVICE PORT
qualt primary-vcc0@primary 5002
Edited by: user13014014 on Aug 1, 2012 7:32 AMAnswering my own question, I set my partitions up as below and it worked.
Customize Disk: c0d0
Boot Device: c0d0s0
Entry: / Recommended: 6458 MB Minimum: 5489 MB
================================================================================
Slice Mount Point Size (MB)
0 / 50941
1 0
2 overlap 50941
3 0
4 0
5 0
6 0
7 0
================================================================================
Capacity: 50941 MB
Allocated: 50941 MB
Free: 0 MB
Customize Disk: c0d1
Boot Device: c0d0s0
Entry: swap Recommended: 0 MB Minimum: 0 MB
================================================================================
Slice Mount Point Size (MB)
0 swap 20376
1 0
2 overlap 20376
3 0
4 0
5 0
6 0
7 0
================================================================================
Capacity: 20376 MB
Allocated: 20376 MB
Free: 0 MB -
Oracle 11gR2 RAC in LDOM Network issue
Hi, Requesting your expert advise regarding this configuration.
We are implementing LDOM 2.2 on two SPARC T4-4 for Oracle 11gR2 RAC; Solaris 10 U10 on both control and guest domain. The setup for each primary/control domain is: Two 10g links aggregated and have four VLAN trunked on the aggregate. vSwitch created using the aggr as the device as following per T4-4:
NOTE: VLAN 1501 is for data connection and VLAN 10 is for heartbeat for one RAC cluster and VL 1601 and 11 is for another RAC. all together four LDOMS.
ldm add-vswitch vid=1501,1601,10,11 net-dev=aggr1 primary-vsw0 primary
ldm add-vnet pvid=1501 vnetprod primary-vsw0 guest1
ldm add-vnet pvid=10 vnethb primary-vsw0 guest1
ldm add-vnet pvid=1601 vnetprod primary-vsw0 guest2
ldm add-vnet pvid=11 vnethb primary-vsw0 guest2
vnet inside the LDOM are not tagged:
vnet1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 10.220.128.20 netmask ffffff80 broadcast 10.220.128.127
ether 0:14:4f:f9:ec:7f
vnet2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
inet 192.168.2.11 netmask ffffff80 broadcast 192.168.2.127
ether 0:14:4f:fb:2b:8f
Here is the whole configuration:
root@gp-cpu-suh004 # ldm -V
Logical Domains Manager (v 2.2.0.0)
Hypervisor control protocol v 1.9
Using Hypervisor MD v 1.4
System PROM:
Hostconfig v. 1.2.0. @(#)Hostconfig 1.2.0.a 2012/05/11 07:34
Hypervisor v. 1.11.0. @(#)Hypervisor 1.11.0.a 2012/05/11 05:28
OpenBoot v. 4.34.0 @(#)OpenBoot 4.34.0 2012/04/30 14:26
root@gp-cpu-suh004 # ldm ls
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 32 16G 2.5% 48m
oidrac1 active -n---- 5000 32 16G 0.0% 27m
root@gp-cpu-suh004 # ldm ls -l
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv- UART 32 16G 3.1% 48m
SOFTSTATE
Solaris running
UUID
e73421fe-7003-e748-be7e-801fee5bfcc7
MAC
00:21:28:f1:95:26
HOSTID
0x85f19526
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
VCPU
MEMORY
RA PA SIZE
0x20000000 0x20000000 16G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot-on-error?=true
auto-boot?=true
boot-device=/pci@400/pci@1/pci@0/pci@0/LSI,sas@0/disk@w5000cca0251e7a29,0:a
keyboard-layout=US-English
nvramrc=." ChassisSerialNumber 1207BDYFFE " cr
use-nvramrc?=true
IO
DEVICE PSEUDONYM OPTIONS
VCC
NAME PORT-RANGE
primary-vcc0 5000-5100
VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw-mgmt 00:14:4f:fb:75:c0 igb1 0 switch@0 1 1 1500 on
primary-vsw0 00:14:4f:fa:33:8b aggr1 1 switch@1 1 1 1501,1601,10,11 1500 on
VDS
NAME VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 rootoid /dev/dsk/c14t50060E8005BFAA04d1s2
data_oid /dev/dsk/c14t50060E8005BFAA04d2s2
ocr_oid /dev/dsk/c14t50060E8005BFAA04d3s2
VCONS
NAME SERVICE PORT
UART
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
oidrac1 active -n---- 5000 32 16G 0.0% 27m
SOFTSTATE
Solaris running
UUID
0fcbbf21-14a2-eb21-f544-d4424212f3ef
MAC
00:14:4f:f9:1b:d4
HOSTID
0x84f91bd4
CONTROL
failure-policy=ignore
extended-mapin-space=off
cpu-arch=native
DEPENDENCY
master=
CORE
CID CPUSET
VCPU
VID PID CID UTIL STRAND
MEMORY
RA PA SIZE
0x20000000 0x420000000 16G
CONSTRAINT
threading=max-throughput
VARIABLES
auto-boot?=true
boot-device=disk:a
keyboard-layout=US-English
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw-mgmt@primary 0 network@0 00:14:4f:fa:61:77 1 1500
vnetprod primary-vsw0@primary 1 network@1 00:14:4f:f9:ec:7f 1501 1500
vnethb primary-vsw0@primary 2 network@2 00:14:4f:fb:2b:8f 10 1500
DISK
NAME VOLUME TOUT ID DEVICE SERVER MPGROUP
oneidrootdisk rootoid@primary-vds0 0 disk@0 primary
oid_data data_oid@primary-vds0 1 disk@1 primary
oid_ocr ocr_oid@primary-vds0 2 disk@2 primary
VCONS
NAME SERVICE PORT
oidrac1 primary-vcc0@primary 5000
root@gp-cpu-suh004 # ldm ls-services
VCC
NAME LDOM PORT-RANGE
primary-vcc0 primary 5000-5100
VSW
NAME LDOM MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw-mgmt primary 00:14:4f:fb:75:c0 igb1 0 switch@0 1 1 1500 on
primary-vsw0 primary 00:14:4f:fa:33:8b aggr1 1 switch@1 1 1 1501,1601,10,11 1500 on
VDS
NAME LDOM VOLUME OPTIONS MPGROUP DEVICE
primary-vds0 primary rootoid /dev/dsk/c14t50060E8005BFAA04d1s2
data_oid /dev/dsk/c14t50060E8005BFAA04d2s2
ocr_oid /dev/dsk/c14t50060E8005BFAA04d3s2
root@gp-cpu-suh004 # dladm show-link
vsw0 type: non-vlan mtu: 1500 device: vsw0
vsw1 type: non-vlan mtu: 1500 device: vsw1
vsw1501001 type: vlan 1501 mtu: 1500 device: vsw1
igb0 type: non-vlan mtu: 1500 device: igb0
igb1 type: non-vlan mtu: 1500 device: igb1
qlge0 type: non-vlan mtu: 1500 device: qlge0
qlge1 type: non-vlan mtu: 1500 device: qlge1
qlge2 type: non-vlan mtu: 1500 device: qlge2
qlge3 type: non-vlan mtu: 1500 device: qlge3
aggr1 type: non-vlan mtu: 1500 aggregation: key 1
root@gp-cpu-suh004 # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
igb0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.223.12.14 netmask ffffff00 broadcast 10.223.12.255
ether 0:21:28:f1:95:26
vsw1501001: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 3
inet 10.220.128.9 netmask ffffff80 broadcast 10.220.128.127
ether 0:14:4f:fa:33:8b
root@gp-cpu-suh004 # netstat -nr
Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
default 10.220.128.1 UG 1 7
10.220.128.0 10.220.128.9 U 1 5 vsw1501001
10.223.0.0 10.223.12.1 UG 1 2
10.223.12.0 10.223.12.14 U 1 1 igb0
224.0.0.0 10.220.128.9 U 1 0 vsw1501001
127.0.0.1 127.0.0.1 UH 8 261 lo0Yes, I can connect to the vswitch interface on the control domain. I didn't specify any PVID because my understanding is that PVID will tag any frame with the PVID VLAN by default. basically the PVID for this interface is 1.
Here's the VNET config for the other LDOM in the RAC cluster:
VSW
NAME MAC NET-DEV ID DEVICE LINKPROP DEFAULT-VLAN-ID PVID VID MTU MODE INTER-VNET-LINK
primary-vsw-mgmt 00:14:4f:f9:91:fa igb1 0 switch@0 1 1 1500 on
primary-vsw0 00:14:4f:fa:8e:cf aggr1 1 switch@1 1 1 1501,1601,10,11 1500 on
NETWORK
NAME SERVICE ID DEVICE MAC MODE PVID VID MTU LINKPROP
vnet1 primary-vsw-mgmt 0 00:14:4f:fb:65:6d 1
vnetprod primary-vsw0 1 00:14:4f:fa:2b:02 1501
vnethb primary-vsw0 2 00:14:4f:f8:12:c1 10
Thanks for reviewing my configuration. -
Any "Best Practice" regarding use of zfs in LDOM with zones
I have 3 different networks and I want to create a guest-domain for each of the three networks on the same control domain.
Inside each guest-domain, I want to create 3 zones.
To make it easy to handle growth and also make the zones more portable, I want to create a zpool inside each guest domain and then a zfs for each zoneroot.
By doing this I will be able to handle growth by adding vdisks to the zpool(in the guest domain) and also to migrate individual zones by using zfs send/receive.
In the "LDoms Community Cookbook", I found a description on how to use zfs clone in the control domain to decrease deploy time of new guest domains:
" You can use ZFS to very efficiently, easily and quickly, take a copy of a previously prepared "golden" boot disk for one domain and redeploy multiple copies of that image as a pre-installed boot disk for other domains."
I can see clear advantages in using zfs in both the control domain and the guest domain, but what is the downside?
I ends up with a kind of nested zfs where I create a zpool inside a zpool, the first in the control domain and the second inside a guest domain.
How is zfs caching handled, will I end up with a solution with performance problems and a lot of I/O overhead?
Kindest,
TorI'm not familiar with the Sybase agent code and you are correct, only 15.0.3 seems to be supported. I think we'd need a little more debug information to determine if there was a workaround. May be switching on *.info messages in syslogd.conf might get some more useful hints (no guarantee).
Unfortunately, I can't comment on if, or when, Sybase 15.5.x might be supported.
Regards,
Tim
--- -
Cluster in a box with Guest LDOMs : SCSI-3 reservations are not supported
Hello,
I recently installed the Oracle Solaris Cluster 4.1 in two simple Guest LDOMs (OVM for SPARC 3.1) with one T5140 server and SE 7110 as a shared storage. The some SE 7110 whole LUNs mapped as VDS devices to both LDOMs. After initial installation of Oracle Solaris Cluster 4.1 I observed issues with quorum device - both nodes cannot get SCSI3 (default) persistent reservation keys information at same time - only one node can be able to scrub. After switching cluster's global fencing option to "nofencing" (with "software" quorum implementation) both nodes can access quorum device successfully. So I can conclude that SCSI3 PGRs are not supported in this cases.
Unfortunately I didn't find any official and nonofficial documents info regarding this limitation. Could you please confirm or decline my suggestion.
Thanks.I am answering on my question by itself
Planning the Oracle Solaris OS - Oracle Solaris Cluster Software Installation Guide
Fencing – Do not export a storage LUN to more than one guest domain on the same physical machine unless you also disable fencing for that device. Otherwise, if two different guest domains on the same machine both are visible to a device, the device will be fenced whenever one of the guest domains halts. The fencing of the device will panic any other guest domain that subsequently tries to access the device.
RTFM...
Maybe you are looking for
-
Dear All, Our Client want a report in which what are all the payments made against the Purchase orders. Is there any std report available? Please advice what to do if std report not available. Regards
-
Hello Experts I have already searched for any related postings on the Package Group. I could not find any. I dont know why everytime my posting gets removed from the list. There are some postings on Package and Function Groups only - which are irrele
-
Game development: how to pause a game?
How to pause a game in order to open my inventory panel? I always think of destroying all objects, removing from stage and instantiating and adding to stage all again. But I don't know if I am going to waste my time doing that the hard way. I would l
-
When I am loading data at infopackage level in data selection we cam give the selection i.e from value & to value But when I press F4 on this it is not displaying any thing Whem I press F4 for company code then I can see the the values when I press F
-
Can we change equipment serial number
I have very basic question. We are creating Equipment Master automatically for every maerial-serial number combincation during is Good Receipt. Ther serial number is assigned manually or auto generated during Goods Receipt. Now we would like to chang