Beware that BOX doesn’t sync dot files, and ignores some other filetypes.
At first you might not notice, and when you do it might be too late (when you don’t care for accurate backups). Then there’s another dangerous pitfall when you try to bypass the necessary first sync from the cloud.
Make sure all files are synched through the box sync app on your old computer
Make a backup copy of the ENTIRE Box Sync folder on an external drive
Typically under c:\Users\<username>\Box Sync\
Migrating to a new computer / installing on a secondary computer
1) Download and install the BOX app
2) Run the BOX app and login
3) Let BOX download everything from the cloud onto your computer. Do not copy the backup to your new computer! Chances are BOX sees these files as new ones and your sync will eventually end up with an unexpected amount of duplicate files!
Now you may wonder why you need the backup or the old copy of the Box Sync folder?
BOX does not support certain files, they are not synched, but you’ll find them in your existing backup.
If you use a MAC, if you are a webdeveloper, chances are that you have a lot of files that start with a dot.
This is not a problem that is only related to BOX. Other cloud storage services have similar downsides. Stack also doesn’t .htaccess files to their cloud storage, although they recognize the need (especially for webdevelopers). There shouldn’t be a problem with folders starting with a dot.
All these files are considered ‘hidden’ by BOX, though they are not!
You need to copy those files manually to the new BOX location.
So that’s why BOX cannot be considered as a complete backup in the cloud!
How to deal with dozens of ignored files?
If you had a lot of dot files, it will be a burden to copy these files manually. But fortunately there are lots of applications which can make life easer for you. I use Total Commander (Commands > Synchronize dirs…) to make sure all these dot files are copied to their respective locations.
Download het ZIP-bestand rechtstreeks van de FileZilla website (kies show all download options). Download niet via http://portableapps.com
Volg vervolgens de procedure op http://www.portablefreeware.com/forums/viewtopic.php?p=84339#p84339
created settings sub-folder
renamed fzdefaults.xml.example file from docs sub-folder to fzdefaults.xml
edit fzdefaults.xml so the string $SOMEDIR/filezilla/ from Config Location line now reads settings
moved fzdefaults.xml from docs up one level (same as filezilla.exe)
Getest met FileZilla_220.127.116.11_win64.zip op Windows 7 Enterprise.
Result: config files are saved in settings sub-folder, but the icons cache is still created in AppData.
If the “Kiosk mode” setting is set to 1, FileZilla will not write any
passwords to disk. If set to 2, FileZilla will not write to any
configuration file. The latter is useful if FileZilla gets executed from
Geen update checks
If the “Disable update check” setting is set to 1, the capability to
check for new FileZilla versions will be completely disabled.
Ran into some problems recently with XAMPP. Exported a large mySQL production database and tried to import it locally in XAMPP (through Shell access).
Error: ERROR 1118 <42000> at line 437919: Row size too large <> 8126>. Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row format, BLOB prefix of 768 bytes is stored inline.
First I tried changing table to ROW_FORMAT=COMPRESSED doing so:
ALTER TABLE <tablename>
No success with that. Then I changed innodb_buffer_pool_size to 32MB (default setting was 8 or 16) in my.ini (mySQL config file in XAMPP)
# Comment the following if you are using InnoDB tables
innodb_data_home_dir = "/Sites/xampp-portable-win32-1.8.3-5-VC11/mysql/data"
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = "/Sites/xampp-portable-win32-1.8.3-5-VC11/mysql/data"
#innodb_log_arch_dir = "/Sites/xampp-portable-win32-1.8.3-5-VC11/mysql/data"
## You can set .._buffer_pool_size up to 50 - 80 %
## of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 32M
innodb_additional_mem_pool_size = 2M
## Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 10M
innodb_log_buffer_size = 32M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50
innodb_file_per_table = 1
innodb_file_format = Barracuda
Doing so made it possible to import a 1GB sql table without any problem.