01-29-2017 10:05 PM
If netbackup is using this policy to perform oracle database backup, what type of backup should I expect?
From the GUI of the netbackup(NetBackup Management > Policies > "DB Policy" > "Backup Selections" tab) it shows "WHOLE_DATABASE". While on the "Instances" tab, host and ORACLE_HOME were just provided.
We're using 7.6.0.2.
Solved! Go to Solution.
02-13-2017 08:47 PM
Hello,
No problem,
Kindly check the oracle rman configuration by using below command.
Connect to rman prompt
RMAN> show all
If we select "CONTROLLFILE AUTOBACKUP ON" in rman configuration.
It will take controlfile backup after save any changes in controlfile. It also take control file backup after successful backup from any third party vendor.
I believe that, list backup output you shared earlier also belong to autobackup. Because in oracle catalog terminology use F = Full.
Command / output reference attached. :)
Regards,
01-29-2017 11:41 PM
Hello,
The NBU Master server registers the instances available in environment automatic or we can do manually.
The WHOLE_DATABASE option backup complete database (database file, Archive Log and Control file) of that instance. The instance gets register with below information.
Instance Name: SID
HOST: Client Name
Oracle_HOME: home directory of oracle user for that instance.
Credential: The user authentication by NBU to connect and access the database.
We need to provide instance name, host name, home path and credential (OS/Oracle) to register that instance.
The instance should register successfully before configure the policy using OIP.
what type of backup should I expect?
The OIP is nothing but run time template to take backup of database. So If we are using OIP it mean taking oracle database online backup using template.
Thanks & Regards,
01-31-2017 10:17 PM
Hi Tousif,
Thank you for your response.
Yeah, I'm seeing we have the backup for these three database file, archive and control file. But checking my backup summary, I have two different database file backup, L0 (level0) and F (Full). Is it a duplicate?
02-01-2017 02:00 AM
Hello
02-01-2017 02:03 AM
Hello,
not sure which "backup summary" you are referring to, but in Oracle terminology, Full backup is "Level 0" backup, and Incremental backup is "Level 1" backup.
I recommend you to work closely with Oracle DBA when configuring Oracle policies.
regards
Michal
02-02-2017 07:15 PM
Hello,
I have two different database file backup, L0 (level0) and F (Full). Is it a duplicate?
The Level 0 and F both is full backup. If you configured the duplication or run manually then only it will show you the two copies under same backup id.
Example command: /usr/openv/netbackup/bin/admincmd/bpimagelist –backupid <backupid> -L
To check the backup images are full or incr, use the below command against client.
Example command: /usr/openv/netbackup/bin/admincmd/bpimagelist –client <client_name> -U
The default rman backup script snippet mentioned below for more information.
# Schedule type is BACKUP_TYPE is
# ---------------- --------------
# Automatic Full INCREMENTAL LEVEL=0
# Automatic Differential Incremental INCREMENTAL LEVEL=1
# Automatic Cumulative Incremental INCREMENTAL LEVEL=1 CUMULATIVE
If we select the ‘Full Backup’ schedule in backup policy configuration. It will consider as level=0 backup and execute the script parameter for full backup. The same way work for OIP (template) also.
If we configured the incremental schedule in policy and run the backup then it will consider the backup level=1 backup and execute the script parameter for incremental backup. The same way work for OIP (template) also.
Please refer the below article for more information about NBU for oracle terminology
http://www.veritas.com/docs/000073330
From your current question we are not able to understand about your expectation. There are different possible answers on your current query.
If you not get your answer from above explanation then please share the command output your are getting for L0 and F.
Thanks & Regards,
Tousif Naik
02-04-2017 11:11 PM
Hi,
Yeah, "Full" and "Level0" were the same. I 've just got confused why I have two level in our RMAN backup. For January 20, If you can see the "LV" column we have 0(Level0) and F(Full).
02-04-2017 11:21 PM
Hi Tousif,
Thank you for the input.
The Level 0 and F both is full backup. If you configured the duplication or run manually then only it will show you the two copies under same backup id.
Yes its the same, but what should I expect (0 or F) if we're using OIP? Apologies for the confusion :)
Please see screenshot above.
02-06-2017 12:51 AM
Hello,
I have reviewed my two instances with Oracle dbs backed up by OIPs. Actually, my RMAN "list backup summary" does not show any "0" values in "LV" column, just "F" and "A" values.
I recommend you to map details of parent/child Oracle jobs in Activity Monitor from 20-JAN-2017 to information in RMAN list output, then you can get an answer for what is actually "hidden" behind "F" and "0" backups.
Note - when NetBackup perform a duplication of backups, RMAN is not aware of this.
Regards
Michal
02-12-2017 10:50 PM
Hello,
Have you enabled oracle catalog backup from oracle site?
Thanks & Regards
02-13-2017 06:34 AM
Hi Sir,
Ok, let me try your recommendation and get back to you. Thank you Sir.
02-13-2017 06:38 AM
Hi Sir Tousif,
I'm not sure if the vendor who setup the configuration enable oracle catalog. I'm new in the company, and have no enough knowledge in using netbackup. Is the oracle catalog related to this tool?
02-13-2017 08:47 PM
Hello,
No problem,
Kindly check the oracle rman configuration by using below command.
Connect to rman prompt
RMAN> show all
If we select "CONTROLLFILE AUTOBACKUP ON" in rman configuration.
It will take controlfile backup after save any changes in controlfile. It also take control file backup after successful backup from any third party vendor.
I believe that, list backup output you shared earlier also belong to autobackup. Because in oracle catalog terminology use F = Full.
Command / output reference attached. :)
Regards,
02-13-2017 10:30 PM - edited 02-13-2017 10:32 PM
Hi Tousif,
All the configuration were set to default.
RMAN> show all 2> ; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name ORCL are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2/db_1/dbs/snapcf_ORCL.f'; # default
In addition, I've check the log in the console to have idea what really happened and I see this command during initialization of the job/policy. From here, incremental level0 was used.
02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - ************************************************************ 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Backup Information: 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Client: server1.domain.com 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - ORACLE_SID: ORCL 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - ORACLE_HOME: /u01/app/oracle/product/11.2/db_1 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Online (Hot) Stream backup requested 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Objects being backed up: 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Whole Database 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Archive Logs 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Control File 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Number of channels to allocate (database): 1 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Number of channels to allocate (archive logs): 1 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - OS Authentication is being used 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - RMAN Default Limits will be used (Database) 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - RMAN Default Limits will be used (Archive Logs) 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Backup File Name Formats: 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Database: bk_d%d_u%u_s%s_p%p_t%t 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Archive Log: arch_d%d_u%u_s%s_p%p_t%t 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - Control File: ctrl_d%d_u%u_s%s_p%p_t%t 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - End of Backup Information 02/13/2017 20:00:07 - Info bphdb (pid=1948) INF - ************************************************************ 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Database status is: OPEN 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Database open mode is: READ WRITE 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ARCHIVE LOG mode is: ARCHIVELOG 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - CDB mode: NOT ENABLED 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Starting Oracle Recovery Manager. 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Using: /u01/app/oracle/product/11.2/db_1/bin/rman 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Connection info: target / nocatalog 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - Start of Recovery Manager input. 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - # ----------------------------------------------------------------- 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - # RMAN command section 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - # ----------------------------------------------------------------- 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - RUN { 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ALLOCATE CHANNEL ch00 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - TYPE 'SBT_TAPE' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - SEND 'NB_ORA_CLIENT=server1.domain.com,NB_ORA_SID=ORCL,NB_ORA_SERV=bkpserver.domain.com,NB_ORA_POLICY=ORCL_PROD_DB_BKP,NB_ORA_PARENT_JOBID=39348,NB_ORA_SCHED=ORCL_Daily_Full_Schedule'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - BACKUP 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - INCREMENTAL LEVEL=0 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - FORMAT 'bk_d%d_u%u_s%s_p%p_t%t' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - DATABASE; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - RELEASE CHANNEL ch00; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - # Backup Archived Logs 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - sql 'alter system archive log current'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ALLOCATE CHANNEL ch00 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - TYPE 'SBT_TAPE' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - SEND 'NB_ORA_CLIENT=server1.domain.com,NB_ORA_SID=ORCL,NB_ORA_SERV=bkpserver.domain.com,NB_ORA_POLICY=ORCL_PROD_DB_BKP,NB_ORA_PARENT_JOBID=39348,NB_ORA_SCHED=ORCL_Daily_Full_Schedule'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - BACKUP 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - FORMAT 'arch_d%d_u%u_s%s_p%p_t%t' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ARCHIVELOG 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ALL 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - DELETE INPUT; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - RELEASE CHANNEL ch00; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - # Control file backup 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - ALLOCATE CHANNEL ch00 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - TYPE 'SBT_TAPE' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - SEND 'NB_ORA_CLIENT=server1.domain.com,NB_ORA_SID=ORCL,NB_ORA_SERV=bkpserver.domain.com,NB_ORA_POLICY=ORCL_PROD_DB_BKP,NB_ORA_PARENT_JOBID=39348,NB_ORA_SCHED=ORCL_Daily_Full_Schedule'; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - BACKUP 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - FORMAT 'ctrl_d%d_u%u_s%s_p%p_t%t' 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - CURRENT CONTROLFILE; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - RELEASE CHANNEL ch00; 02/13/2017 20:00:10 - Info bphdb (pid=1948) INF - }
Regards,
Jr
03-27-2017 09:13 PM
Hello,
My apology for delay in reply...
Just to confirm. Have you find solution on it?
Still looking for help?
Thanks & Regards
04-16-2017 11:44 PM - edited 04-16-2017 11:47 PM
Hi Tousif,
Apologies. I missed to update the thread.
Yeah, things got cleared now. I'm not sure if this was the default behavior of OIP. Its creating backup for database, archivelog and control file. These create 3 TAG. I easily identify the backup based on the logfile in netbackup console by checking the TAG assigned and compared to the backup summary.
Thank you for the help.
Regards,
J
04-16-2017 11:58 PM
Hello,
Great know that issue has fixed. Thanks for sharing this information. Much appreciate.
Each backup piece content the TAG information.
Thanks & Regards