Skip to main content

Carbonite and PRG files: Problem and Workaround

I've been using Carbonite for online backup for a few years now. I did try XDrive and I have earlier posts about how horrible it was.

One thing I've always liked about it is the ability to pull back individual files almost like an incremental version update. The fact that the backup drives integrate perfectly with Windows Explorer is a definite plus.

But when my laptop bit the dust recently (a <12 month old Toshiba power jack issue), I was hoping to rely on it for the restoring my files onto my new laptop. While I did have the physical drive from the Toshiba, I wanted to test it out for a full restore.

That's when I found a major problem. By default, Carbonite does not backup what it considers to be system files (EXE, DLL, COM, etc). It does backup VB, CS , ASPX files without a problem. But Carbonite considers a PRG file to be a system file. I'm not quite sure why - but it does. As a result, none of my PRG files were backed up.

As a FoxPro developer, this is tantamount to disaster. I would restore all my files and while the VFP screens and class libraries were all present - I couldn't run any of my code because it was missing a PRG file.

I contacted Carbonite about this and the first response was "sorry, we don't back up system files". What is interesting is that this post lists off the files that Carbonite considers system files.

That list is at the end of this post.

But there is a workaround.

If you highlight a PRG file and right-click, you can choose Properties. Click on the Carbonite tab and check the option to Backup Files of this type.



This solves the problem. So now, all of your PRG files will be backed up.

But what system file ends in PRG?

For reference, here is a list of all the file extensions that Carbonite will not backup in alphabetical order:

.$$$
.$db
.113
.BSC
.IDB
.ILK
.NCB
.OBJ
.PCH
.PDB
.SBR
.abf
.abk
.afm
.ani
.ann
.bac
.bak
.bck
.bcm
.bdb
.bdf
.bkf
.bkp
.bmk
.cab
.cf1
.chm
.chq
.chw
.cnt
.com
.cpl
.cpl
.cur
.dev
.dfont
.dll
.dmp
.drv
.drv
.dvd
.eot
.evt
.exe
.ffa
.ffl
.ffo
.ffx
.fnt
.fon
.ftg
.fts
.fxp
.gid
.grp
.hlp
.hxi
.hxq
.hxr
.hxs
.ico
.idx
.img
.inf
.ini
.ins
.ipf
.iso
.isp
.its
.jar
.jse
.kbd
.kext
.key
.lex
.lib
.lnk
.log
.lwfn
.msc
.msi
.msm
.msp
.mst
.nt
.obs
.ocx
.old
.ost
.otf
.otf
.pf
.pfa
.pfb
.pfm
.plist
.pnf
.pol
.pref
.prf
.prg
.prn
.pwl
.rdb
.reg
.reg
.rll
.rox
.scf
.scr
.sdb
.shb
.suit
.swf
.swp
.sys
.sys
.theme
.tmp
.tms
.ttc
.ttf
.ttf
.v2i
.vbe
.vga
.vgd
.vhd
.vmc
.vmdk
.vmsd
.vmsn
.vmx
.vxd
.vxd
.win
.wpk


Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP