Return-Path: X-Original-To: oracle-l@orafaq.com Delivered-To: oracle-l@orafaq.com Received: from puck1183.startdedicated.com (localhost [127.0.0.1]) by puck1183.startdedicated.com (Postfix) with ESMTP id 496881960AB4 for ; Thu, 5 May 2016 17:08:47 +0200 (CEST) Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by puck1183.startdedicated.com (Postfix) with ESMTPS for ; Thu, 5 May 2016 17:08:47 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 3C61F3822B; Thu, 5 May 2016 11:08:46 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at turing.freelists.org Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XKXy3xMZLdf0; Thu, 5 May 2016 11:08:46 -0400 (EDT) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 0BCE9384CC; Thu, 5 May 2016 11:08:34 -0400 (EDT) Received: with ECARTIS (v1.0.0; list oracle-l); Thu, 05 May 2016 11:07:12 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 24F8F38253 for ; Thu, 5 May 2016 11:07:12 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oy8DD9pMDdkH for ; Thu, 5 May 2016 11:07:12 -0400 (EDT) Received: from mail-yw0-f181.google.com (mail-yw0-f181.google.com [209.85.161.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id B1E113488F for ; Thu, 5 May 2016 11:07:11 -0400 (EDT) Received: by mail-yw0-f181.google.com with SMTP id g133so125623803ywb.2 for ; Thu, 05 May 2016 08:07:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :message-id:references:to; bh=U0WZ0wkXotY++pQdsgkBEPR8teLyrFo6IIcLDxgAB7U=; b=Yr7188nt5QkNMkiRslJJu93lzqYYXwS2Z9SXrlbAPWgzxhPq/Psz9G8OoXnpV6SuDH zEKmHFm55z0VulPdOZMRZROgAEWQzxNJMzn8e6agGfszO/bEgIHYZblgi29dATqGmc2b NQdxzJsynsV1uZ/8YG1OmRifshphSO1lem57tl9y4Ee/Ev6KkOuK3iomEm1qntyIi1nN GCj2Gzhi5vS/c2tDJxM/ROwvHVkB39iwRWWhPv/A7GjcFiKzbXaGgEwp4BN2GhdbPADG WOgkYZSBEx2Gj9dQnCxrIEVXbZbEL7XyYO/US4TTXxuNQz1qcDHlyJUPM98A5s5zGf3K fPQg== X-Gm-Message-State: AOPr4FVfYGqCtw9q6pVYt0HylUknsA/ccqSt5K1roMdzBfcVJvbiYAK0TKn/KbzBfWMv5g== X-Received: by 10.129.115.138 with SMTP id o132mr8506248ywc.48.1462460831136; Thu, 05 May 2016 08:07:11 -0700 (PDT) Received: from mike-mbp.japhi.net (cpe-75-183-122-43.triad.res.rr.com. [75.183.122.43]) by smtp.gmail.com with ESMTPSA id l186sm5722466ywe.29.2016.05.05.08.07.09 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 05 May 2016 08:07:09 -0700 (PDT) Subject: Re: EMC DD Boost / Data Domain Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: multipart/alternative; boundary="Apple-Mail=_886602D2-DB1F-4F68-96F7-4B6E8BEE22AC" From: Michael Brown In-Reply-To: Date: Thu, 5 May 2016 11:07:08 -0400 Cc: dbmangler@gmail.com, Listserv Oracle Message-Id: References: To: ebrown2266@gmail.com X-archive-position: 64826 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: dba@michael-brown.org Precedence: normal Reply-To: dba@michael-brown.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l --Apple-Mail=_886602D2-DB1F-4F68-96F7-4B6E8BEE22AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii We had the opposite experience, but we are replicating between two data = domains. We found we had better performance by switching to using rman = to an NFS mount from the Data Domain (type disk instead of sbt). The = impact is that the replication is now independent of the rman backup = (with DD Boost, the backup does not complete until the replication is = complete), the replication still completes at approximately the same = time as it did when the it was through DD Boost, but the rman job in = production completes sooner. =20 After switching to NFS, it is still important to turn off compression = and use one file per set for the data files. My experience has been = that I use less space on the data domain if I compress the archive logs = (and files per set is your choice as well). The reason appears to be = that each archive log is fairly unique, so the data domain is not able = to do much de-duplication on them.=20 =20 > On May 5, 2016, at 10:12 AM, Eric Brown wrote: >=20 >=20 > We switched our backups from writing to the data domain via NFS to = DDBoost and it cut the backup time by about 75%. Everything is managed = natively using RMAN (rman views DDBoost as a SBTTAPE interface). >=20 > We have been quite happy with it. The extra cpu usage during the = backup is offset by the much shorter backup window. >=20 > On Wed, May 4, 2016 at 12:12 PM, Jeff Thomas > wrote: > Our environment is 11.2.0.4 / OEL 6 / RAC. =20 >=20 > Currently we are using Netbackup, compressed incrementals to the FRA, = then backup recovery area to tape. =20 > Our company has purchased the EMC suite of backup tools to replace = Netbackup. >=20 > My understanding is the optimal use of DD Boost/DD is to turn off = compression, set FILESPERSET to 1, skip backups to the FRA; > going directly via the DD Boost module to DD, essentially using DD as = your tacit FRA. >=20 > I would appreciate hearing any experiences with respect to your B/R = strategy using DD Boost / DD. >=20 > Thanks... >=20 >=20 >=20 --Apple-Mail=_886602D2-DB1F-4F68-96F7-4B6E8BEE22AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii We had the opposite experience, but we are replicating = between two data domains.  We found we had better performance by = switching to using rman to an NFS mount from the Data Domain (type = disk instead of sbt).  The impact is that the replication is now = independent of the rman backup (with DD Boost, the backup does not = complete until the replication is complete), the replication still = completes at approximately the same time as it did when the it was = through DD Boost, but the rman job in production completes sooner. =  

After = switching to NFS, it is still important to turn off compression and use = one file per set for the data files.  My experience has been that I = use less space on the data domain if I compress the archive logs (and = files per set is your choice as well).  The reason appears to be = that each archive log is fairly unique, so the data domain is not able = to do much de-duplication on them. 
 

On May 5, 2016, at 10:12 AM, Eric Brown <ebrown2266@gmail.com> wrote:


We switched our backups from writing to the = data domain via NFS to DDBoost and it cut the backup time by about = 75%.  Everything is managed natively using RMAN (rman views DDBoost = as a SBTTAPE interface).

We have been quite happy = with it.   The extra cpu usage during the backup is offset by = the much shorter backup window.

On Wed, May 4, 2016 at = 12:12 PM, Jeff Thomas <dbmangler@gmail.com> wrote:
Our environment is 11.2.0.4 / OEL 6 / RAC.     =  

Currently we are = using Netbackup, compressed incrementals to the FRA, then backup = recovery area to tape.    
Our company has purchased the EMC suite of = backup tools to replace Netbackup.
My understanding is the optimal use of = DD Boost/DD is to turn off compression, set FILESPERSET to 1, skip = backups to the FRA;
going directly via the DD Boost = module to DD, essentially using DD as your tacit FRA.

I would = appreciate hearing any experiences with respect to your B/R strategy = using DD Boost / DD.

Thanks...




= --Apple-Mail=_886602D2-DB1F-4F68-96F7-4B6E8BEE22AC-- -- http://www.freelists.org/webpage/oracle-l