On Server A, you catalog the Server B as:
DB2 CATALOG TCPIP NODE serverB REMOTE <what resolves to its IP address>
SERVER <its listening entry port>
On Server A, you backup your db to some Target.
On Server A, you : DB2 ATTACH TO serverB user .... using .....
On Server A, you: DB2 RESTORE DB <dbanme> FROM Target
If you "stay" on Server A, you need to attach to the remote instance
that holds your QA system.
HTH, Pierre.
Yasaswi Pulavarti wrote:
Let us assume "ServerA" is the production DB2 node and "ServerB" is
the QA DB2 node. Then do I do "catalog tcpip node ..." on ServerA or
on ServerB?
The reason I say this is when I run "db2 restore db productiondb..." I
need to be connected to the target instance, but then if I catalog the
qa instance on production server then when running db2 restore, the
production server will be overloaded right? Please help.
Thanks,
Yasaswi
"Jan M. Nelken" <Un**********@Invalid.Domain> wrote in message news:<fo********************@rogers.com>...
Yasaswi Pulavarti wrote:
I have three instances with a database each on a production server. I
need to replicate the databases on a qa server once a week. I
installed administration client on qa server. How do I go about
replicating the production databases on to the qa server.
Please help.
Yasaswi
Backup/Restore ?
Jan M. Nelken
--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.