Hi John, Sounds like you have the right idea to me. Make sure you co-locate the worker process with either your old blob location (which you probably can't do now anyway since I don't think you can create new roles in NW) or with your new blob storage location.
You probably want to store a marker against the ones succesfully migrated so that any failures can be re-tried. Table storage should do this fine (and can be co-located as well). Regards, Steven Nagy Readify | Senior Developer M: +61 404 044 513 | E: steven.n...@readify.net<sip:steven.n...@readify.net> | B: azure.snagy.name<http://azure.snagy.name/> ________________________________ From: ozazure-boun...@lists.codify.com [ozazure-boun...@lists.codify.com] On Behalf Of John OBrien [j...@soulsolutions.com.au] Sent: Tuesday, 3 November 2009 10:20 AM To: ozazure@lists.codify.com Subject: blob to blob copy Hey guys, has anyone written/seen/know how to do a direct blob to blob copy? I need to migrate thousands of little images from the closing NW datacentre to the other datacentre and uploading from Australia took well over 12 hours initially with my upload client failing 3-4 times. I’m thinking a little worker process hosted in azure should be the fastest hey? I did have plans for a little process where i could upload them as a single zip file then decompress into azure but never had time to built it. John.
_______________________________________________ ozazure mailing list ozazure@lists.codify.com http://prdlxvm0001.codify.net/mailman/listinfo/ozazure
