Re: Arcserve restore of Oracle database

"cooljigs" <egypt11_at_hotmail.com> wrote in message news:28779312.0306211003.60260f5a_at_posting.google.com...
> Sybrand Bakker <gooiditweg_at_sybrandb.demon.nl> wrote in message
news:<7ci1ev0if924t8bfpt0vl085klh5uadcoh_at_4ax.com>...
> > On 6 Jun 2003 04:04:47 -0700, loadofcr_ap_at_yahoo.com (gOD) wrote:
> >
> > >Hello,
> > >
> > >Our company made the mistake of using Arcserve for Oracle backups and
> > >now I am paying the price.
> > >
> > >I have built a new (W2K) server, installed Oracle, installed Arcserve
> > >(and db agent) and am trying to do a restore. When I do a restore, it
> > >asks for a password and user ID. I have tried the local admin account,
> > >tried a domain admin account, tried INTERNAL, tried SYS, and SYSTEM.
> > >None work. It always returns an E8601 error saying "Invalid username
> > >or password".
> > >
> > >Has anyone managed to get this to work?
> > >
> > >Cheers
> >
> > I agree with your sentiments about Arcserve. I have never seen a
> > product with such lousy documentation and with such misleading errors.
> > I have been working on configuring the backup for more than a week,
> > and YES: I did read all the manuals, I did investigate the complete
> > and LOUSY Computer Associates Support sites, I noticed they rename
> > their crap with every new release, I noticed I still don't get RMAN
> > support working.
> > Frankly it has been quite a frustrating experience. I managed to get
> > the Oracle 7 Agent working after reading the *German* manual, which is
> > floating around somewhere on the CA site in pdf format.
> >
> > My restore should be conducted next week.
> >
> > A few things to note:
> > - The account you are using MUST have SYSDBA privilege.
> > - you seem to MUST use sqlnet.authentication_services=(nts) in
> > sqlnet.ora
> > - there is a debug parameter in the registry under the dbaora7@<SID>
> > key. Change that in 1, and you will get an useful tracefile in the
> > home directory of the Oracle Agent.
> > - The LOG_ARCHIVE_DEST parameter is ignored, to whatever you set it.
> > You MUST use log_archive_dest_1 or _2 or _3 or _4 or _5
> > - No error at all is shown. Chances are your backup is succesful, and
> > you won't even notice you didn't backup the database unless you read
> > the logs.
> >
> > As we are fellow victims in the same situation I would be happy to
> > work together to get this piece of shit operational.
> > Oh yes: Somehow some SYSADMIN decided the Arcserve copy on the
> > database has to backup the rest of the network. The Arcserve database
> > is now 2.95 G and the C drive some 8G. The said SYSADMIN doesn't
> > understand why you can't use a database server as a network backup
> > server.
> >
> > Life sometimes really sucks.
> >
> > Regards
> >
> >
> > Sybrand Bakker, Senior Oracle DBA
> >
> > To reply remove -verwijderdit from my e-mail address
>
> Thanks for your posts. It is very informative. I however am just
> trying this out on our lab network which contains almost the same
> infrastructure as our production network.
>
> What I want to do though is much simpler - I want to NOT use Oracle
> backup agents. I simply want to use Arcserve 9's Universal Client
> Agent so I can perform a complete OS-level backup with Disaster
> Recovery. A separate Oracle backup is performed on the server itself
> using Oracle scripts (this is not my area so I can't provide detailed
> info). The restore is 2 parts - the OS-level restore and then the
> restore from the Oracle backup.
>
> The trouble is, as soon as I do a remote install of the Universal
> Client Agent for Windows, I can no longer start Oracle even though all
> the Oracle-related services are supposedly running.
>
> I have Oracle 9i on a Win2K Std. Server with SP3. Any help on this
> would be appreciated.
>
> By the way, during the remote install, Arcserve automatically selects
> the Oracle agents in addition to the Universal Client agent. I simply
> de-selected the Oracle agents since I did not want to install them.

I'm not sure whether this approach is advisable. First of all: your O/S backup will be worthless, as it is conducted on an *open* database. You will answer your scripts will be responsible for the Oracle backup, but stil you will be in the situation where you backup a substantial part of the disks *2* times, where the O/S backup will be worthlesss. I would simply refuse to do this. The Arcserve product should work, building own scripts would cost more than the price the Arcserve agent, they won't be tightly integrated, there won't be any backup history etc , etc. and I expect this will also be less reliable. In short: your approach stinks.

'No longer start Oracle' The problem with such a blank statement is you only state 'It doesn't work' and people here should look in their crystall ball, where you so far failed to do the obvious

- check the eventlog
- check oradim.log
- check the alert log of the instance.

-- 
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address