Re: Veritas file locking

thanks Bruce:

1. Veritas Open File Option
2. I refuse to answer the question of backup policy at this time since Im green, inherited this DW environment, and i dont want to fully incriminate myself in the forum.

oh ok. until i can get a better policy in place we just have exports runnkng on the critical tablespaces. told you it was incriminating. As i mentioned, im no expert, but i am quickly becoming the new sheriff. I am planning a Stalinist takeover of the weekend window to begin getting cold backups to a remote directory where they can backup however/whenever they want to their hearts content. We are finally moving to SAN in the next 3 to 6 months which will allow the CPU and disk to implement RMAN.

3) What about causing file corruption in our MV indexes?

On Fri, 25 Feb 2005 09:26:53 +1100, Reardon, Bruce (CALBBAY) <Bruce.Reardon_at_comalco.riotinto.com.au> wrote:
> Yes.
> I've had this happen during setup of new servers - the database will get brought down.
> Are you using the Veritas Oracle agent or the Veritas Open File Option?
> How are you doing your DB backups - is Veritas meant to back up the DB, or are you (eg) doing RMAN to disk and then Veritas of those RMAN files to tape?
>
> Suggestion - have Veritas file backup exclude all the data, redo & control files.
> Some ways to achieve this are to use dedicated dirs or dedicated drives for these files & only these files & then exclude the dir / drive from the OS backup.
>
> Also exclude the Intelligent agent queue files (?\network\agent\*.q) - until this was done we would get Dr Watson errors & the IA service crashing.
>
> HTH,
> Bruce Reardon
>
> -----Original Message-----
> From: Bryan Wells
> Sent: Friday, 25 February 2005 9:20 AM
>
> 9205 DataWarehouse on W2K Advanced Server. Has anyone ever had any
> issues with Veritas running weekend fulls on everything, including
> data files and oracle binaries? would veritas take precedence by
> locking these files for backup, not allowing the db to access them?
>
> We seem to be having this issue. i can see the error in the alert
> log, and correspond it to a rough time that veritas had the specific
> data file locked for backup. im making assumtions, but we believe
> that it is this that brings the DB down. could this hard down cause
> corruption in our MV indexes, especially since they are not being
> rebuilt when the MV is being rebuilt. or does dropping the MV
> recreate the index?
>
> Bryan S Wells - DBA Newbie
> bunjibry_at_gmail.com
>
> NOTICE
> This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments.
> This notice should not be removed.
>

-- 
Bryan S Wells - DBA Newbie
bunjibry_at_gmail.com
--
http://www.freelists.org/webpage/oracle-l