Data Loss Prevention

Hello All,

I am planning ro migrate to DLP 14.0 from 12.5.

So i was thinking about the External storage for incident attachements feature. have few questions regarding the same

1. How the metadata is maintained when we are migrating existing incidents to new external storage??

2. When my primary DB is down how the external storage is link to the backup DB(secondary DB)?? Any configuratio we have to do and how its manage?

3. What kind of storage is full proof?? NFS or other

4. When external stoarge is crashed how we can restore it?? hot backup is possible??

Awaiting your help on these question guys.

1. How the metadata is maintained when we are migrating existing incidents to new external storage??

  There is no migration of existing incidents in the database to external storage. When you turn on external storage only new incidents will be stored on the file system. Should you decide to go back to storage into the DB there is no way to insert the external storage.

2. When my primary DB is down how the external storage is link to the backup DB(secondary DB)?? Any configuratio we have to do and how its manage?

  In order to fail over you would need the external storage to be available to both the primary and backup systems. This could be accomplished via load balancing or a system such as DFS. It should be noted that using multiple databases is beyond the scope of the DLP Admin guide and relies solely on your own Oracle DBAs.

3. What kind of storage is full proof?? NFS or other

No storage is fool proof however most SANS offer some sort of redundancy and checks such as CRC

4. When external stoarge is crashed how we can restore it?? hot backup is possible??

Restore using normal file backup procedures. As long as you restore it to the same directory as where you initially had the data it will be fine.

Thanks for your response John,

Coluld you please let me know the significance advantages of moving to external storage othe than DB size.

Since my management is asking just for space miggrating is not good enough whether any performance will be enhance from this in DB or other related tools DLP-

What are the key points u should tell to explain this external storage solution??

Regards,

Ram

The main reasons for using external storage is for space on Oracle and enhanced performance. In larger customers that have multiple instances on their Oracle farm it helps to move non critical data out of the database cluster. It also has a performance boost in that the things the incident data ,i.e. the middle pane of an incident in the console, you only really need that when viewing a particular incident and is not indexed. That leaves things easy to index (and thus smaller indexes overall) in the database which results in a performance boost as well. Since we are putting less into the database it also has the side effect of making incident processing faster as when Enforce gets the incident it is already on disk so it becomes a file move rather than a database insert. Another advantage of putting less into the database overall is that reduces the chances of database corruption which is more likely as a database grows.

Thank you so much for this information John Sir.

Currently in my environment enforce DB is 11 TB size so they are managing like any supporting documents as a large object in DB.

So DB is growing drastically so how can i provide the solution on this.

Kindly advise the solution i can give to my management for this.

Ramchandra,

Just as an FYI.. I know there are some issues with the External storage aspect for the new release... they may or may not effect you.

I would contact Support to understand the issue with it before moving forward.. 

I wold also ask why is the DB so large.. what are you capturing for incidents and how long are you keeping all of the incidents.

Keep in mind that there should also be a data retention strategy on how long to keep all of the incidents and deleting thos that are not neeed. This is could from a data clean up issue as well as a legal data retenion issue.

Thanks

Ronak

PLEASE MARKED SOLVED WHERE POSSIBLE

Hello Ronak,

Could you please let me know how the metadata will be maintained when the new incidents attachents will be stoared in external storage??

Since ideally it sholud not change when we are storing incident attachment.

For new incidents metadata i.e who has accessed? when ? owener? should not modify when storing in external storage.

Any confirmation on this

Regards,

Ram

Anyone can help me on above mentioned scenarios??

Ram,

When you ask about Meta Data.. hat are you talking about?

When the DLP system stores the attachments outside the DB it will use the same ACL properties as if it was a File system.

I would assume (I do not know) that the folder stucture will either have the files renamed to have an identifiable name or it will have the same original name of the file and be segmented by Incident number or another identifiable name for the folders.

As far as who has accessed the file or modified it.. will still happen, since it is on a File system. I do not know how it will work for ACL and other accesses records..

I have not used the EXTERNAL stroage of attachments before.. and do not plan on it.

I would contact SYMC support or worst case.. just try it out!

Good Luck,

Ronak

PLEASE MARKED SOLVED WHERE POSSIBLE