Incremental Backups in Time Machine taking forever

Greetings all,
I have read the various posts about slow initial backups with Time Machine. I, on the other hand, had no such problem. However, now that my initial backup is complete I find it takes quite a long time for Time Machine to do its hourly thing. I mean a LONG time. The machine will sit for minutes at a time doing nothing, then copy a few kilobytes of a reported 239 MB backup. Then when it finally does complete - roughly 30 minutes later - it will sit for 10 or 15 minutes at the "Finishing backup" stage. At this rate Time Machine is running almost constantly - by the time the darnned thing finishes it's almost time to start again. It didn't do this on my G5 quad core with the same amount of data (about 850 GB). Does anyone have any ideas why this might be happening?
Thanks for your help.

Your Majesty!!
Sounds like your incremental backups are quite fast!
I have a mid 2011 iMac with SSD and 2TB HDD, and Time Machine incremental backups take anything up to 5 hours, sometimes longer. Trivial amounts of data are usually involved, but the log reports very large numbers of files.
One time I completed a Time Machine backup, rebooted and initiated another backup immediately with very few apps running (Console, Activity Monitor), and after several hours, the backup log said it had backed up over 800,000 files but only a very small amount of data.
I have a case open with AppleCare since July 1st. They have a whole lot of logs and other information being analyzed.
You will find others who have the same unresolved problem at - https://discussions.apple.com/thread/3144862?start=0&tstart=0

Similar Messages

Complete (Non-incremental) Backup Using Time Machine

When the Time Machine icon in the top bar of the desktop is clicked on and Back Up Now selected, does a complete backup starting from scratch result, or does Time Machine perform an incremental back up?
JohnnyS

It performs a backup as usually (minus the schedule). If it is the first backup, it is complete, otherwise the backup is incremental.

Time Machine taking forever and backing up extensive files. Help!

Ever since we upgraded my spouse's iMac, Time Machine has been acting up. My Mac store/guru guy migrated all the files from her really old G5 to her "new" (refurbished) aluminum iMac... NOT from the external HD she used for her Time Machine back-ups. When we connected the external HD to her new iMac, Time Machine automatically made a new back-up folder and did a complete back-up to that new folder. That was unexpected but understandable. After that, however, subsequent back-ups take forever, and Time Machine insists on preparing tens of thousands of files for back-up every time it runs, even though the great majority of said files had not been touched and did not need to be backed up. I will periodically check Time Machine preferences during these interminable back-ups, and sometimes it will be stuck in the "preparing" phase, and sometimes in the "finishing up" phase. The poor external HD just cranks and cranks and cranks.
I've read many of the Time Machine-related questions and responses, but none seem to address this particular problem. I tried putting the external HD on the Spotlight Preferences/Privacy/Indexing exclusion list, quitting System Preferences, then opening it up again and reversing the process to see whether Spotlight would re-index the external HD (per one communities suggestion I read), but that didn't seem to take place.
I have yet to visit the site referenced several times as the Time Machine FAQ gold mine; will do that next.
Any other ideas, anyone?

Thanks, Joe. My software is up to date. I forgot to mention that, after this first began happening, I erased the external HD and had Time Machine start all over again. It did the first, complete backup overnight, but subsequent ones still take longer than they should and it still prepares 90,000 - 120,000 items when it should be doing no where near that many files on an hourly basis. I'm wondering whether the cable needs to be changed out, as well. We're running OS 10.6.8.

HT201250 Time Machine taking forever...???

I am backing up 230GB from my local drive to a new external drive using Time Machine. I am now 24hrs into the process and only 25GB along...should it take this long?

