[Veritas-bu] Restore SIZE_DATA_BUFFER in mixed OS Environment

I ran a quick test in a NBU 5.0 MP3 environment on Solaris 9 (v210 
attached to Sun L8 w/LTO2 drive).
Note that NUMBER_DATA_BUFFERS and SIZE_DATA_BUFFERS exist in both tests, 
with contents
identical to the _RESTORE files.  I'm not sure that 
SIZE_DATA_BUFFERS_RESTORE is actually used.

Anyways, I didn't see a significant difference in restore speeds with or 
without the _RESTORE files, but it's
also a very simple test environment.  Note that the restore was faster 
(again, insignificantly, I think) without the
_RESTORE files.

Here's a snapshot of the results:

# ls /opt/openv/netbackup/db/config/*RESTORE
/opt/openv/netbackup/db/config/NUMBER_DATA_BUFFERS_RESTORE
/opt/openv/netbackup/db/config/SIZE_DATA_BUFFERS_RESTORE
# cat /opt/openv/netbackup/db/config/*RESTORE
16
262144

<restore initiated>
$ iostat -xn 2
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c0t0d0
    0.0   80.0    0.0 50853.4  0.0  4.6    0.0   57.1   0  98 c0t1d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t0d0
  207.0    0.0 52992.6    0.0  0.0  0.8    0.0    3.9   0  81 rmt/0

# /opt/openv/netbackup/bin/goodies/bp.kill_all
<output snipped>
# rm /opt/openv/netbackup/db/config/*RESTORE
# ls /opt/openv/netbackup/db/config/*RESTORE
/opt/openv/netbackup/db/config/*RESTORE: No such file or directory
# /etc/init.d/netbackup start
Media Manager daemons started.
NetBackup request daemon started.

<restore initiated>
$ iostat -xn 2
                    extended device statistics
    r/s    w/s   kr/s   kw/s wait actv wsvc_t asvc_t  %w  %b device
    0.0    4.5    0.0  478.0  0.0  0.0    0.0    5.8   0   2 c0t0d0
    0.0   89.0    0.0 56671.2  0.0  8.4    0.0   93.9   0  98 c0t1d0
    0.0    0.0    0.0    0.0  0.0  0.0    0.0    0.0   0   0 c2t0d0
  227.0    0.0 58115.3    0.0  0.0  0.9    0.0    3.9   0  89 rmt/0

Here are a couple of articles on [SIZE|NUMBER]_DATA_BUFFERS from 
Veritas' site:
http://seer.support.veritas.com/docs/183702.htm (Explanation/how to 
configure)
http://seer.support.veritas.com/docs/267047.htm (Best Practices)

Dan  Shauver

Scott Jacobson wrote:

>NetBackup Buffer Gurus!
> 
>(My particular situation applies exclusively within a 5.1 Enterprise
>environment).
>
>I have a rather urgent need to validate the below scenario from
>previous NBU comments I've seen in the past.
>
>Scenario - Disaster Recovery:
>
>The Master (W2K SP4) is restored, however, the media servers that wrote
>the data are a Linux OS using SIZE_DATA_BUFFERS" of 256K (262144). 
>Instead rebuilding "Xteen" number of media servers, I'd prefer to just
>rebuild the master server and migrate the data volumes to the master and
>restore from the master.
> 
>I'm not certain if those previous NBU suggestions did or didn't work,
>which I believe went like:
>
>Create a "touch" file(s) for either "RESTORE_SIZE_DATA_BUFFERS" and
>"RESTORE_NUMBER_DATA_BUFFERS" files that would allow or will force the
>restore behavior of data originally backed up by, again, in this case, a
>Linux media server OS configuration to that of being restored by a W2K
>type OS configuration.
> 
>At present, Veritas can't even validate that a
>"RESTORE_anynumber_or_size_BUFFERS" touch file option EVEN EXISTS !!
>Ahhh !!
>
>Can anyone validate that they've done this or can tell me that it a
>"go" or "no go" situation?
>
>Thank you very much, again - a great forum.
>
>Scott J.
> 
>
>_______________________________________________
>Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
>http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>  
>