Re: Encryption in API
Fred, Here is the basic idea: Let's say that you have 3 databases, DB1 and DB2 and DB3, and you only want to encrypt data for DB2 and DB3. You would need to have an RMAN script for each database. Data Proctection for Oracle can share the same dsm.opt among these databases. Assuming your TDPO_FS is /adsmorc here is what it might look like: RMAN script for DB1: run { allocate channel t1 type 'sbt_tape'; backup format 'DB1_%d_%t_%s_%p' (database); } RMAN script for DB2: run { allocate channel t1 type 'sbt_tape'; backup format 'DB2_%d_%t_%s_%p' (database); } RMAN script for DB3: run { allocate channel t1 type 'sbt_tape'; backup format 'DB3_%d_%t_%s_%p' (database); } ** dsm.opt include.encrypt /adsmorc/.../DB2_* include.encrypt /adsmorc/.../DB3_* Regards, Neil Rasmussen Software Development Data Protection for Oracle [EMAIL PROTECTED] fred johanson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 08/28/2006 07:54 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Encryption in API Thanks Neil, explicit examples would mean I don't lose anything in transmission to the ORACLE DBAs. At 07:40 AM 8/28/2006 -0700, you wrote: >Fred, > >Encrypting Oracle databases with DP Oracle is accomplished in very much >the same fashion. The twist? In order to exploit the include.encrypt >statements you will have to rely on the 'format' statement in the RMAN >scripts that you use to backup your Oracle database. Using the 'format' >statement allows you to prepend/append characters (strings) to each backup >piece. For instance, you may have an RMAN script for each database, say >DB1 and DB2, then prepend these strings to each 'format' statement in your >RMAN script. Then you can use these identifiers in your include.encrypt >statements in your dsm.opt file. > >I can give you explicit examples if you need them. > > >Regards, > >Neil Rasmussen >Software Development >Data Protection for Oracle >[EMAIL PROTECTED] > > > > >fred johanson <[EMAIL PROTECTED]> >Sent by: "ADSM: Dist Stor Manager" >08/28/2006 07:00 AM >Please respond to >"ADSM: Dist Stor Manager" > > >To >ADSM-L@VM.MARIST.EDU >cc > >Subject >Re: Encryption in API > > > > > > >Thanks Del. I suspected that is the way it works for SQL. I can't >surmise >how to limit how much ORACLE is encrypted. > > >At 08:44 AM 8/28/2006 -0400, you wrote: > >Fred, > > > >Go to: > > http://www.ibm.com/us/ > > > >Search for: > > "Encrypting Data Protection for SQL Backups" > > > >(include the double quotes around the "Search for" text) > > > >Del > > > > > > > >"ADSM: Dist Stor Manager" wrote on 08/25/2006 > >01:07:23 PM: > > > > > Since TDP for ORACLE and MSSQL use the API, I should be able to >encrypt > > > some or all of DB backups we do. Since SQL generates the directory >name > > > for the backup, how do we determine which is which to include or >exclude > > > selected DBs on a particular client? We have one client with about 75 > >DBs > > > on it and not all should be encrypted. > >Fred Johanson >ITSM Administrator >University of Chicago >773-702-8464 Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Encryption in API
Thanks Neil, explicit examples would mean I don't lose anything in transmission to the ORACLE DBAs. At 07:40 AM 8/28/2006 -0700, you wrote: Fred, Encrypting Oracle databases with DP Oracle is accomplished in very much the same fashion. The twist? In order to exploit the include.encrypt statements you will have to rely on the 'format' statement in the RMAN scripts that you use to backup your Oracle database. Using the 'format' statement allows you to prepend/append characters (strings) to each backup piece. For instance, you may have an RMAN script for each database, say DB1 and DB2, then prepend these strings to each 'format' statement in your RMAN script. Then you can use these identifiers in your include.encrypt statements in your dsm.opt file. I can give you explicit examples if you need them. Regards, Neil Rasmussen Software Development Data Protection for Oracle [EMAIL PROTECTED] fred johanson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 08/28/2006 07:00 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Encryption in API Thanks Del. I suspected that is the way it works for SQL. I can't surmise how to limit how much ORACLE is encrypted. At 08:44 AM 8/28/2006 -0400, you wrote: >Fred, > >Go to: > http://www.ibm.com/us/ > >Search for: > "Encrypting Data Protection for SQL Backups" > >(include the double quotes around the "Search for" text) > >Del > > > >"ADSM: Dist Stor Manager" wrote on 08/25/2006 >01:07:23 PM: > > > Since TDP for ORACLE and MSSQL use the API, I should be able to encrypt > > some or all of DB backups we do. Since SQL generates the directory name > > for the backup, how do we determine which is which to include or exclude > > selected DBs on a particular client? We have one client with about 75 >DBs > > on it and not all should be encrypted. Fred Johanson ITSM Administrator University of Chicago 773-702-8464 Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Encryption in API
Fred, Encrypting Oracle databases with DP Oracle is accomplished in very much the same fashion. The twist? In order to exploit the include.encrypt statements you will have to rely on the 'format' statement in the RMAN scripts that you use to backup your Oracle database. Using the 'format' statement allows you to prepend/append characters (strings) to each backup piece. For instance, you may have an RMAN script for each database, say DB1 and DB2, then prepend these strings to each 'format' statement in your RMAN script. Then you can use these identifiers in your include.encrypt statements in your dsm.opt file. I can give you explicit examples if you need them. Regards, Neil Rasmussen Software Development Data Protection for Oracle [EMAIL PROTECTED] fred johanson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" 08/28/2006 07:00 AM Please respond to "ADSM: Dist Stor Manager" To ADSM-L@VM.MARIST.EDU cc Subject Re: Encryption in API Thanks Del. I suspected that is the way it works for SQL. I can't surmise how to limit how much ORACLE is encrypted. At 08:44 AM 8/28/2006 -0400, you wrote: >Fred, > >Go to: > http://www.ibm.com/us/ > >Search for: > "Encrypting Data Protection for SQL Backups" > >(include the double quotes around the "Search for" text) > >Del > > > >"ADSM: Dist Stor Manager" wrote on 08/25/2006 >01:07:23 PM: > > > Since TDP for ORACLE and MSSQL use the API, I should be able to encrypt > > some or all of DB backups we do. Since SQL generates the directory name > > for the backup, how do we determine which is which to include or exclude > > selected DBs on a particular client? We have one client with about 75 >DBs > > on it and not all should be encrypted. Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Encryption in API
Thanks Del. I suspected that is the way it works for SQL. I can't surmise how to limit how much ORACLE is encrypted. At 08:44 AM 8/28/2006 -0400, you wrote: Fred, Go to: http://www.ibm.com/us/ Search for: "Encrypting Data Protection for SQL Backups" (include the double quotes around the "Search for" text) Del "ADSM: Dist Stor Manager" wrote on 08/25/2006 01:07:23 PM: > Since TDP for ORACLE and MSSQL use the API, I should be able to encrypt > some or all of DB backups we do. Since SQL generates the directory name > for the backup, how do we determine which is which to include or exclude > selected DBs on a particular client? We have one client with about 75 DBs > on it and not all should be encrypted. Fred Johanson ITSM Administrator University of Chicago 773-702-8464
Re: Encryption in API
Fred, Go to: http://www.ibm.com/us/ Search for: "Encrypting Data Protection for SQL Backups" (include the double quotes around the "Search for" text) Del "ADSM: Dist Stor Manager" wrote on 08/25/2006 01:07:23 PM: > Since TDP for ORACLE and MSSQL use the API, I should be able to encrypt > some or all of DB backups we do. Since SQL generates the directory name > for the backup, how do we determine which is which to include or exclude > selected DBs on a particular client? We have one client with about 75 DBs > on it and not all should be encrypted.