TM starting new full backup

I just had a new, larger hard drive installed in my imac. It appears that TMkl is starting a full backup, rather than incremental on top of the previous backup. Should I allow it to finish? or should I stop the new backup and reformat or erase external drive and start again? If I let this one continue, I will have a double backup on my external drive.

jerrybobbabe wrote:
I just had a new, larger hard drive installed in my imac. It appears that TMkl is starting a full backup, rather than incremental on top of the previous backup.
yes, this will happen with a new drive.
Should I allow it to finish? or should I stop the new backup and reformat or erase external drive and start again? If I let this one continue, I will have a double backup on my external drive.
this is up to you. if you don't particularly need the old backups I would erase the backup drive and start backups afresh.

Similar Messages

Time Machine starts new full backups

Two MacBook Pro using Time Machine and Time Capsule: TM never uses the full capacity ot TC but claims "A problem has ocurred preventing TM from using the existing safety copy.", wipes out the existing sparsebundle and starts a new one so old backups go lost. Why this? How to avoid?

Please visit Pondini's Time Machine FAQ for help with all things Time Machine.

HT1175 Time Machine wants to start with a new, full backup instead of using the existing one

Hi, my Time Machine wants to start a new, full backup, instead of continuing with the existing one on the time Capsule.
Looking a the Troubleshooting guide, I've found the following piece of info, which is, as 99% of the times with the troubleshooting guides, totally useless to resolve my problem...
Message: Time Machine starts a new, full backup instead of a smaller incremental backup
There are three reasons why this may occur:
You performed a full restore.
Your Computer Name (in Sharing preferences) was changed--when this happens, Time Machine will perform a full backup on its next scheduled backup time.
If you have had a hardware repair recently, contact the Apple Authorized Service Provider or Apple Retail Store that performed your repair. In the meantime, you can still browse and recover previous backups by right-clicking or Control-clicking the Time Machine Dock icon, and choosing "Browse Other Time Machine disks" from the contextual menu.
It should be noted (hence the uselessness of the guide) that:
-I haven't performed ANY full restore
- I havent changed my computer name
- My computer has not had ANY repair, much less a hardware repair. Neither recently, nor in the 9 months I've owned it.
Which puts me back to square one, with the marginal improvement that now I have a way of browsing my old backups.
In the event I decide to start all over again, will there be a way for me to "sew" the two backup files?
Or will I always have to go the silly way around?
Anybody has any idea?
Thank you for your time (machine/capsule, your choice;-)

Hi John,
no, that doesn't have anything to do with my problem.
Just look at the image below.
Time Machine thinks that the disk I've always used to do my backups has none of them.
If I open the disk with Finder, obviously they are where they should be.
It is even possible to navigate them as per the instruction reported above, but even following Pondini's advice #s B5 and B6 (which are more applicable to my problem) didn't solve the problem.
Actually, not being a coder, I'm always scared of doing more damage than good when I have a Terminal window open.
My question is: how is it possible that Apple hasn't thought of some kind of user command to tell the idiotic Time Machine software that a hard disk backup is a hard disk backup, no matter what?
Estremely frustrating and annoying: I'm wasting HOURS in trying to find a solution to a problem that should not have arisen in the first place...
Have a nice weekend
Antonio

I bought a new external hard drive for backups, but time machine won't do a full back up. I think it is remembering backing up onto previous external hard drives, which I don't own anymore. How do I do a new full backup?

I bought a new external hard drive for backups, but time machine won't do a full back up.
I think it is remembering backing up onto previous external hard drives, which I don't own anymore. How do I do a new full backup?
When I bought the new (used) iMac, I also bought an external hard drive for backups. It worked fine, but my husband stole it.
Then I bought a new external hard drive (Seagate) and it worked fine for three weeks, then died.
So I just got a new external hard drive, which was put together from an internal hard drive and a hard drive enclosure.
Time machine did the first backup today, and it should have taken 9 hours like it did on the previous first time full back up. Instead, it took 30 minutes. That can't be right. I want to start over and do a full backup to make sure everything gets onto my new external hard drive, but I can't figure out how to do that. Please help.

