Onbar Backup?

Onbar Backup?

Post by Venkatesh Konnu » Wed, 09 Jul 2003 22:42:12



Hi,
I am running Level-1 backup on IDS 9.4.UC1 ,SunOS 8.

My question is even though multiplexing is on and set to 8 in the
onconfig as well as on the Netbackup side. (Veritas Storage Manager ),
the Level-0 backups take about 12 Hours to complete for backing up 90
dbspaces.

Each dbspace is about 2 GB in size.

Secondly, when I want to look at stack output for the threads running
the backups, in "onstat -g ath" output, I donot see arcbackup thread but
instead 9 ontape backup threads.
Hence, not able to determine if we are hitting the old
arc_very_old_pages bug.

Moreover, in the infx_db_comm directory under /usr/openv/netbackup...
directory, the output for the storage Manager ID for e.g :does show
that may be even multiplexing is not working:

fsaatdw1 $more infxbsa.1057670308.27198.1
08:18:31 Initiating backup
08:19:27 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:20:12 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:21:01 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:21:53 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:22:37 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:23:22 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:24:06 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:24:50 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:25:35 INF - Waiting in NetBackup scheduler work queue on server
kcax09
08:26:18 INF - Starting bpbrm
08:26:21 INF - Data socket = kcax09.IPC:/tmp/vnetCDVx7a
08:26:21 INF - Name socket = kcax09.IPC:/tmp/vnetCDVx7b
08:26:21 INF - Frozen image = 0
08:26:21 INF - Backup copy = 0
08:26:22 INF - Master server = kcax09
08:26:22 INF - New data socket = kcax09.IPC:/tmp/vnetCr.YEa
08:26:22 INF - Backup id = eclipse_1057670970
08:26:22 INF - Compression = 0
08:26:22 INF - Backup time = 1057670970
08:26:23 INF - Encrypt = 0
08:26:23 INF - Multiplexing = 8                      
08:26:23 INF - Client read timeout = 900
08:26:23 INF - Media mount timeout = 0
08:26:37 INF - Beginning backup on server kcax09 of client eclipse.
08:27:21 INF - Server status = 0
08:27:24 INF - Server status = 0
08:27:28 INF - Backup by informix on client eclipse: the requested
operation was
 successfully completed.                      

Does anybody know to overcome this issue ?

Thanks in advance.
Venaktesh Konnur
sending to informix-list

 
 
 

Onbar Backup?

Post by Brice Avi » Fri, 11 Jul 2003 01:35:58


Venkatesh,

Well, the backup speed is dependant on the type of tape drive you
have. For a DLT7000 you should get about 40-50 GB/hour. Backing-up to
a disk storage unit is the fastest speed you will ever get, so you can
benchmark against this.

The Informix "arc_very_old_page" bug is 101062, fixed in 9.21.UC5. I
doubt that you are running into this, but you can always look at the
stack of the ontape processes and see if you are encountering the
"arc_very_old_page" function. Run "onstat -g ath" and get the session
if of the ontape process, and then run "onstat -g stk <session_id>".

Instead of setting BAR_MAX_BACKUP to 8, set it to zero (unlimited).
Then make a storage group with several tape drives, and set your
Informix policy to this storage group. Do not limit jobs per policy.
Avoid multiplexing . . . though it speeds the backup, it will
drastically slow the restore. If you have a
/usr/openv/netbackup/logs/bptm log of this backup, you can see if the
Informix backup is wating for full buffers (from the Informix
instance) or waiting for empty buffers (the tape library taking the
information from netbackup). You'll aways get a few waits, but if the
number of waits gets into the tens of thousands, it's a concern.

Hope this information helps. Also consider sending this questions to
the veritas newsgroup at "veritas.netbackup.datacenter.english" or
opening a case with Veritas support. Hope this information helps.

Brice Avila
Minneapolis, Minnesota


> Hi,
> I am running Level-1 backup on IDS 9.4.UC1 ,SunOS 8.