You might start with this link:
http://pondini.org/TM/D2.html
and
http://pondini.org/TM/Home.html
Also the other links within these Time Machine general information web sites may shed light on your issue. For instance, you need to format the external backup drive properly, probably not causing your issue, but check this link just in case:
http://pondini.org/TM/5.html
FYI, my Time Machnie backup for ~ 215 GB took 2.5 hours, yours should be similar, so checking through the above links' list of troubleshooting steps might be worthwhile. Mine was via firewire and USB 2.0 might be somewhat slower, up to a factor of x2, but the time you have been waiting seems excessive.
Sep 5 12:53:27 username com.apple.backupd[1029]: Starting standard backup
Sep 5 12:53:27 username com.apple.backupd[1029]: Backing up to: /Volumes/LaCie/Backups.backupdb
Sep 5 12:54:28 username com.apple.backupd[1029]: Backup content size: 242.2 GB excluded items size: 29.7 GB for volume Macintosh HD
Sep 5 12:54:28 username com.apple.backupd[1029]: 255.02 GB required (including padding), 1.82 TB available
Sep 5 12:54:28 username com.apple.backupd[1029]: Waiting for index to be ready (101)
Sep 5 15:11:02 username com.apple.backupd[1029]: Copied 1168316 files (212.4 GB) from volume Macintosh HD.
Sep 5 15:11:10 username com.apple.backupd[1029]: 10.24 GB required (including padding), 1.60 TB available
Sep 5 15:11:10 username com.apple.backupd[1029]: Waiting for index to be ready (100)
Sep 5 15:23:53 username com.apple.backupd[1029]: Copied 15087 files (14.1 MB) from volume Macintosh HD.
Sep 5 15:23:54 username com.apple.backupd[1029]: Copying Lion Recovery set
Sep 5 15:24:03 username com.apple.backupd[1029]: Starting post-backup thinning
Sep 5 15:24:03 username com.apple.backupd[1029]: No post-back up thinning needed: no expired backups exist
Sep 5 15:24:03 username com.apple.backupd[1029]: Backup completed successfully.

New backup to Time Machine taking ridicously long. Is this normal?

I bought a brand new 1TB WD Mybook external drive to use for my Time Machine backups. It is connected via USB to my Macbook Pro 15" running Leopard 10.5.7. This is my first back up to Time Machine and I have only about 110GB of data for backing up. I have been backing up now for about 28 hours and the Time Machine status bar still says it only has backed up 864MB of 110GB. This cannot be right can it? Does anyone have any suggestions? Should I just continue to wait it out? Please help.

V.K. wrote:
PT wrote:
Time Machine doesn't really care if the volume is GUID or MBR,
yes, it does.
http://support.apple.com/kb/TS1550?viewlocale=en_US
It is referring to drives that use Master Boot Record (MBR) partition type, not GUID or APM, causing that issue. It then goes on to tell you how to reformat the drive for either GUID or APM for use with Time Machine.
While the article does suggest one type for Intel Macs and another for PowerPC Macs, that really only matter if you are trying to make a bootable drive. Since TM volumes are not bootable, you can use either sceme.
Regards,
Patrick
EDIT Whoops sorry about that. I read your original post and my mind substituted APM for MBR (as you can see in my reply here). But then when I re-read your post I see you were talking about Master Boot Record and NOT Apple Partition Scheme.
Silly me!
Message was edited by: PT

Time Machine taking forever to backup

I am using a mid 2009 MBP running OSX 10.9 and my TC is model A1355. I've been noticing the past week or so it hase been taking extra long to back up. I am backking up over Wifi which is what I've always done and have never had this problem. Not sure why it has been taking so long. Please help.

After a new OS install, TM can and will take a very very long time. It has to backup a whole new OS and its endless 10000s new files.
An alternative, is take another drive (blank and unused) and create a new TM backup,...that will go very FAST
(did same twice myself).

HT203177 how do i clear old backups from time machine to make more space

My 2TB Time Machine is nearly full. I am trying to back up a drive in a Mac Min that is starting to fail and wanted to do so on Time Machine. Unfortunately since my Time Machine is nearly full it will not back up drive without eliminating nearly all of the files on this Mini. I am okay overwriting the other backups already on the Time Machine but do not know how to force Time Machine to do so. Please any clues on how to make Time Machine overwrite other backups would be greatly appreciated.

About TM "Backup Drive is Full" Alert
TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive.
As you can see Time Machine does prune old backups to make space, but eventually it may no longer succeed. Then you will get the alert. You can delete old backups if you wish, but only using the Time Machine application.

Incremental backup from time capsule (time machine backup) to external disk

I have two questions regarding backing up a time capsule backup.
I would like to backup the time machine backup of my Macs from a time capsule to an external hard disk. The time capsule is a first geneneration one with 500 GB. The external hard disk has 500 GB as well with USB and firewire ports..
First question: What is the best way to connect these two hard drives - I am using a MacBook Air with two USB ports ?
Second question: What backup software could I use to do incremental backups - I tried ChronoSync but it is not picking up the changes of the sparcebundles ?
Thank you for every valuable advice
Regards

