DB2 Transaction Logs - can they be COPY-PASTE on another Disaster Recovery Server? We have Server1 with Online Backup1, Archive Logs 1,2,3 for example and Transaction Logs from  1 to 10.
We are interested in next scenario:
If Server1 fails completely and we want to move everything on second server I suppose it is not the problem to move and restore Backup1 and Archive logs 1,2,3 on Server2.
But can Transaction Logs (their snapshot in some specific time) be also copied to the Server2? Because Transaction Logs are probably the most problematic part for this Disaster Recovery Scenario. Can there be some problem with the fact that transaction logs are written and populated all the time?

ADDITION: DISK option is used when configuring Archive Mode
Perhaps you wish to look into HADR on DB2. It actually does log shipping to the standby, so if there is a fail over you can either manually take over on the standby, or if you install TSA (Tivoli Systems Automation), then you can have it detect a failure and automatically fail over to the standby.

If you don't want HADR, then yes, you could copy logs. Or even use the alternate/mirror log/archive parameters to get DB2 to copy the logs (possibly to a shared mount).