If backup time is that critical you could store them in the same database using a dedicated tablespace for the LOB data. Then exclude that tablespace from your standard backup and create a backup process to backup the LOB tablespace. To exclude the tablespace use the following RMAN command "CONFIGURE EXCLUDE FOR TABLESPACE <LOB TABLESPACE NAME>; Brent On Tue, Jan 17, 2012 at 11:47 AM, Jeff Chirco <JChirco@xxxxxxxxxx> wrote: > We are working on an application that will store images, well actualy > pdf's in our database. We are debating on storing the blobs in our main > production database or creating a separate database just for these images. > We have applications running on our main production database that will > need to pull these across to display. I am thinking a second database is > the best idea since this database will get rather large very quickly and I > don't want to slow down the backup of my main production database. Does > anybody else do something similar to this and can provide your experiences. > We are running 11.2.0.2 Enterprise Edition on Windows Server 20003 R2, > soon to be 2008. > Thanks. > > -- > //www.freelists.org/webpage/oracle-l > > > -- //www.freelists.org/webpage/oracle-l