How to Backup Your Smart Phone 85
Lucas123 writes "According to a Computerworld story there will be 8 million cell phones/smart phones lost this year. The site describes how to easily back up data on handhelds. The piece also addresses the future of these technologies: 'In Dulaney's opinion, traditional USB syncing "will die." Gartner is telling its corporate customers they should hasten this process by not permitting their employees to sync to their PCs. He explains this by saying that individual end users can create distributed computing and security problems because they are poor data administrators. Moreover, he adds, PCs are not necessarily more reliable than cell phones. Drake gives a qualified endorsement of wireless e-mail as the master application for backing up and syncing data, saying the technology is fine for dedicated e-mail environments but insufficient for corporate environments that require a vast array of wireless applications.'"
No longer an issue (Score:3, Interesting)
If you are at home it can even discover and use WiFi saving you some bandwidth - if you think it's worth the hassle.
Of course you might have problems with this if your smart phone doesn't run Linux, but it'll only cost you about $300 to fix that
*More is not charged for, but you can't do it too often.
Blame the users (Score:4, Interesting)
The biggest reason that corporate IT departments aren't particularly respected by the rest of the company is this blame the user culture that seems to pervade it. If there are shortcomings in the desktop and mobile software that makes it easy to get things wrong, then the software is at fault. Software is a tool for people, not the other way around.
Fun with Vendor Lock-In Techniques (Score:5, Interesting)
This type of backup is nothing new, a provider here in canada has had this style of application for backing up contact lists for over a year now for certain handsets. The convenience of a contact list (read: the inconvenience of losing it) is one of the retention techniques used in the industry here in canada, and i'm sure it is the same in the states. I somehow doubt that having the contacts stored by the provider themselves is going to be at all useful EXCEPT for one specific case: You lose/destroy/etc your device and are getting a hardware upgrade through your existing provider or purchasing out of pocket FOR the existing provider.
Blaming users own inability to herd data securely is a severely weak excuse for removing the one nearly-universal method of accessing the phone's data. What these companies want is to remove any and all data transfers that are not through their own data networks. Why would you want your customer to back up his own information when you can retain control of said information? Why would you want a customer to find a way to upload mp3's directly to their mp3 enabled phone instead of using their mobile browser store?
The rational for this is obvious, and the only sad thing is that the corporate clients are not the ones who will feel the pain. Once it becomes a "Standard" to not have USB file transfers, its the CONSUMERS who are going to find themselves limited to their provider for any and all data transfers (check data plan rates recently? if you do not REALLY need them they're quite the thorn to the side).
This smells to me like a prelude to DRM type control approached from a different angle. Instead of putting the content control in the content, its in controlling delivery methods.
Re:Blame the users (Score:3, Interesting)
If the user's home directories are kept on a share, then it's relatively easy to back up their stuff on a daily basis, but it costs money to build the SAN and network infrastructure. Even easier, put scripts on their systems to rsync their home directories to a repository at night; there are several commercial programs that will do this, but again you do have to spend money (on Macs, Retrospect was pretty good for this).
Maybe the Iron Triangle of IT is GoodCheapConstrain the User.
With regard to the article, it's solution is no better, it proposes several carrier-based backup plans that lock all your data up on Sprint's servers-- \sarcastic{which I'm sure are SO much safer than the average corporate desktop, nobody would ever think of cracking a box with a 10 million business names, tel numbers and addresses on it.}
I had to exchange my iPhone yesterday for a new one (the touch screen had become numb in a section after a week, a very painless process BTW). When I brought the new one back from the store, iTunes restored it UTTERLY: when the phone came up, the application I had up before I synced was in focus, all of my applications were in even the same modes they had been in when I synced it, down to the route I had showing in Google Maps, plus my history. My old Treo, though not this detailed, would still have my photos, call logs, and applications all restored, and with the associated preferences and settings restored. I just don't see a cell carrier providing that level of support for individual devices.
Re:Blame the users (Score:3, Interesting)
Well, NFS / automount and an array works quite nicely if you don't want to shell out the dough for a full-on SAN. With Linux users it's a total breeze to maintain once you get it set up (especially so w/ NIS or LDAP to bind it all together). Tie the /home server into Samba for the Windows users (then instruct 'em to drop their backups to a mapped drive on their desktop PC), and as long as you can keep the network halfway tuned (and keep an eye on it for bandwidth reasons, just like you would for a SAN), then it's not too much of an expense or headache.
I agree perfectly that the article completely overlooks the abuse potentials (wot!? You're leaving us for XYZ phone company? Well, we're sorry, but your data stays here!)
Crackberries already have facilities to sync email and contact/calendar/etc info wirelessly... wouldn't take much to extrapolate the concept to other non-RIM situations, would it? At least that way the corp keeps control of the original data (like they would w/ all the data passing through their Exchange box, for instance).