azcopy journal .jnl

%3CLINGO-SUB%20id%3D%22lingo-sub-443662%22%20slang%3D%22en-US%22%3Eazcopy%20journal%20.jnl%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-443662%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20use%20the%20azcopy%20command%20to%20send%20a%20file%20to%20an%20azure.%20The%20command%20generates%20two%20log%20files%3A%20AzCopy.jnl%20and%20AzCopyCheckpoint.jnl.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAre%20these%20%22logs%22%20that%20can%20be%20read%20and%20in%20this%20case%2C%20with%20which%20software%20or%20are%20they%20only%20files%20for%20azcopy%20to%20manage%20its%20transfer%20(status%2C%20recovery%2C...)%20and%20therefore%2C%20not%20intended%20to%20be%20read%20by%20a%20human...%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-443662%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-557104%22%20slang%3D%22en-US%22%3ERe%3A%20azcopy%20journal%20.jnl%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-557104%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319126%22%20target%3D%22_blank%22%3E%40yannBD%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBelow%20is%20from%20the%20Microsoft%20docs%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3ENote%20that%20when%20exporting%20tables%20to%20blobs%2C%20AzCopy%20downloads%20the%20Table%20entities%20to%20local%20temporary%20data%20files%20and%20then%20uploads%20those%20entities%20to%20the%20blob.%20These%20temporary%20data%20files%20are%20put%20into%20the%20journal%20file%20folder%20with%20the%20default%20path%20%22%3C%2FSPAN%3E%25LocalAppData%25%5CMicrosoft%5CAzure%5CAzCopy%3CSPAN%3E%22%2C%20you%20can%20specify%20option%20%2FZ%3A%5Bjournal-file-folder%5D%20to%20change%20the%20journal%20file%20folder%20location%20and%20thus%20change%20the%20temporary%20data%20files%20location.%20The%20temporary%20data%20files'%20size%20is%20decided%20by%20your%20table%20entities'%20size%20and%20the%20size%20you%20specified%20with%20the%20option%20%2FSplitSize%2C%20although%20the%20temporary%20data%20file%20in%20local%20disk%20is%20deleted%20instantly%20once%20it%20has%20been%20uploaded%20to%20the%20blob%2C%20please%20make%20sure%20you%20have%20enough%20local%20disk%20space%20to%20store%20these%20temporary%20data%20files%20before%20they%20are%20deleted.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3ESo%20from%20this%2C%20I%20would%20say%20they%20are%20not%20meant%20to%20be%20read%20by%20a%20human.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Visitor

Hello,


I use the azcopy command to send a file to an azure. The command generates two log files: AzCopy.jnl and AzCopyCheckpoint.jnl.

 

Are these "logs" that can be read and in this case, with which software or are they only files for azcopy to manage its transfer (status, recovery,...) and therefore, not intended to be read by a human...?

 

thanks

1 Reply

@yannBD 

Below is from the Microsoft docs:

 

Note that when exporting tables to blobs, AzCopy downloads the Table entities to local temporary data files and then uploads those entities to the blob. These temporary data files are put into the journal file folder with the default path "%LocalAppData%\Microsoft\Azure\AzCopy", you can specify option /Z:[journal-file-folder] to change the journal file folder location and thus change the temporary data files location. The temporary data files' size is decided by your table entities' size and the size you specified with the option /SplitSize, although the temporary data file in local disk is deleted instantly once it has been uploaded to the blob, please make sure you have enough local disk space to store these temporary data files before they are deleted.

So from this, I would say they are not meant to be read by a human.

 

Hope this helps.