Depending on NetBackup version, I don't think it is (I know we can't
do it at our version).  Create InstA on ServerB and restore to that.
Then you can use db2relocatedb to move the database over to InstB.

/T

I have DB2 9.1 LUW on Solaris 10.
I have Netbackup 6.0 MP4  (maybe MP5, not sure, I am not netbackup
admin).

I have completed a physical restore of the database much like you
desire (netbackup alternate client restore):
ServerA:InstA:DB1 ---> ServerB:InstB:DB1   (with rename to DBx)

I have not yet successfully rolled forward logs/transactions in this
scenario, but i will be getting a test server soon to continue to work
through this.  in short, you can do it, but it is not easy, nor is it
straight forward.  it was easy/straight forward with informix, but
that's a diff story.

do you have a process for a DB2 restore "redirected restore" in this
scenario from a filesystem?
if you can make it work without netbackup in the equation, that is the
proof you can give netbackup support and they have the responsibility
to help you if you are paying for support and netbackup-db2 licenses.

when we take NetB out of the equation and use a filesytem for the
backup image, we have to make the backup image perms wide-open (777)
otherwise InstB can't get the backup.  in this same vein, netbackup
expects instB to be in the same PRIMARY UNIX group as instA.  (we run
SAP and that is not how SAP has us set our user accounts).  We finally
got a process to work around this restriction (is it a netbackup or
DB2 restriction i am not sure... i have only 4 months of exp on DB2).

you may need a ticket with netbackup support and db2 support ... so
they don't point fingers at each other and leave you sitting in the
middle ;)

so far the guy helping me on my netbackup ticket has been very good,
it is dragging on and on because i don't have a test server dedicated
to this.  and my DB2 contacts have provided some good "work around"
docs.

good luck,
Norma Jean