![do i need both fbackup 5 and fbackup 6 do i need both fbackup 5 and fbackup 6](https://alternative.me/media/256/fbackup-icon-er3bvp25ezge06e6-c.png)
IOS backups have always behaved like this. The only thing to avoid is renaming the files within the backup, those are hashed paths to the data in the iOS filesystem.
Do i need both fbackup 5 and fbackup 6 windows#
As far as I know renaming the backup folder on Windows is legitimate.
Do i need both fbackup 5 and fbackup 6 archive#
If you are on Windows the archive feature is not in the iTunes preferences, so you can only archive by renaming the folder (or copy to another destination). The 'jumble of letters & numbers' for the backup name is actually the device UUID, it means you always get one backup per device, even if you erase the device & give it a new name. Archive it from within iTunes if you wish, or copy it intact to some other location, but do not alter the name of an encrypted backup file. DO NOT rename an encrypted iTunes backup file. Time Machine does both include the features of an incremental backup and an archive, but that is because by design, it is intended to use some separate and dedicated hardware storage system for its database and files, while iTunes (and iCloud) are storing files in active storage which also is used for other data storage uses (so no one wants their laptop hard drive or iCloud space filling up with endless backup files). Or, you can use OS X Time Machine to restore a previous incarnation of the current incremental backup file. Or you can always just copy the actual backup file to an archive folder. The ability to archive an iTunes backup has also always existed, to completely preserve a backup from a specific time point.
![do i need both fbackup 5 and fbackup 6 do i need both fbackup 5 and fbackup 6](https://alternative.me/media/512/fbackup-thumbnail-nc0dtwdoxj661bl9-c.png)
If it is not current with the device contents, it is not really a backup, but an (older state) archive. A backup needs to be current with the contents of the device or system being backed up. There is, in IT, a distinct difference between a backup, and an archive. It does NOT erase the previous backup - it simply amends it incrementally (a fairly standard method, btw, of maintaining a given backup file to reflect the current state of the backed up device). This is, and always has been, their normal backup behavour. ITunes and iCloud backups have always been incremental in nature - the existing backup file is simply overwritten to reflect only those changes since the last update. So much complication, only to loose e-bye all the playlists I used Pre-sync, because when you sync the first thing it does is create a back up.and now find out I guess you can tell.I thought I had a back up before I synced.now I don't have backup from
![do i need both fbackup 5 and fbackup 6 do i need both fbackup 5 and fbackup 6](https://i.ytimg.com/vi/wv-Wauo7cUY/maxresdefault.jpg)
The nice system Apple used to have to save backups. I guess people were building up a huge backload of back-ups, so those people messed up Why did they do all this? It worked well, now it seems broken. I guess I can just name it with the date like it used to do automatically, but I guess because I use encrypted back ups. To save it? The backup name is already incoherent jumble of odd letters and numbers Has some good reason, but it sure isn't good for customers. Where can I change this "default".there is no way to change it? You have to manually createĪnd the bigger question is WHY!! And even bigger than that is why did they make When did this start happening? When did backups start getting deleted by DEFAULT?