Triple-click anywhere in the line below to select it:
tmutil compare -E
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
The command will take at least a few minutes to run. Eventually some lines of output will appear below what you entered.
Each line that begins with a plus sign (“+”) represents a file that has been added to the source volume since the last snapshot was taken. These files have not been backed up yet.
Each line that begins with an exclamation point (“!”) represents a file that has changed on the source volume. These files have been backed up, but not in their present state.
Each line that begins with a minus sign (“-“) represents a file that has been removed from the source volume.
At the end of the output, you’ll get some lines like the following:
Added:
Removed:
Changed:
These lines show the total amount of data added, removed, or changed on the source(s) since the last snapshot.

How to create a new full backup alongside existing one?

I have recently reinstalled my MBP from scratch and installed some apps from scratch as well. I still have my old TM backup in a sparsebundle on my NAS (a ReadyNAS NV+).
I now would like to create a complete new full backup alongside my existing one. Or put differently, a new folder/backup inside the Backups.backupdb inside the mounted sparsebundle. Currently I see a folder called "XYZs MacBook Pro". I'd like that to be renamed to something like "XYZs Old MacBook Pro" and create a new full backup under "XYZs MacBook Pro".
I understand you end up having multiple folders inside Backups.backupdb if you have many Macs (with different MAC addresses). I only have one Mac, but want TM to treat my old previous backup (of the same MPB, hence with the same MAC address) as if it was from another Mac (with a different name).
With such a setup, I can still access backups from my previous installation of the same hardware by selecting another volume from TM (by holding Alt when clikcing at the TM icon) or with tools such as Back-In-Time.
Is there any way to achieve this? My sparsebundle is large enough to hold another full backup alongside the old one.
Thanks
- Tom

Pondini wrote:
tofe1965 wrote:
But wait, you said if I erased the disk I get a new UUID. I did not erase it but I moved all files into a /Previous folder (after booting from the install DVD), then installed the system new, and then moved user data (and some Library and some application stuff) back from /Previous. So, I guess, I have no new UUID for my internal disk.
Ah, yes, that is different ("reinstalled from scratch" usually means erased). If the disk was never erased, it will still have the same UUID. But since you've moved or replaced virtually everything, it will all get backed up anyway.
I'm not sure why you did all that; the old +Erase and Install+ and +Archive and Install+ options no longer exist for Snow Leopard: there's just Install, which replaces OSX without touching anything else.
I wanted to have a *really clean* install as my old systems seemed to be messed up with some bad settings.
So, back to my original question: how can I make the new "XYZs MacBook Pro" appear alongside the old "XYZs MacBook Pro" and switch volumes when I start TM using the Option key?
Why would you want to do that? You can view and restore from any backup.
I figured that way I can keep all old backups from the old installation and not have TM retire old stuff. And start a new one from scratch for the new installation where things will get retired. Basically keep the two backups apart from each other and not see any of the old stuff unless explicitly mounted using the option key.
If I follow your approach, what happens to old files of the old disk/UUID? Will they get retired eventually? Would my original idea work as envisioned or would it retire old things nevertheless? If the latter is the case, it is of no use and your suggested approach is the better one.
Is there maybe a ay to force TM to start a new full backup?
Back up to a different place: a different HD or partition, or erase the current one.
Guess that's my only option then. I created a full bootable backup to en external USB disk using Carbon Copy Cloner. Erasing the internal disk and copying back using CCC will create a new UUID then I guess ...
I will try that in the next couple of days and report back here. Thanks a lot for all your help and explanations so far, much appreciated!

I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

I recently did a full reinstall from my time machine and now my MacBook pro won't back up to the time machine. It starts a full backup ignoring the original back up, can anyone help?

Did you follow the instructions on the page linked below?
OS X Yosemite: Recover your entire system

HT201250 Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in and if so, do I really need all the old backups on my smaller ext

Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in and if so, do I really need all the old backups on my smaller external drive?

50maz wrote:
Hi, I hope this question won't seem too basic but if I want to use a new larger external drive for my time machine backups, will it do a new full backup the first time I plug it in
Yes, it will do a full backup.
and if so, do I really need all the old backups on my smaller external drive?
Only if you want to be able to go back in time to those previous Time Machine backups. When you plug in the new larger external drive, you will only be able to go back as far as the first day you plugged it in and ran the first Time Machine backup on it.

Can't rename my computer and start new TM backup

Three techs at Apple have not been able to help me.
I have been backing up a PowerBook G4 and MacBook to a TC wirelessly, and now the MacBook BU stopped working but the PB continues OK. The sparsebundles are different sizes; PB 115 GB, MB 151 GB. After many gyrations with my MB sparsebundle, all unsuccessful, the tech suggested I start fresh with new computer name for my MB (the old name was firstname lastname's computer). So my new computer name is firstnameMacBook. After preparing to do a backup for more than an hour I get the error message "The backup disk image could not be mounted". Same error message I had when my MB BU stopped working. So a name change had no effect. Should I change the name of the existing old sparesbundle? Should I delete it? How? What?
What to do?
Bruce

Sorry. I should have been clearer. I was just wondering if it was ok to do so.
I had taken my partners computer. Re-installed Leopard, then when I went to do the time machine backup it just started using the original sparse bundle that was technically my partners. I wasn't sure how to get it to start another and wanted to check first if it was ok the rename a sparse bundle?
For interest sake. I did rename the original bundle and this forced the Macbook to start a new sparse bundle.
I wanted to keep the original sparse bundle that was my partners in case we had any trouble with my partners new computer set up and migration.
Hope that all makes sense now.
Thanks

Time Machine starts new "hourly" backup in under an hour

My last backup was completed at 9:44. Time Machine just started a new backup at 10:27! It now says completed at 10:31, next scheduled at 11:25 (still under an hour) Per Genius advice, I just reinstalled Snow Leopard which at least help the backup time drop down to about 3-5 minutes. It used to take 30 minutes to backup 50mb. But even after the reinstall, I am seeing Time Machine kick in under an hour between backups!?!

the next backup time is determined by the start time of the previous backup, not by the finish time. and there are always small variations anyway as the launchd (the mechanism that schedules periodic tasks) doesn't check on them every second. what you see is quite normal.

2008 R2 Backups running without error, but doing FULL backups twice a week...

I have two Windows Server 2008 R2 systems which I am backing up with the native WSB utility. Both are VMs under ESXi 5.5 on the same physical Dell R710 host. Each has its own 2 TB USB connected device which was dedicated to and formated by and
for WSB. Both complete their respective backups without error and have been up for months.
On system A, WSB reports there are 243 copies available and examining the drive shows there is 288 GB free of the 1.81 TB total.
On system B, WSB reports there are 11 copies available and examining the drive shows there is 1.33 TB free of the 1.81 TB total.
My question is, why doesn't system B leverage a similar amount of the drive?
Thank you for any ideas!
Clay
Newark IT Guy...

I may be way off base as I'm a real estate agent not an IT person and I've just started learning about WSB/wbadmin last week, but here are my thoughts:
1. Mandy's response is all about MaxShadowCopies which has little to do with the OPs issue (I think). MaxShadowCopies is associated with "Client Accessible Shadow Copies" and related "Shadow Copies for Shared Folders." Useful for when
you accidentally delete or mess up a file in some way and you quickly and easily restore a previous version of that file via the file's properties window. Going down the wrong path with this I think except for the small caveat that the absolute 512 shadow
copy maximum applies to WSB shadow copies. Somebody correct me if I'm wrong.
2. system B may have hit the "Maximum Shadow Copy Storage Space" setting for that volume. From the command line, use command "vssadmin list shadowstorage" and compare the "used shadow copy storage space" to the Maximum.
If it is close, or if an additional backup would cause it to exceed the limit, the system will delete backups from shadow copy until there is room for the new one (again, "I think" this is so). See the vssadmin resize shadowstorage" command
options for adjusting the size.
3. I've read a few examples where the free space shown via a drive's properties was wrong for various reasons so maybe this is your circumstance. So, system B may have had much less available space than you think, and because of limited space, The new
full backup takes priority and WSB is automatically deleting older shadow copy snapshots in order to make room for the new backup. Run chkdsk on that volume and see what the "available" space is.
Also, If it turns out you do have a space issue, Do you know for sure that your backups are succeeding? If the low number of backups is due to limited space, it could also cause the new backups to fail due to not enough space.
Caveat on all of the above: I am quite uncertain about all of this, so hopefully someone will chime in and corroborate or correct my comments.
As a parting thought, I'll have to say that after reading the forum for a few hours trying to learn about WSB/wbadmin it is disappointing to see, in thread after thread, so many canned responses linking the same reference material without any attempt to actually
answer the OPs questions or deepen understanding of the subject. Is this forum managed by paid employees? If so, it feels like many simply locate a document that "might" be related, then they copy and paste a link along with a few statements
directly from said document. No added insights of their own, no furthering or revealing of nuances about the subject at all. Mandy's post above is a prime example. Just an observation from a new visitor to this forum.
PS - I did notice that "Sriram [MSFT]" posted some very very helpful comments on the WSB & VSS subjects, just wish there were more like his.

Time machine full backup after disk and disk permissions repair

my macbook would not boot so i inserted the snow leopard DVD and did a disk repair and disk permissions repair, after that it booted perfectly but when it went to do a backup it did a full backup of 149GB , i am unsure why it has done this and would like to know how to stop it as i am trying to save space on my time capsule.
thank you in advance

Brycycle wrote:
i do not wish to let it do a full backup so as to save space on my time capsule but this is the log up till when it started transferring data.
I'm afraid you don't have much choice. You do have lot of space available, though.
Node requires deep traversal:/ reason:must scan subdirs|new event db|
No pre-backup thinning needed: 165.92 GB requested (including padding), 507.60 GB available
The "deep traversal" means TM compared everything on your system to the backups, and estimates that about 138 GB is new/changed (it adds 20% for workspace on the TM disk - the "padding" in the message).
If there's about 138 GB on your system, see #D3 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum), for some common reasons for TM to do a new full backup.
If there's more, #D4 there has some common reasons for large backups.
If all you did was repair disk and permissions, neither should have resulted.
the reason i did a permission repair and disk repair while running from the install disk was because my laptop would not boot from the internal disk so i did both just to be safe.
That's fine; just do the Permissions Repair again, while running normally.

Time machine full backup

Why does my computer start a new backup series every week / 10 days now? Never used to with Lion.

It backs up every hour which is OK but the frequency of starting a new backup has increased dramatically since I switched to Mountain Lion.
It now wants to start a new backup every week to 10 days and it takes forever to do a new full backup.

Amount being backed up by Time Machine keeps growing during full backup

After some problems with Time Machine backup, I removed a bunch of stuff from my internal hard drive, reformatted my external HD used for backups, and started a new full backup. Time Machine has been running for about 24 hours and gives me a status of Backing up: xx GB of yy GB. Both xx and yy keep growing (apace) so that I don't believe xx will ever equal yy.
To cryptic? Here are real numbers. My internal disk being backed up contains 469.39 GB. Backup status now says Backing up: 685.78GB of 754.42 GB. Both numbers just keep growing. What's going on here? I'm happy to let Time Machine overnight (again) but, really, this can't be normal.

Start up in Recovery mode, launch Disk Utility, select the startup volume ("Macintosh HD," unless you gave it a different name), and run Repair Disk (not Repair Permissions.) If any problems are found, repeat. Then restart as usual.
If you don't already have a current backup, you must back up your data before you take the above step. You may be able to back up, even if the system isn't fully functional. Ask if you need guidance.
Directory corruption in a MacOS journaled volume is always the result of a drive malfunction. It's not caused by power failures, system crashes, or anything else. You might choose to tolerate such a malfunction once in the life of a drive. If it's repeated, the drive must be replaced, or there is some other hardware fault that needs to be corrected. Ignoring repeated directory errors will result in data loss.

Repaired permissions, now TM doing a full backup?

Hi, intelligent user who doesn't have much advanced knowledge concerning what Repairing Permissions even means here.
So I'm planning on replacing my Macbook Pro's HD, and I just finished making a full bootable backup onto a 200GB FW drive using Super Duper, and checked the "Repair Permissions first" option. I figured that having a latest Time Machine backup (1TB Time Capsule) would make sense as well, so before powering down to unscrew the case I did a Back Up Now. It scanned the entire computer and decided that it would backup all 70 GB fresh. I'm assuming this has something to do with having repaired permissions, but I don't quite know what that means. It may be something similar to what recently happened to me, when I erased my whole computer and refreshed from Time Machine, and then on the next backup it did everything over again instead of updating (for that backup I can still browse dates before that happened as long as I start at the root drive).
Anyone know what I could do to fix this?

Brian wrote:
We have to be careful here: there are three different scenarios:
New computer or logic board. Time Machine identifies your computer by it's +Media Access Control address+ (MAC address), embedded in the hardware of the logic board. There is a way that some folks have gotten around this on Leopard after a new logic board, but it's tedious and very easy to mess up (I did that, twice!) per the link in #C8 of Troubleshooting. (It's very dangerous on a different Mac).
That was automated for Snow Leopard, resulting in the Re-Use prompt mentioned in #B5 of Troubleshooting. But, as #B5 specifies, Time Machine usually still does a full backup; the advantage is, Time Machine will delete the old backups normally.
New drive on the same Mac (per the link you provided). I don't believe that works on Snow Leopard, and I've not seen a hack specifically for Snow Leopard posted here.
Full restore (from Time Machine, a "clone", or otherwise) to the same drive on the same Mac. This almost always results in a new, full backup. An Apple engineer said that would stop with Snow Leopard, but obviously didn't. Some real techie UNIX guru decided there ought to be a way to do it; he posted a two-page log here a few months ago, of altering all sorts of things via Terminal, converting UUIDs to hex, etc., and claimed to have made it work. But he did it only as an exercise, and even he wouldn't recommend it, even to expert UNIX types.
. . . I suppose the best way to save space on my Time Capsule (it now has at least 3 copies of my entire system with only very minor differences in the existence of some files) would be to make sure I have all the files I will ever want to have backed up, then delete the old records, which is something I presume wouldn't be too hard, make a fresh backup, then delete whatever I don't think I need right now, knowing it will all be found by scrolling back to July of 2010?
I'd have to agree. It just isn't worth the hassle, or the risk of damaging something that you might not notice for a long time. I have no problem hacking around with most things, but not my backups.
Depending on whether Time Machine made new sparse bundles, it may not be too tedious to delete the old backups. See #12 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

PSE 7 Full Backup Error

I upgraded from PSE 3.0 to PSE 7.0 this summer. I converted my catalog without a problem.
I recently tried to perform an incremental backup based on the last backup I did using PSE 3.0, but verison 7.0 says it will not recognize the old format, so I need to do a full backup first.
Fine. I start with the full backup which will require 26 DVDs (!?!!?). After the 3rd DVD, the program crashed with non-specific error during the disc verification. I try to restart the backup by doing an incremental and using the last disc, but no luck.
I figure my on choice is to start over. After the 10th DVD and many hours, the program crashed with non-specific error.
Now it appears that I must start the full backup over again but now I've already wasted a full day and 13 DVDs with no guarentee that it won't occur again next time on disc #22 or something.
I know that I can physically copy the files from windows onto another hard drive or DVDs, but the whole point of the full and incremental backups is preserve not just the pictures themselves, but my tags and everything else I've done in PSE.
Is there away to continue an interrupted full backup?
Ideas?

For your backup needs going forward, you might consider moving away from manual backup using the PSE backup command. Hard drives are pretty cheap these days -- you can get a 500 GB external drive from Amazon for $70. Hard drives are a lot faster, and you can set up a standard backup program to backup up everything on your computer, not just your photos, on a nightly automated schedule. The main problem with DVDs and PSE backup is that it is manual, and human nature being what it is, people don't do it often enough (or at all). Also, accumulating too many incremental backups without a full backup now and then increases the likelihood that a restore will fail partially or fully. And doing a full backup to 26 DVDs is just too painful for most people!
I use two external hard drives, one for the nightly backups, and one that I backup to once a quarter and keep in my car ("offsite").

TM starting new full backup

Similar Messages

Maybe you are looking for