> My question is even though multiplexing is on and set to 8 in the
> onconfig as well as on the Netbackup side. (Veritas Storage Manager ),
> the Level-0 backups take about 12 Hours to complete for backing up 90
> dbspaces.

> Each dbspace is about 2 GB in size.

> Secondly, when I want to look at stack output for the threads running
> the backups, in "onstat -g ath" output, I donot see arcbackup thread but
> instead 9 ontape backup threads.
> Hence, not able to determine if we are hitting the old
> arc_very_old_pages bug.

> Moreover, in the infx_db_comm directory under /usr/openv/netbackup...
> directory, the output for the storage Manager ID for e.g :does show
> that may be even multiplexing is not working:

> fsaatdw1 $more infxbsa.1057670308.27198.1
> 08:18:31 Initiating backup
> 08:19:27 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:20:12 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:21:01 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:21:53 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:22:37 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:23:22 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:24:06 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:24:50 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:25:35 INF - Waiting in NetBackup scheduler work queue on server
> kcax09
> 08:26:18 INF - Starting bpbrm
> 08:26:21 INF - Data socket = kcax09.IPC:/tmp/vnetCDVx7a
> 08:26:21 INF - Name socket = kcax09.IPC:/tmp/vnetCDVx7b
> 08:26:21 INF - Frozen image = 0
> 08:26:21 INF - Backup copy = 0
> 08:26:22 INF - Master server = kcax09
> 08:26:22 INF - New data socket = kcax09.IPC:/tmp/vnetCr.YEa
> 08:26:22 INF - Backup id = eclipse_1057670970
> 08:26:22 INF - Compression = 0
> 08:26:22 INF - Backup time = 1057670970
> 08:26:23 INF - Encrypt = 0
> 08:26:23 INF - Multiplexing = 8                      
> 08:26:23 INF - Client read timeout = 900
> 08:26:23 INF - Media mount timeout = 0
> 08:26:37 INF - Beginning backup on server kcax09 of client eclipse.
> 08:27:21 INF - Server status = 0
> 08:27:24 INF - Server status = 0
> 08:27:28 INF - Backup by informix on client eclipse: the requested
> operation was
>  successfully completed.                      

> Does anybody know to overcome this issue ?

> Thanks in advance.
> Venaktesh Konnur
> sending to informix-list


 
 
 

Onbar Backup?

Post by Brice Avi » Fri, 11 Jul 2003 23:59:41


Venkatesh,

Learned that Informix 9.4 isn't on the support matrix for any version
of NetBackup yet. It still should work, but watch out trying to take
advantage of the new 9.4 features, i.e. backing-up dbspaces > 2GB.

From the progress file you showed, it could be something as simple as
the backup waiting for an available drive (try staggering the
backups). But it only waited about 6 minutes, and the whole backup of
this object is 10 minutes. Is this a logical log backup? It doesn't
illustrate you 12 hour dbspace backup.

Hope this helps again.

Brice Avila
Minneapolis, Minnesota


> Venkatesh,

> Well, the backup speed is dependant on the type of tape drive you
> have. For a DLT7000 you should get about 40-50 GB/hour. Backing-up to
> a disk storage unit is the fastest speed you will ever get, so you can
> benchmark against this.

> The Informix "arc_very_old_page" bug is 101062, fixed in 9.21.UC5. I
> doubt that you are running into this, but you can always look at the
> stack of the ontape processes and see if you are encountering the
> "arc_very_old_page" function. Run "onstat -g ath" and get the session
> if of the ontape process, and then run "onstat -g stk <session_id>".

> Instead of setting BAR_MAX_BACKUP to 8, set it to zero (unlimited).
> Then make a storage group with several tape drives, and set your
> Informix policy to this storage group. Do not limit jobs per policy.
> Avoid multiplexing . . . though it speeds the backup, it will
> drastically slow the restore. If you have a
> /usr/openv/netbackup/logs/bptm log of this backup, you can see if the
> Informix backup is wating for full buffers (from the Informix
> instance) or waiting for empty buffers (the tape library taking the
> information from netbackup). You'll aways get a few waits, but if the
> number of waits gets into the tens of thousands, it's a concern.

