Backups to a remote server

[kimon]

I have a local backup server which is on the same network as all my client notes, and I have a remote backup server which can only communicate with the local backup server.



I want my backups to end up on the remote backup server.



It appears that this can by done using a storage pool which uses a "SERVER" device class.



Are there any restrictions do doing this?



For example, I must guarantee that data from separate nodes must not end up on the same media. I think the only way to do this is to have a separate storage pool for each node (let me know if this is incorrect!). Will I be able to have multiple "SERVER" device classes that point to the same server, but end up in different storage pools?



Looking at "DEFINE DEVCLASS" I am unclear on how to do this, since there does not seem to be a parameter which specifies which device class on the remote end it hooks into.



Thanks for any suggestions,



Kimon

 

[sphynx]

Ok lets start from the beginning....



The local server is a client of the remote server, so you have to set up an account on the remote server for the local server. This account must have a domain specifying the backup/archive copy destination of whatever pool (you want that data stored to). In other words, you must have created a domain with a policyset that has a default management class pointing to the storage pool you desire.



You do not have to guarantee anything!!! I would just created one storage pool (DISKPOOL) must be large on the remote server. The remote server will take care of storing the data. Creating more storage pools will only burden the process.



So local server TSM01 needs to store it's data on a remote server TSM00.



If you have a small diskpool on TSM01 then,



1) Set up server to server communications by specifying the remote server on the local server, under OTHER SERVERS

2)Create a Server Devclass VIRPOOL1 that using SERVER NAME:TSM00

3) Est/Max Capacity (MB)=THE SIZE OF YOUR TOTAL INCREMENTAL BACKUP OF THE LOCAL SERVER's CLIENT DATA

4) Create a Sequential Access Storage pool that's using the new VIRPOOL1 as the migration destination (MAX SCRATCH=500).



In this scenarion. Your data will be stored on the remote server's storage pools (TAPE DISK WHATEVER) and the local server will need the remote server to migrate/restore and copy the Storage pool VIRPOOL1. Another way of doing this would be to have a large enough diskpool that will hold all your client data and then you would just backup the storage pool to the VIRPOOL1. But 4 TERABYTES of disk are expensive.



I hope this helps....

EFH