Solved Image your system with free Macrium

[ignatzatsonic]

Ignat -- Rogerthat wrote "software STOPS when it finds a file-name that is too long (over 18 letters on this Windows 7 x64 Ultimate laptop."

=======================
Isn't the file length 256? Why would the backup stop after 18 characters? Eighteen doesn't sound right to me.

My backup software will not back up a particular file if the path to that file (including the name itself) is over 255 characters. The file name length does not matter, by itself.

But my backup software will NOT stop at that file. It will skip it and continue to back up all files whose paths are no more than 255 characters in length. I can then look in the log and see which files were not backed up.

I have no idea what software he is using, but there are clearly programs that do not STOP. I use one of them.

Likewise, if his software stops at 18 character file names per se, he's using bogus software. I've never even heard of software that will balk at anything other than full path length of 256 or more characters--and even then it should skip rather than stop.

It may be that his files are in a deeply nested folder that itself is circa 237 characters in path length. In that case, an 18 character file name would succeed (255 character total path length) and a 19 character file name would fail (256 character total path length).

 

[bigmck]

Thanks for the info.

 

[rogerthat]

You say a "small percentage" of your file names prevent a backup.

If nothing else, I'd do this:

Run a non-image backup tool such as Karen's Replicator or Synctoy. It should run to completion, copying all the shorter file names, and failing to backup the long ones.

Will do.

Then look in the log file to identify the failed files.

Then put those failed files in a separate directory and exclude that directory from future backups since you know the files will fail. Then either rename them or possibly use a command prompt to copy them using their 8 dot 3 name. At least that way you have a backup, even if the names are shortened from 255 plus characters.

The problem is that to find files (where I have hundreds of thousands); the only way I can think of, of finding them, is to have a descriptive file folder and descriptive file folder contents and descriptive files-names. That job of pulling files out of directories and re-naming each one would take forever. It would break my understanding of how to find a specific file. :huh:

Wondering how you ever got in the habit of using extremely long names?

