Windows-based recovery tends to rely more of having a working backup set than Linux does, I guess -- every time you do something "slightly risky" like installing a new drive, Windows automatically (with the default settings) creates a "system restore point," which is just a backup copy of the registry and various other important files. Not that it always works, mind you...
Users can have a bin directory in their home directories. Within these can lie scripts which preform back ups. A user can also have a crontab which does hourly,daily,weekly,monthly,annual backups.
These scripts could direct the backups be stored off site via use of rsync, or maybe even removable media such as cds, dvds, flash drives. Windows doesn't own backing up data.
Usually, a good Linux system administrator will set up back ups for users. For example on a home network the server administrator can set up back up scripts to back up each user's data on the other computers.
Rough example illustration / explanation:
______ User A
Server { ______ User B
______ User C
And so on diagramming out a vast home network. (NB: Most home networks really are not terribly vast.)
The administrator would pull data to be backed up from each user's system, do the back ups from the server. NTFS is good for doing this, Samba could also be used. You could set up a policy similar to a Public directory for each user. Anything in ~/Backup would then be pulled accordingly to the server's cron job listings for backups.
I know Windows may also be capable of doing this. My point is backing up data is a concept, an idea. Nobody can really own ideas and thinking someone can is pretty backwards thinking in my opinion. This also leads me to see any argument of Windows or any operating system as better because it does back ups.
*chuckle*
Most of them can and do. Backing up data is a human idea and concept. Computers do what humans tell them, for the most part. Excuse me, think bash in Fedora has aliased rm -Rf / to ls, must go reset it.