________________________________ From: Nico Kadel-Garcia Sent: Thursday, 22 August 2013 8:10 AM I would never do a transfer like this without a copy of the dumpfile available, for reference. The pain of having to re-run the dump later, especially if there are any bugs in the "svnadmin load" configuration, normally justifies keeping the dump around until well after the migraiton is completed. Hi Nico,
I'm keeping the original BDB repositories, with read-only permissions. If I really have the need, I can restart Apache 2 with SVN 1.2.3 and go back to the original repositories. Otherwise, I also have the option of re-running my batch file (modifying it if absolutely required). On top of that, there are bunches of files on another server that give us at least the latest state of the projects. The dump files in this case are not really as useful as the data itself. Regards, Geoff -- Apologies for the auto-generated legal boilerplate added by our IT department: - The contents of this email, and any attachments, are strictly private and confidential. - It may contain legally privileged or sensitive information and is intended solely for the individual or entity to which it is addressed. - Only the intended recipient may review, reproduce, retransmit, disclose, disseminate or otherwise use or take action in reliance upon the information contained in this email and any attachments, with the permission of Australian Arrow Pty. Ltd. - If you have received this communication in error, please reply to the sender immediately and promptly delete the email and attachments, together with any copies, from all computers. - It is your responsibility to scan this communication and any attached files for computer viruses and other defects and we recommend that it be subjected to your virus checking procedures prior to use. - Australian Arrow Pty. Ltd. does not accept liability for any loss or damage of any nature, howsoever caused, which may result directly or indirectly from this communication or any attached files.