CAAN wrote:
I have two questions regarding backing up a time capsule backup.
I would like to backup the time machine backup of my Macs from a time capsule to an external hard disk.
Backing-up your backups is generally not a good idea. If there's a problem with the original backup, it will be copied to, and perhaps magnified on, the copy.
You'd be much better off making "secondary" backups separately. See #27 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum), for some suggestions.
About the only alternative is to "archive" the TC's contents to a USB drive connected to it, but that's not incremental, and has other downsides as well. See #Q6 in [Using Time Machine with a Time Capsule|http://web.me.com/pondini/TimeMachine/TimeCapsule.html] (or use the link in *User Tips* at the top of this forum).

After formatting and creating two partitions on my external HD, why is Time Machine taking 25x longer to perform a backup?

Hi.
I bought a macbookpro 13"retina, new two weeks ago and a G-tech 1TB external drive from the apple store. It's my first mac.
I performed a backup, using Time Machine, which copied 18 GB onto he 1TB external HD in around 20 minutes.
After a little more reading, I realised I should use Disk utility to partition the 1TB external G-tech drive into a 250gb partition, and a 750gb partition.
[My MBP has a 250gb flash HD. I'll use the other 750gb for storage of my other files, like photos, music etc.]
So, using disk utility I formatted the 1TB exernal drive, then created two partitions.
However, I've started backing up my data using time machine again, onto the 250gb partition, on the external drive, and its now taking 5 hours to copy the 19.81GB
So why is it taking 25x longer than the first time I did it? [First time it took 20 minutes]
Thanks

Since performing the fist backup, a couple of days ago, which took twenty minutes, and the second backup, which is taking 5 hours, I installed MS office for Mac 2011 and Silverlight.
Dont know if thats responsible?

Time Machine Taking a Long Time to Index

Hi everyone.
I first noticed this today. My Time Machine is taking a long time to index. It's stuck on "Waiting for index to be ready (100)" for about 10 minutes at least, it seems. I did notice earlier today that it had to delete old backups to make space for new backups, and I'm wondering if that has anything to do with it. I'm in the process of doing a verification now, but here's the code from two backups earlier today.
Here's the one where it had to delete backups to make room for new and future backups.
1/30/13 5:48:13.069 PM com.apple.backupd: Starting standard backup
1/30/13 5:48:13.267 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 5:48:13.749 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 5:48:35.120 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 5:48:40.280 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 5:48:40.407 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 5:54:50.703 PM com.apple.backupd: 500.8 MB required (including padding), 403.3 MB available
1/30/13 5:55:00.163 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
1/30/13 5:55:00.163 PM com.apple.backupd: Compacting backup disk image to recover free space
1/30/13 5:58:52.014 PM com.apple.backupd: Completed backup disk image compaction
1/30/13 5:58:52.016 PM com.apple.backupd: Starting standard backup
1/30/13 5:58:52.065 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
1/30/13 5:59:13.694 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 5:59:17.577 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 5:59:17.673 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 6:01:22.433 PM com.apple.backupd: 500.9 MB required (including padding), 424.6 MB available
1/30/13 6:02:40.909 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-28-225651 containing 5.8 MB; 430.4 MB now available, 500.9 MB required
1/30/13 6:02:40.909 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
1/30/13 6:25:09.045 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-12-095019 containing 1.08 GB; 1.50 GB now available, 500.9 MB required
1/30/13 6:25:09.045 PM com.apple.backupd: Deleted 2 backups containing 1.09 GB total; 1.50 GB now available, 500.9 MB required
1/30/13 6:25:09.045 PM com.apple.backupd: Backup date range was shortened: oldest backup is now May 20, 2012
1/30/13 6:28:35.009 PM com.apple.backupd: Copied 2289 files (7.3 MB) from volume Macintosh HD.
1/30/13 6:28:35.920 PM com.apple.backupd: 494.0 MB required (including padding), 424.6 MB available
1/30/13 6:28:35.921 PM com.apple.backupd: No expired backups exist - deleting oldest backups to make room
1/30/13 6:30:36.145 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-20-194752 containing 55.0 MB; 479.6 MB now available, 494.0 MB required
1/30/13 6:30:36.146 PM com.apple.backupd: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
1/30/13 6:33:16.203 PM com.apple.backupd: Deleted backup /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2012-05-27-093117 containing 64.5 MB; 544.0 MB now available, 494.0 MB required
1/30/13 6:33:16.203 PM com.apple.backupd: Deleted 2 backups containing 119.4 MB total; 544.0 MB now available, 494.0 MB required
1/30/13 6:33:16.203 PM com.apple.backupd: Backup date range was shortened: oldest backup is now Jun 7, 2012
1/30/13 6:34:11.232 PM com.apple.backupd: Copied 1171 files (2.5 MB) from volume Macintosh HD.
1/30/13 6:34:44.355 PM com.apple.backupd: Backup completed successfully.
1/30/13 6:34:54.258 PM com.apple.backupd: Ejected Time Machine disk image.
1/30/13 6:34:54.493 PM com.apple.backupd: Ejected Time Machine network volume.
And here's the one where it started to take awhile to index.
1/30/13 7:21:11.358 PM com.apple.backupd: Starting standard backup
1/30/13 7:21:11.955 PM com.apple.backupd: Attempting to mount network destination URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 7:21:12.540 PM com.apple.backupd: Mounted network destination at mountpoint: /Volumes/Time Machine Backups using URL: afp://Michael%20Payne@Extreme%20Pleasantville._afpovertcp._tcp.local/Time%20Mac hine%20Backups
1/30/13 7:21:38.074 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 7:21:41.754 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 7:21:41.768 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 7:23:47.444 PM com.apple.backupd: 452.8 MB required (including padding), 401.2 MB available
1/30/13 7:23:56.687 PM com.apple.backupd: Ejected disk image: /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle
1/30/13 7:23:56.687 PM com.apple.backupd: Compacting backup disk image to recover free space
1/30/13 7:27:52.753 PM com.apple.backupd: Completed backup disk image compaction
1/30/13 7:27:52.754 PM com.apple.backupd: Starting standard backup
1/30/13 7:27:52.898 PM com.apple.backupd: Network destination already mounted at: /Volumes/Time Machine Backups
1/30/13 7:28:14.638 PM com.apple.backupd: QUICKCHECK ONLY; FILESYSTEM CLEAN
1/30/13 7:28:18.207 PM com.apple.backupd: Disk image /Volumes/Time Machine Backups/Michael’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups 1
1/30/13 7:28:18.309 PM com.apple.backupd: Backing up to: /Volumes/Time Machine Backups 1/Backups.backupdb
1/30/13 7:34:32.780 PM com.apple.backupd: 399.3 MB required (including padding), 937.6 MB available
1/30/13 7:34:32.780 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:35:32.919 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:36:34.779 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:37:36.419 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:38:37.465 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:39:39.420 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:40:40.628 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:41:41.317 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:42:42.105 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:43:42.982 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:45:20.244 PM com.apple.backupd: Copied 1381 files (6.4 MB) from volume Macintosh HD.
1/30/13 7:45:21.507 PM com.apple.backupd: 382.5 MB required (including padding), 826.5 MB available
1/30/13 7:45:21.508 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:46:22.938 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:47:24.914 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:48:25.931 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:49:26.589 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:50:27.743 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:51:27.952 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:52:28.736 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:53:29.707 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:54:30.516 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:55:31.297 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:56:33.290 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:57:35.031 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:58:36.765 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 7:59:37.721 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 8:00:38.577 PM com.apple.backupd: Waiting for index to be ready (100)
1/30/13 8:01:48.483 PM com.apple.backupd: Copied 1069 files (5.6 MB) from volume Macintosh HD.
1/30/13 8:02:02.230 PM com.apple.backupd: Starting post-backup thinning
1/30/13 8:02:46.083 PM com.apple.backupd: Deleted /Volumes/Time Machine Backups 1/Backups.backupdb/Michael’s MacBook Pro/2013-01-29-183909 (5.4 MB)
1/30/13 8:02:46.083 PM com.apple.backupd: Post-back up thinning complete: 1 expired backups removed
1/30/13 8:02:46.083 PM com.apple.backupd: Warning: backup disk now has only 644.1 MB free without removing old backups
1/30/13 8:02:46.259 PM com.apple.backupd: Backup completed successfully.
1/30/13 8:02:58.025 PM com.apple.backupd: Ejected Time Machine disk image.
1/30/13 8:02:58.407 PM com.apple.backupd: Ejected Time Machine network volume.
I'm backing up to a Time Capsule over WiFi. This time capsule has a total of 3 laptops that are backed up on it.

Never mind. Whatever it was, it's fine now. We'll see what happens when it has to delete old backups to make space. It's down to about 720 MB free without removing old backups.

Backup to Time Machine failed due to large iMovie Library

Hi All
I have had issues backing up to Time Machine since upgrading to OS Mavericks and iMovie 10, the likely culprit is my large iMovie library. I have deleted my previous iMovie events, so only have the 1 iMovie library file related to the current version of iMovie. I have the following situation;
- iMac HDD - 1 TB with 0.5 TB free
- External HDD - 2 TB with 0.5 TB free (used for iMovie library which is 1.5 TB)
- External HDD - 3 TB with 1.0 TB free (used for Time Machine backup)
Now I have just imported some additional video into my iMovie library. When I try to do a backup I get the error "Backup Failed, Time Machine couldn't back up to "Time Machine"." Then further details suggest "The backup disk needs 1.55 TB for the backup but only 982.04 GB are available. Select a larger backup disk or make the backup smaller by excluding files." This seems to suggest that Time Machine wants to backup my entire iMovie library (ie, 1.55 TB)
Two questions; does Time Machine backup the entire iMovie Library each time there is a change rather than just the incremental imported files?, and how can I get my backup to work again?

Hello Eric,
unfortunately it is not possible to do it, because I have only remote access to the SAP system.
Is it possible to analyse the problem with the log files?
If yes --> which logs should I post here?
I went through the monitors in RZ20 and found a lot of errors/warning:
Database:
DBIF_SETG_SQL_ERROR
ORA-03106: fatal two-task communication protocol error
DB error 24909 in FET
SQL error 3106: WP in reconnect status
Background:
Job SAP_COLLECT_FOR_PERMONITOR terminated
Utilisation:
100% > 95% Background work process load exceeds threshold
BackgroundService: SystemWideFree BPWP: 1 WPs > 2 WPs Current value over threshold value.
Abap ErrorInUpdate
Syslog : BasisSystem
Operating system call recv failed (error no. & >E5)
The log file dev_cp retrieves the following information after execution of DB Check:
Trace file of control program (trace level 3)
< Function: BtcTrcInit> Function: main SAPXPG 700
2007-10-23--14-42-27 : Before BtcXpgDetach
> Function: BtcXpgDetach < Function: BtcXpgDetach Accept RFC connection from R/3 system
2007-10-23--14-42-27 : Before RfcAccept
2007-10-23--14-42-27 : RfcAccept returned OK
security check switched OFF
Install RFC call SAPXPG_START_XPG
Install RFC call SAPXPG_START_XPG_LONG
Install RFC call SAPXPG_END_XPG
Wait for RFC call SAPXPG_START_XPG or SAPXPG_START_XPG_LONG
2007-10-23--14-42-27 : Before first call of RFCDispatch
> Function: BtcXpgStartXpgLong
2007-10-23--14-42-27 : Beginning of BtcXpgStartXpgLong
> Function: BtcXpgStartXpgImportLong > Function: BtcXpgParam < Function: BtcXpgParam > Function: BtcXpgParam
Line Text
<No StdOut/StdErr output reported>
Target log table is not identical to source
ItGetLine terminated with NULL
<Function: BtcXpgItTransfer > Function: BtcTrcReset < Function: BtcTrcReset Call mode: VIA RF
Input arguments of BtcXpgStartXpg:
My WP settings are:
rdsip/wp_no_dia = 6
rdsip/wp_no_btc = 3
rdsip/wp_no_vb = 1
rdsip/wp_no_vb2 = 1
rdsip/wp_no_spo = 1
Thank you!
Thom

Backups without Time Machine?

I'm wondering what the options are for backups without Time Machine. I'm a tech support guy from a way back who's primarily worked with *nix and Windows machines, and I'm no stranger to setting up networks, NAS devices and filers, etc.
This is an all-Apple setup - MacBook Pros, iMacs, iPads, iPhones, etc. There were 2 Time Capsules in the mix, but they both began to fail so we replaced them with a single Seagate 4-bay NAS attached to 2 LAN ports. This is a 10/100/100 network with N-wireless and Gigabit switches.
Both before and after swapping out the Time Capsules for the NAS, we received the "
Time Machine completed a verification of your backups. To improve reliability, Time Machine must create a new backup for you.
message on the MacBooks, less often on the iMac. Post-NAS implementation, we are still seeing on the MacBooks. I've tried relaxing the backup settings to every 3-4 hours since all machines were set to backup every hour as default and I believe they were stepping on each other.
I'm not ruling out the network, or anything at this point, but it seems odd that Time Machine will complete a backup, then at some point in the future find that it's not valid and need to go again from scratch. It's not ideal to use Time Machine if it needs a new full backup every ~2 days or more.
So I'm simultaneously looking for any advice on how to resolve the Time Machine error, and/or how to perform routine backups to the NAS without Time Machine.
Thanks in advance.
MM

I'm wondering what the options are for backups without Time Machine
Time machine is NOT a data backup, its a system (/emergency) backup. (whats the difference? the system is data?!, Yes, however the difference is huge).
....and most pros (nearly all) are absolutely NOT using Time machine as a source, and never as a single source to archive important data.
Time machine by definition is absolutely not a data archive, nor a storage nexus for vital data, which is secure by definition.
here you go:
Methodology to protect your data. Backups vs. Archives. Long-term data protection
Data Storage Platforms; their Drawbacks & Advantages
#1. Time Machine / Time Capsule
Drawbacks:
1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
OS X Lion, Mountain Lion, and Mavericks include OS X Recovery. This feature includes all of the tools you need to reinstall OS X, repair your disk, and even restore from a Time Machine
"you can't boot directly from your Time Machine backups"
2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
6. Restoring from TM is quite time intensive.
7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
13. *Level-1 security of your vital data.
Advantages:
1. TM is very easy to use either in automatic mode or in 1-click backups.
2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
#2. HD archives
Drawbacks:
1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
Advantages:
1. Fills the gap left in a week or 2-week-old HD clone, as an example.
2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
4. Best-idealized 1st platform redundancy for data protection.
5. *Perfect primary tier and level-2 security of your vital data.
#3. HD clones (see below for full advantages / drawbacks)
Drawbacks:
1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
Advantages:
1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
3. HD clones are unconnected and isolated from recent corruption.
4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
7. *Level-2 security of your vital data.
HD cloning software options:
1. SuperDuper HD cloning software APP (free)
2. Carbon Copy Cloner APP (will copy the recovery partition as well)
3. Disk utility HD bootable clone.
#4. Online archives
Drawbacks:
1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
Advantages:
1. In case of house fire, etc. your data is safe.
2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
5. *Level-1.5 security of your vital data.
#5. DVD professional archival media
Drawbacks:
1. DVD single-layer disks are limited to 4.7Gigabytes of data.
2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
Advantages:
1. Archival DVD professional blank media is rated for in excess of 100+ years.
2. DVD is not subject to mechanical breakdown.
3. DVD archival media is not subject to ferromagnetic degradation.
4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
5. DVD media is once written and therefore free of data corruption if the write is correct.
6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
7. Best-idealized 4th platform redundancy for data protection.
8. *Level-3 (highest) security of your vital data.
[*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
#6. Cloud based storage
Drawbacks:
1. Cloud storage can only be quasi-possessed.
2. No genuine true security and privacy of data.
3. Should never be considered for vital data storage or especially long-term.
4. *Level-0 security of your vital data.
Advantages:
1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
2. Easy source for small-file data sharing.
#7. Network attached storage (NAS) and JBOD storage
Drawbacks:
1. Subject to RAID failure and mass data corruption.
2. Expensive to set up initially.
3. Can be slower than USB, especially over WiFi.
4. Mechanically identical to USB HD backup in failure potential, higher failure however due to RAID and proprietary NAS enclosure failure.
Advantages:
1. Multiple computer access.
2. Always on and available.
3. Often has extensive media and application server functionality.
4. Massive capacity (also its drawback) with multi-bay NAS, perfect for full system backups on a larger scale.
5. *Level-2 security of your vital data.
JBOD (just a bunch of disks / drives) storage
Identical to NAS in form factor except drives are not networked or in any RAID array, rather best thought of as a single USB feed to multiple independent drives in a single powered large enclosure. Generally meaning a non-RAID architecture.
Drawbacks:
1. Subject to HD failure but not RAID failure and mass data corruption.
Advantages:
1. Simplex multi-drive independent setup for mass data storage.
2. Very inexpensive dual purpose HD storage / access point.
3. *Level-2 security of your vital data.
Time Machine is a system hub backup, not a data hub backup
Important data you “don’t dare lose” should not be considered ultimately safe, or ideally stored (at the very least not as sole copy of same) on your Time Machine backup. Hourly and daily fluctuations of your system OS, applications, and software updates is the perfect focus for the simple user to conduct ‘click it and forget it’ backups of the entire system and files on the Macbook HD.
Bootable clones are the choice of professionals and others in that Time Machine cannot be booted from and requires a working HD to retrieve data from (meaning another computer). Your vital data needs to be and should be ‘frozen’ on some form of media storage, either in a clone, as an archived HD containing important files, or on DVD blank archival media.
A file that is backed up to Time Machine is unsafe in that if that file is deleted off the computer by accident or lost otherwise, that file will likewise vanish from Time Machine as it reflects changes on the internal computer HD/SSD.

How to backup a Time Machine backup

How can I best backup a Time Machine volume?
After a house fire that luckily didn't reach the computers, I was thankful that I did have backups so could be sure it wasn't a data disaster, but it got me thinking. The server providing the TM volume is in the same room as the Macs being backed up and if the fire had entered that room, all would have been toast, backups and all. So I want to setup an 'off-site' backup to avoid this potential problem. In fact, it will be another Mac in a nearby but separate building and I want that to keep a copy of the Time Machine volume. In fact it really wants to be a mirror of the TM volume so it could be used as the TM volume instead of the original (which would of course be unusable, hence the need to use the backup).
Since all TM backups are across the network, each client Mac has its own large backup file and any backup program that simply checks modification dates would therefore copy the files across every time as they would have changed, whereas Time Machine itself would only be copying a few changes each time.
Anyone any bright ideas about the best way to implement such a backup copy of a Time Machine backup volume?

Barney,
I have a question along the same lines and it might be of help to the author of this thread.
What about a Time machine RAID?
I am thinking about upgrading my 24" iMac to a 27" with much larger 2TB HDD. My current machine has a 500 GB. I back up to two WD MyBook Studio 500 GB drives which I have partitioned. One partition is for TM archives (which is my understanding of what TM makes: additive incremental archives) and the other partition is for weekly bootable duplicates I make with Carbon Copy Cloner.
I rotate one drive off site every week just in case of the dreaded house fire.
This set up seems to work okay in that I have two sets of backups, with one off-site at all times. The most data I stand to lose is one week, since I switch my backups every Monday.
However, the only drawback is that the Time Machine archives are not the same. They both contain the original TM back up I did way back when I first set up the drives, but since I am rotating the drives off site every week, they contain staggered back ups from thence forward. If I go to look for a file that I only had on my computer for one week and later deleted, that file will only exist on one TM drive and not the other.
So, long story short, a three disk RAID seems to be the best way to achieve TM back ups that are identical. Two drives would be constantly connected to the computer with the third drive rotating off site.
However, I have read on other threads that people were having problems using TM with a RAID set up.
Does Time Machine play well with RAIDs? Is there a particular RAID set up I should use? Can I partition the RAID in order to separate my TM archives from my bootable duplicates? Will the machine boot from a duplicate stored on a RAID?
Forgive all the monotonous questions, but I have never set up a RAID before so I am a total novice.
Cheers!
Thomas

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.

Old computer I had is OSX Snow Leopard with Entourage. New one is OSX Mavericks. Using Mail where are my addresses and old address book. Transferred old computer backup by Time Machine and other things work? Can't see a symbol for address book.

Old computer I had is OSX Snow Leopard with Entourage. New one is OSX Mavericks. Using Mail where are my addresses and old address book. Transferred old computer backup by Time Machine and other things work? Can;t see a symbol for address book.

Where are addresses kept on MAIL? I don;t like the new format at all. Frances
Begin forwarded message:
From: Frances Topping <[email protected]>
Subject: Re: - Old computer I had is OSX Snow Leopard with Entourage. New one is OSX Mavericks. Using Mail where are my addresses and old address book. Transferred old computer backup by Time Machine and other things work? Can't see a symbol for address book.
Date: August 25, 2014 at 9:46:01 AM EDT
To: discussions-replies <[email protected]>
Old Entourage is POP and new Mavericks MAIL is IMAP I believe. I don;t know how to export in the forms you mention. Frances

Incremental Backups in Time Machine taking forever

Similar Messages

Maybe you are looking for