Re: database decommission checklist

yeah, and of course that data doesn't exist in spreadsheets, presentations,
emails and filing cabinets either! There's a reason that companies that are
serious about data rivacy and retention employ people on high salaries to
think about, legislate and audit on  this stuff and don't just run shred or
whatever on the production disks.

Niall

On Tue, Jun 30, 2009 at 7:03 PM, Matthew Zito <mzito@xxxxxxxxxxx> wrote:

>  Thanks for the reiteration, Jared.  And just to continue along those
> lines, don’t forget BCVs or snapshots, tape backups, etc. etc.  If you have
> a real need to destroy data, you’ll want to get your storage admins
> involved, talk to your vendors, and potentially even purchase a dedicated
> solution for data cleansing.
>
>
>
> These days, a simple rm or even a shred is unlikely to really remove your
> data everywhere.
>
>
>
> Matt
>
>
>  ------------------------------
>
> *From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
> oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Jared Still
> *Sent:* Tuesday, June 30, 2009 1:09 PM
> *To:* QuijadJC@xxxxxxxxxxxxxxx
> *Cc:* oracle-l@xxxxxxxxxxxxx
> *Subject:* Re: database decommission checklist
>
>
>
>
>
> On Tue, Jun 30, 2009 at 6:40 AM, QuijadaReina, Julio C <
> QuijadJC@xxxxxxxxxxxxxxx> wrote:
>
> On Linux, you can use a tool called ‘shred’. It will repeatedly write 25
> times over on the disk. Make it a little harder to recover data if that is
> your intent.
>
> Just to re-iterate what Matt Zito already stated:
>
>
>
> That won't work on some storage systems.
>
>
>
> In particular it will not work on NetApp, and there may be others.
>
>
>
> Jared
>
>
>



-- 
Niall Litchfield
Oracle DBA
http://www.orawin.info

Other related posts: