A slower alternative (than copying the files) is to add a connect/addnode in the conf of the new node to point to the existing node. It will then download from your existing node (assuming v0.10). It's easier to set up but the new node will still verify all data again. The advantage is that you can probably leave this config up as you probably don't need to make both nodes available externally. Your new node can just continue to leech of the existing node in future.
Could I will probably do that. But I will also like to have a backup of the blockchain in case something happen and I need to reboot all my setup. Dont want to downlaod 34gb again.
![Tongue](https://bitcointalk.org/Smileys/default/tongue.gif)
The above approach would result in a copy of the blockchain on each pc. The download will mostly be from your existing peer to the new one though, which should speed things up compared to the normal download. It will be slower than copying the folders directly as it would still verify everything again.