Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Bin Zhu's onbar backup with NetBackup (onbar -b -w) failed to restore with onbar -r -p. Claus Samuelsen and Brice advised restoring with onbar -r -w (or -r -p -w), not leaving LTAPEDEV as /dev/null, and noted cold restore can overwrite a damaged database. Bin's log showed 'could not fork server connection, SQLCODE -25596'; Valeriy Kravchuk said INFORMIXSERVER must match a sqlhosts entry. Cause identified, final result not reported.
Bin Zhu — — source: Usenet: comp.databases.informix
Hi,
I am using Informix netbackup agent for backup and restore.
The backup is done by using onbar -b -w
However the restore failed by onbar -r -p or onbar -r -p -w.
Is it LTAPDEV and TAPEDEV set to /dev/null causing the problem?
Do I need to delete or "damage" the database before I do a restore?
Any comment will be appreicated.
Thanks
Bin
Bin Zhu wrote:
> Hi,
>
> I am using Informix netbackup agent for backup and restore.
>
> The backup is done by using onbar -b -w
>
> However the restore failed by onbar -r -p or onbar -r -p -w.
>
When backing up with "onbar -b -w" you should do the restore using
"onbar -r -w".
The "-p" options means physical only and will probably leave the
database in recovery mode.
> Is it LTAPDEV and TAPEDEV set to /dev/null causing the problem?
>
When using onbar for backup LTAPEDEV should NOT be set to /dev/null as
logical log files will never be backed up.
> Do I need to delete or "damage" the database before I do a restore?
If you want to do a cold restore IDS should be offline (but onbar can
handle that).
If you want to do a warm restore IDS must be online.
>
> Any comment will be appreicated.
>
> Thanks
>
> Bin
>
>
>
>
>
What is the BAR_ACT_LOG errors that you recieved? What are the
errors/warnings in the "/usr/openv/netbackup/logs/infxbsa/log.<date>"
file?
1. If you backup using "onbar -b -w", you should restore using either
"onbar -r -w" or "onbar -r -p -w".
2. LTAPEDEV should not bet set to /dev/null
3. You can cold-restore over a damaged database. One should not warm
restore over a damaged database.
Hope this helps.
Brice Avila
Bin Zhu wrote:
> Hi,
>
> I am using Informix netbackup agent for backup and restore.
>
> The backup is done by using onbar -b -w
>
> However the restore failed by onbar -r -p or onbar -r -p -w.
>
> Is it LTAPDEV and TAPEDEV set to /dev/null causing the problem?
>
> Do I need to delete or "damage" the database before I do a restore?
>
> Any comment will be appreicated.
>
> Thanks
>
> Bin
↪ replying to Brice
Bin Zhu — — source: Usenet: comp.databases.informix
Thanks for the help,
I check activity log, it says:
2005-06-16 18:57:58 13215 13213 /opt/informix/bin/onbar_d -r -w
2005-06-16 18:57:59 13215 13213 Working with veritas-netbackup as generic
stor
age manager.
2005-06-16 18:58:00 13215 13213 Successfully connected to Storage Manager.
2005-06-16 19:01:00 13215 13213 Begin salvage for log 2.
2005-06-16 19:01:43 13215 13213 Completed salvage of logical log 2.
2005-06-16 19:01:48 13215 13213 Successfully connected to Storage Manager.
2005-06-16 19:01:58 13215 13213 Begin cold level 0 restore rootdbs
(Storage Ma
nager copy ID: 1 1118961048).
2005-06-16 19:04:24 13215 13213 Unable to write storage space restore data
to
the database server: could not fork server connection, SQLCODE -25596.
2005-06-16 19:04:24 13215 13213 Skipped backup/restore of space 'rootdbs'.
d. Aborting XBSA session. 13213 XBSA Error: (BSAEndData) A system error
occurr
l not be attempted.4 13215 13213 Due to the previous error, logical restore
wil
2005-06-16 19:04:54 13215 13213 /opt/informix/bin/onbar_d complete,
returning
3 (0x03)
Regards,
Bin
"Brice" <briceavila@hotmail.com> wrote in message
news:1118765268.272948.256050@g47g2000cwa.googlegroups.com...
> What is the BAR_ACT_LOG errors that you recieved? What are the
> errors/warnings in the "/usr/openv/netbackup/logs/infxbsa/log.<date>"
> file?
>
> 1. If you backup using "onbar -b -w", you should restore using either
> "onbar -r -w" or "onbar -r -p -w".
>
> 2. LTAPEDEV should not bet set to /dev/null
>
> 3. You can cold-restore over a damaged database. One should not warm
> restore over a damaged database.
>
> Hope this helps.
>
> Brice Avila
>
> Bin Zhu wrote:
> > Hi,
> >
> > I am using Informix netbackup agent for backup and restore.
> >
> > The backup is done by using onbar -b -w
> >
> > However the restore failed by onbar -r -p or onbar -r -p -w.
> >
> > Is it LTAPDEV and TAPEDEV set to /dev/null causing the problem?
> >
> > Do I need to delete or "damage" the database before I do a restore?
> >
> > Any comment will be appreicated.
> >
> > Thanks
> >
> > Bin
>
You have to set correct value for the INFORMIXSERVER environment variable or
check the sqlhosts file content.
Here is the quote forme the finderr -25596:
------
The INFORMIXSERVER value is not listed in the sqlhosts file or the
Registry.
The default database server name that the INFORMIXSERVER environment
variable specifies must be a valid database server name in the file
$INFORMIXDIR/etc/sqlhosts on UNIX or the registry on Windows. Check that the
specified server is listed in the sqlhosts file or the registry.
------
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.