> Hope this information helps. Also consider sending this questions to
> the veritas newsgroup at "veritas.netbackup.datacenter.english" or
> opening a case with Veritas support. Hope this information helps.

> Brice Avila
> Minneapolis, Minnesota


> > Hi,
> > I am running Level-1 backup on IDS 9.4.UC1 ,SunOS 8.

> > My question is even though multiplexing is on and set to 8 in the
> > onconfig as well as on the Netbackup side. (Veritas Storage Manager ),
> > the Level-0 backups take about 12 Hours to complete for backing up 90
> > dbspaces.

> > Each dbspace is about 2 GB in size.

> > Secondly, when I want to look at stack output for the threads running
> > the backups, in "onstat -g ath" output, I donot see arcbackup thread but
> > instead 9 ontape backup threads.
> > Hence, not able to determine if we are hitting the old
> > arc_very_old_pages bug.

> > Moreover, in the infx_db_comm directory under /usr/openv/netbackup...
> > directory, the output for the storage Manager ID for e.g :does show
> > that may be even multiplexing is not working:

> > fsaatdw1 $more infxbsa.1057670308.27198.1
> > 08:18:31 Initiating backup
> > 08:19:27 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:20:12 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:21:01 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:21:53 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:22:37 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:23:22 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:24:06 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:24:50 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:25:35 INF - Waiting in NetBackup scheduler work queue on server
> > kcax09
> > 08:26:18 INF - Starting bpbrm
> > 08:26:21 INF - Data socket = kcax09.IPC:/tmp/vnetCDVx7a
> > 08:26:21 INF - Name socket = kcax09.IPC:/tmp/vnetCDVx7b
> > 08:26:21 INF - Frozen image = 0
> > 08:26:21 INF - Backup copy = 0
> > 08:26:22 INF - Master server = kcax09
> > 08:26:22 INF - New data socket = kcax09.IPC:/tmp/vnetCr.YEa
> > 08:26:22 INF - Backup id = eclipse_1057670970
> > 08:26:22 INF - Compression = 0
> > 08:26:22 INF - Backup time = 1057670970
> > 08:26:23 INF - Encrypt = 0
> > 08:26:23 INF - Multiplexing = 8                      
> > 08:26:23 INF - Client read timeout = 900
> > 08:26:23 INF - Media mount timeout = 0
> > 08:26:37 INF - Beginning backup on server kcax09 of client eclipse.
> > 08:27:21 INF - Server status = 0
> > 08:27:24 INF - Server status = 0
> > 08:27:28 INF - Backup by informix on client eclipse: the requested
> > operation was
> >  successfully completed.                      

> > Does anybody know to overcome this issue ?

> > Thanks in advance.
> > Venaktesh Konnur
> > sending to informix-list

 
 
 

1. Informix onbar backup/restore with Veritas NetBackup

Hi,

the installation is the following:

AIX 4.3.3
Informix 7.31
NetBackup 4.5 Informix client on AIX machine

NetBackup 4.5 Backup server/Media Server on Windows 2000

Problem:
The NetBackup documentation says that int htis case the restore has to be
started from the client (= AIX machine).
Q: How can I select which version of several generations I want to restore?

The NetBackup documentation refers to a "bplist" command and its man pages
Q: On a client only machine no NetBackup man pages are installed. How do I
know what the 27 flags of bplist mean?

Has someone a running configuration like this and can give me some hints?

Many thanks in advance and best regards

Helmut Leininger
Bull AG Austria

2. Domino AS/400 DB2 Performance Issues

3. onbar backup problem

4. getting metainfo

5. sbu 6.0.1 / onbar (Backup sometimes fails)

6. Fetching results by PvQuery

7. ONBAR Backup-restore issue.....

8. What is file# == 0 in v$backup_datafile?

9. Onbar Backup/Restore

10. onbar backup with 7.31

11. IDS 7.31 for WINT40 onbar backup continous logicl logs don't work

12. ONBAR backups.....

13. ISM message during onbar backup