I guess having files I do not know where to find; e.g. having a short time to find an important legal file, which relates to a specific part of a case; or when trying to find a piece of conceptual design file for a specific image; requires that I have the most information I can to dig through maybe half-a-million files of various types.
I don`t have the lifespan to search one-by-one.

Is the problem the length of the file name per se, or is it the length of the path to the folder in question?

Length of the Path ALSO. EXACTLY. Nail on the head.

I've had maybe 5 instances of files failing to backup due to path length, but I resolved it by either shortening the name per se or changing the path to something closer to the root.

I have had thousands.

N.B.
I have a concept on how to get a programmer to write a program to prevent files from being made too long (including directory names); and today wrote to a software company to move that one forward.
icnic: Maybe even have a 64Gb USB `program` that collects copies of selected file types automatically when you save in Word or whatever program you select....I would need a lot of them and some way to catalog them. CD/DVD Discs get sat-on or scratched or sometimes just fail.
P.S.
Most of my files are WORD (2010/ Word 2007 Word 2000) files, JPEG/RAW images and AVCHD (+MPEG etc) video files and WAV/MP3 sound files etc.
Some documents are within files, that are within files, that are within briefcases etc.
LONG PATH, over the limit.

P.P.S.
I found it interesting the way opening a laptop Windows 7 x64 Word 2010 document in Word 2000 on my XP desktop used to smash my documents to pieces when it auto-saved.
But eventually microsoft fixed that glitch; in my case, only after I lost two-to-three hundred hours work.

 

[lehnerus2000]

I agree with ignatzatsonic's hypothesis.

I have experienced similar problems.
I think it was when I tried accessing files on Network Shares that weren't mapped to a drive letter.

for example:
​

\\pjl-w7-sp1-64\<path>
vs
Z:\<path>

That said, I thought I read an article about how to change the maximum path length to a much higher value (32767 characters?).
​

 

[ignatzatsonic]

Here are some ideas:

There are excellent search tools that can produce a list of file names containing a certain search string very quickly---typically in a second; presumably a bit longer in your case if you have hundreds of thousands.

One such search tool is Everything, from voidtools.com. It is free. It searches file names or partial file names ONLY, not file contents.

To give you an idea, I just typed "and doc" into Everything. It coughed up 298 files in less than 1 second. All of them contain "and doc" somewhere in the file name. Most of them are Word files, found due to the "doc".

I then tried "and docx" and the list immediately shrunk to 75, representing Word files with a docx extension.

Secondly--and you apparently rejected this years ago:

If you have a file that contains roast beef recipes, name it "roast beef" and put it in D:\recipes. Rather than naming it "here is a file that contains some pretty cool pictures I took while on vacation and also some food related stuff" and putting it in D:\users\yourusername\stuff\food-related\cooking\recipes.

I have tens of thousands of files---I'd guess no more than 100 have file names per se that are more than 50 characters. I can get away with that because of my folder structure, which is often 5 folders deep.

So, I might have this path:

D:\pix\vacation\1998\Vegas\RollingStones

and in that a file named "Mick Jagger grinning.jpg". Total path length maybe 50 characters.

Effectively, most of the "naming" is done by the path, rather than a file name such as "Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff, where there might be 50,000 pictures with no further categorization.

If I am looking for Jagger pictures and can't recall the year I saw the Rolling Stones in Las Vegas, I use the Everything search engine to ID the path, and then either navigate to the folder manually or pop the pic open directly from Everything. The search term would be "jagger jpg".

My data drive has 62,000 files and 12,000 directories. The number of directories poses no problem and in fact helps because of the high degree of categorization and the search tool when I need it (which is only occasionally).

Maybe you have thought all of this through and rejected it. It's just my method.

 

[rogerthat]

Thank you for your addressing the issue/s.
But this method you use;-

Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff

..could not work in my case.
Mainly because of all the cross-referencing elements all my files need to have.
I cannot put files for Manchester in a Manchester file folder because they are also in part used in a London folder and even a Strasbourg folder. I need to find names, or other details form memory also in a file and I would have to have more copies than you could shake a stick at if they were cataloged normally.
If I put a set of files in Manchester I might spend ages searching through all the London files for that document set. etcetera.
Descriptive file-names are the way to go for me until I get a brain update.
At least I can find them with just a few key words.
Naming files;- "Stuff" just doesn`t cut it, on this occasion.
Each document has essential elements which need to be found and may need to be addressed in a short time. Thank goodness for USB sticks. wherever they all get to.

Who has one which has a ticker-tape LCD to `see` the content file-name/s (when you press a button)?

Another `conceptual design` from yours truly.

 

[kado897]

If you are talking about pictures you could use a series of tags and arrange you pictures library by tag. This would work for videos as well. Unfortunately other types don't natively support tags so you may require a third party solution.

 

[rogerthat]

I appreciate the point and agree All file types could have (via update) or should have a tag　option when saving any file or set of files.
Many people do need to keep many file types　in one folder of a set of similar. Tagging is a step in the right direction.
midnight here in . Gdnite

 

[derekimo]

Here are some ideas:

There are excellent search tools that can produce a list of file names containing a certain search string very quickly---typically in a second; presumably a bit longer in your case if you have hundreds of thousands.

One such search tool is Everything, from voidtools.com. It is free. It searches file names or partial file names ONLY, not file contents.

To give you an idea, I just typed "and doc" into Everything. It coughed up 298 files in less than 1 second. All of them contain "and doc" somewhere in the file name. Most of them are Word files, found due to the "doc".

I then tried "and docx" and the list immediately shrunk to 75, representing Word files with a docx extension.

Secondly--and you apparently rejected this years ago:

If you have a file that contains roast beef recipes, name it "roast beef" and put it in D:\recipes. Rather than naming it "here is a file that contains some pretty cool pictures I took while on vacation and also some food related stuff" and putting it in D:\users\yourusername\stuff\food-related\cooking\recipes.

I have tens of thousands of files---I'd guess no more than 100 have file names per se that are more than 50 characters. I can get away with that because of my folder structure, which is often 5 folders deep.

So, I might have this path:

D:\pix\vacation\1998\Vegas\RollingStones

and in that a file named "Mick Jagger grinning.jpg". Total path length maybe 50 characters.

Effectively, most of the "naming" is done by the path, rather than a file name such as "Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff, where there might be 50,000 pictures with no further categorization.

If I am looking for Jagger pictures and can't recall the year I saw the Rolling Stones in Las Vegas, I use the Everything search engine to ID the path, and then either navigate to the folder manually or pop the pic open directly from Everything. The search term would be "jagger jpg".

My data drive has 62,000 files and 12,000 directories. The number of directories poses no problem and in fact helps because of the high degree of categorization and the search tool when I need it (which is only occasionally).

Maybe you have thought all of this through and rejected it. It's just my method.

Thank you for your addressing the issue/s.
But this method you use;-

Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff

..could not work in my case.
Mainly because of all the cross-referencing elements all my files need to have.
I cannot put files for Manchester in a Manchester file folder because they are also in part used in a London folder and even a Strasbourg folder. I need to find names, or other details form memory also in a file and I would have to have more copies than you could shake a stick at if they were cataloged normally.
If I put a set of files in Manchester I might spend ages searching through all the London files for that document set. etcetera.
Descriptive file-names are the way to go for me until I get a brain update.
At least I can find them with just a few key words.
Naming files;- "Stuff" just doesn`t cut it, on this occasion.
Each document has essential elements which need to be found and may need to be addressed in a short time. Thank goodness for USB sticks. wherever they all get to.

Who has one which has a ticker-tape LCD to `see` the content file-name/s (when you press a button)?

Another `conceptual design` from yours truly.

I think you need to re-read ignatzatsonic's post...

So, I might have this path:

D:\pix\vacation\1998\Vegas\RollingStones

and in that a file named "Mick Jagger grinning.jpg". Total path length maybe 50 characters.

Effectively, most of the "naming" is done by the path, rather than a file name such as "Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff, where there might be 50,000 pictures with no further categorization.

His method is in blue, not the part you quoted.

 

[ignatzatsonic]

Thank you for your addressing the issue/s.
But this method you use;-

Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff

..could not work in my case.

As Derekimo pointed out----you apparently did not read my post accurately.

I would NEVER use a method like that.

I pointed out that that type of file name is exactly what I would NOT do and I gave my alternative.

 

[rogerthat]

Thank you for your addressing the issue/s.
But this method you use;-

Picture of Mick Jagger grinning, taken in Las Vegas while on vacation in 1998" located in a folder called D:\stuff

..could not work in my case.

As Derekimo pointed out----you apparently did not read my post accurately.

I would NEVER use a method like that.

I pointed out that that type of file name is exactly what I would NOT do and I gave my alternative.

Pardon me; was uber busy.

Back to the grind.

Thanks for everything.

 

[Still]

Hi guys I ran into a little problem and hope anyone can help me solve this issue..

I am unable to image my Local Disk (C: ), because it doesn't appear in Macrium under "create a Backup" tab, so I went to "computer" and tried right clicking drive and then "create a macrium image of this partition..." but that didn't work either, it gave me " Unable to image drive 'C' ". So anyone know whats wrong?


note: this is my first time using macrium and creating a system image.

edit: nevermind I think I might of found the issue.. this article explains it v5: Identifying Dynamic and GPT disks
Looks like I have to get the pro version, i'll see how that goes.

 

[Sentinel72]

Only problem i have with macrium reflect free is that in order to restore an image it requires a 1.7gb microsoft download..
There is of course the linux option which states it can restore windows operating systems in a linue environment.Ive seen mixed reviews saying that it doesnt work.
Has anybody restored a macrium image successfully within the linux environment.
Im unsure about the restore process now and i dont really want to download 1.7gb of data to restore.
Thank you.:shock:

 

[whs]

Only problem i have with macrium reflect free is that in order to restore an image it requires a 1.7gb microsoft download..
There is of course the linux option which states it can restore windows operating systems in a linue environment.Ive seen mixed reviews saying that it doesnt work.
Has anybody restored a macrium image successfully within the linux environment.
Im unsure about the restore process now and i dont really want to download 1.7gb of data to restore.
Thank you.:shock:

Download the latest WinPE .iso from here ( https://skydrive.live.com/?cid=475a0a48ca6d4035&provision=1&ref=3&wa=wsignin1.0&sa=412485191#cid=475A0A48CA6D4035&id=475A0A48CA6D4035%211812 ) - takes 8 minutes. Then burn this to CD - ImgBurn is best used.

 

[ignatzatsonic]

Only problem i have with macrium reflect free is that in order to restore an image it requires a 1.7gb microsoft download..
There is of course the linux option which states it can restore windows operating systems in a linue environment.Ive seen mixed reviews saying that it doesnt work.
Has anybody restored a macrium image successfully within the linux environment.
Im unsure about the restore process now and i dont really want to download 1.7gb of data to restore.
Thank you.:shock:

WHS's method is probably best as you don't have to download anything but that file.

But--I think the issues with the Linux disk are only that it might not boot and enable you to see your image file and destination drive----which of course can be tested beforehand.

I can't recall anyone who could boot the Linux disc and see the file and drives then say that he couldn't restore.

The WinPE method is less likely to fail to boot.

 

[bigmck]

Only problem i have with macrium reflect free is that in order to restore an image it requires a 1.7gb microsoft download..
There is of course the linux option which states it can restore windows operating systems in a linue environment.Ive seen mixed reviews saying that it doesnt work.
Has anybody restored a macrium image successfully within the linux environment.
Im unsure about the restore process now and i dont really want to download 1.7gb of data to restore.
Thank you.:shock:

When I first started using Macrium, I used the Linux option. I did restore my drive with it and had no problem. I use the Winpe now.

 

[lehnerus2000]

The only problem I've had with the Linux Recovery CD is that I can't make it acknowledge external USB HDDs.

It will restore from Local & Network HDDs.

I don't like the Macrium 5 GUI though.
I hate the way they've hidden all of the important options in links (e.g. resize, MBR).
The wizard in Macrium 4 used to ask you about those things.

 

[Sentinel72]

The only problem I've had with the Linux Recovery CD is that I can't make it acknowledge external USB HDDs.

It will restore from Local & Network HDDs.

I don't like the Macrium 5 GUI though.
I hate the way they've hidden all of the important options in links (e.g. resize, MBR).
The wizard in Macrium 4 used to ask you about those things.

Im not certain but i think the problem with external HDDs has been addressed.its insane that the majority of users will back up to a external HDD and this program does not see them.
Still i hope the problem has been solved.

 

[lehnerus2000]

Clarification

Has anybody restored a macrium image successfully within the linux environment.

On my PC, the Macrium 4 Linux Recovery CD has never failed to restore HDD images (from Local or Network HDDs only though).

Im not certain but i think the problem with external HDDs has been addressed.its insane that the majority of users will back up to a external HDD and this program does not see them.
Still i hope the problem has been solved.

I should have been more specific.
I was referring to the Macrium 4 Linux Recovery CD.
(It may have been an earlier version than v4.)

I haven't created one in Macrium 5 (and therefore I can't comment on its operation).

 

[7user78]

Hello there,
regarding the Macrium software, can I use x64 Rescue CD architecture in order to mount an XP x86 image or should I create another rescue CD directly from XP ?
Usually using the "Clone" option will clone the MBR partition too ?

thanks,

LE: I have made the rescue CD under Win7 x64 but first ,I need to clone/move the XP System x86