"files are compressed"

SyncBackFree is the freeware version of SyncBackSE/Pro. Note that it is not an evaluation version of SyncBackSE/Pro.

"files are compressed"

Postby gknuckles » Mon Jul 15, 2013 8:37 pm

"files are compressed" in the profile setup. What does that mean? Is that a question? Is it asking if files being backed up are compressed or is it asking if I want them to be compressed? If it's the former what if some files are compressed and others aren't? Should I then click "files are compressed" or not? Will it recognize that automatically and not try to compress them again?


Nothing in the help index. Search function on the forum produces unrelated returns. It would be helpful if there was a mention in the Quick Start what each option is and some idea about what to select.
gknuckles
Newbie
Newbie
 
Posts: 4
Joined: Mon Jul 15, 2013 8:02 pm

Re: "files are compressed"

Postby Dave Wilkins » Tue Jul 16, 2013 9:32 am

The captions are 'generalised' because their meaning varies with context and data-flow direction. That is, they mean either 'expect compressed files' or 'create compressed files', depending...

If you use it, you are telling SB to compress to and/or extract from Zips during various operations on that side. For example, a Backup set with 'Files are compressed' on the Destination will Compress the raw Source files as it copies them to Destination, so that the Destination has Zipped copies (and will conversely extract from Zips on Destination to raw files on Source if run as a Restore).

Whereas you could also use it to copy Zips (created by something else on the Source) to your Destination, and extract them at the same time. Some people wanted that...(and still do)

Mixed files (Zips and not-Zips) are not necessarily a good idea. What will happen depends 'what is where' versus 'what you set'. If you have mixed Zips/not-Zips in Source, and set it to 'Files are compressed' on Destination, it will Zip all the Source files (including the Zip files 'again', so you get Filename.zip.zip) during the process of copying them (now compressed) to Destination.

If you start with the same mixed file set on Source and select 'Files are compressed' on Source, it will try to extract from the Zips on Source (and output the resulting uncompressed files to Destination). It will ignore the non-Zip files on Source altogether, because you just told it to expect Zips, so that's what it (only) processes.

Once again, these last two examples depend on data-flow direction. They assume for purposes of illustration that you are copying from Source to Destination.
Dave Wilkins
2BrightSparks Staff
2BrightSparks Staff
 
Posts: 7776
Joined: Thu Jan 04, 2007 10:02 am

Re: "files are compressed"

Postby gknuckles » Thu Jul 25, 2013 3:05 pm

Dave Wilkins wrote:The captions are 'generalised' because their meaning varies with context and data-flow direction. That is, they mean either 'expect compressed files' or 'create compressed files', depending...

If you use it, you are telling SB to compress to and/or extract from Zips during various operations on that side. For example, a Backup set with 'Files are compressed' on the Destination will Compress the raw Source files as it copies them to Destination, so that the Destination has Zipped copies (and will conversely extract from Zips on Destination to raw files on Source if run as a Restore).

Whereas you could also use it to copy Zips (created by something else on the Source) to your Destination, and extract them at the same time. Some people wanted that...(and still do)

Mixed files (Zips and not-Zips) are not necessarily a good idea. What will happen depends 'what is where' versus 'what you set'. If you have mixed Zips/not-Zips in Source, and set it to 'Files are compressed' on Destination, it will Zip all the Source files (including the Zip files 'again', so you get Filename.zip.zip) during the process of copying them (now compressed) to Destination.

If you start with the same mixed file set on Source and select 'Files are compressed' on Source, it will try to extract from the Zips on Source (and output the resulting uncompressed files to Destination). It will ignore the non-Zip files on Source altogether, because you just told it to expect Zips, so that's what it (only) processes.

Once again, these last two examples depend on data-flow direction. They assume for purposes of illustration that you are copying from Source to Destination.


Thanks. That's more clear now. Some of the files on the source drive are zip files but others were compressed by Windows to save disk space. When compressed that second way it isn't a zip file, is it? Does it make a difference what I tell SyncBack?
gknuckles
Newbie
Newbie
 
Posts: 4
Joined: Mon Jul 15, 2013 8:02 pm

Re: "files are compressed"

Postby Dave Wilkins » Thu Jul 25, 2013 3:29 pm

If you use this setting it will try to create or extract from the type of archive the profile is set to handle, as indicated by the file extension. As per the Help, SyncBackFree can only handle

normal type of compression used by the older Zip format

so .zip archives are the only ones it will try to extract from if you point it at a fileset and tell it 'Files are compressed' on that side. Anything else would be simply ignored, as I stated previously.
Dave Wilkins
2BrightSparks Staff
2BrightSparks Staff
 
Posts: 7776
Joined: Thu Jan 04, 2007 10:02 am


Return to SyncBackFree (freeware)

Who is online

Users browsing this forum: No registered users and 2 guests

User Control Panel

Login

Who is online

In total there are 2 users online :: 0 registered, 0 hidden and 2 guests (based on users active over the past 5 minutes)
Most users ever online was 725 on Thu Feb 20, 2014 2:37 pm

Users browsing this forum: No registered users and 2 guests