Changes between Version 1 and Version 2 of MinidvodbCopy

Timestamp:

Nov 23, 2010, 4:30:30 PM (16 years ago)

Author:

bills

Comment:

--

MinidvodbCopy

@@ -16 +16 @@
 }}}
 
-This will queue up all the minidvodbs in 'merge' state, will copy them to /data/ipp022.0/minidvodbs/ThreePi.V1.Mini on ipp022(2). Note that we are using ipp0222 in order for the transfer to work. Also note that ipp004 must be able to ssh/rsync to ipp022 without a password. There are checks on this for each minidvodb queued (there must be 97% or less used, and there must be enough space to transfer the minidvodb onto the host). This is similar to the queueing mechanism for creating dvodbs - it will only queue minidvodbs that have not been queued yet for ipp022(2), there should only be 1 copy of a minidvodb on a machine. 
+This will queue up all the minidvodbs in 'merged' state, will copy them to /data/ipp022.0/minidvodbs/ThreePi.V1.Mini on ipp022(2). Note that we are using ipp0222 in order for the transfer to work. Also note that ipp004 must be able to ssh/rsync to ipp022 without a password. There are checks on this for each minidvodb queued (there must be 97% or less used, and there must be enough space to transfer the minidvodb onto the host). This is similar to the queueing mechanism for creating dvodbs - it will only queue minidvodbs that have not been queued yet for ipp022(2), there should only be 1 copy of a minidvodb on a machine. 
 
 Then, you need to tell pantasks which hosts you want to turn on the transfer - this is a bit like adding labels to determine what is processed: