Time machine caught in preparing time machine
I switch off my time machine for a few hours yesterday as I had some intensive tasks and lots of harddrive action going on.
I deleted the files from the trash and have turned time machine back on, whereby its been stuck on preparing for about 40 minutes now.
Does this sound right? It also has not mounted the time machine back up disk (Network on an airport extreme)
Please don't tell me the simple act of turning it off for a few hours means I lose all my backups to may this year!
We may be having the same symptom for different reasons. I noticed my Time Machine would experience extremely long preparation times after I shutdown my computer. My computer is about 2 months old and before I started using time machine, would shutdown immediately when prompted. After utilizing Time Machine, I noticed my computer would take 30-60 seconds to sutdown. Upon restart, time machine would not backup automatically. If I forced Time Machine to backup, it would prepare for hours before backing up. I read an Apple support topic (same one Barry linked to) stating that this would happen if the computer were shutdown with the backup volume mounted. I would always make sure that the backup volume was ejected before shutdown, but I noticed tonight that sometimes my Time Capsule (the actual Time Capsule, not just the backup volume) would be mounted in the finder window (eject button next to it) but not on the desktop. This would happen when I would click on Time Capsule in the finder and manually view folders in Time Capsule. When I ejected both the backup volume and Time Capsule, the shutdown happened immediately when prompted. This was a good sign. Upon restart, I forced Time Machine to backup and the preparation time took only seconds instead of hours. The backup completed within 1 minute. I tried this several times and it worked every time. I haven't had a chance to verify that Time Machine is backing up automatically upon restart, but I suspect it will. I will post once I have those results. Like I said, we may be experiencing the same symptom for different reasons, but this seemed to fix my problem. Hope this helps.
Message was edited by: Mech. Eng.
Similar Messages
-
Time Machine stuck on 'Preparing to back-up'
Hi
Since upgrading to Lion my iMac has not completed a Time Machine back-up. It's constantly turning away, saying 'Preparing to back-up'.
Any suggestions please?
Cheers
PhilA word of warning:
I too have this same problem, the Time Machine is showing "preparing Backup" for more than 24 hours.
I have tried all the solutions I could find on the 'net, and none have worked, so I took it all in to the Apple store in Sydney.
After 1 hour of them playing around they decided I had a corrupt "in progress" file on the Time Capsule preventing the backup from progressing beyond the preparation stage.
So what was the solution to my problem? I was told I had to either:
* delete all the backup data on the TC and format it or
* take it away, copy all the data to another 500+gb hard drive, format the Time Capsule and copy all the data back again.
Apparently Apple have "no liability" as it is a corrupted file, which "could have been caused by anything - installing or uninstalling software, or just a random glitch".
So it seems that because their Time Machine software can apparently cause a backup file to be easily and randomly corrupted by day to day usage, I now have to either lose all my backup data, or fork out hundreds of dollars for a new hard drive to copy all the backup data to.
I am NOT IMPRESSED that Apple can seemingly wash their hands of the failings of their software and hardware combination, causing me to be out of pocket.
If anyone here believes what I was told is wrong, I would be grateful for your advice, otherwise it looks like I'm going to have to spend out more cash to solve this problem... -
Trying to encrypt Time Machine backup disc getting message - Error preparing Time Machine backup disc- size error usually not being multiples of 512, encryption.
I got the same problem.
But I think it cannot be related to not being a multiple of 512.
As when I devide the number of bytes 3.000.592.982.016 by 512 is equals 5860533168.
3.000.592.982.016 / 512 = 5860533168.
So what could be the real problem?
With kind Regards -
Time Machine stuck in Preparing Data Mode
In the past two days my time Machine has not made a successful back up. It seems to be stuck in "preparing data" and will stay like this all day. Even when I click the time machine preferences and stop it, it never changes. Does anyone have any solutions to this or has experienced it.Any suggestions would be greatly appreciated.
Thanks!!Judith,
The following might contain an explanation for what you are experiencing.
*_Time Machine May Report "Preparing..." For a Long Time_*
First, it’s good to determine WHY Time Machine is "Preparing..." for an extended period of time. Examining the Console logs during this event can reveal what is actually going on behind the scenes. It may be “Preparing…” for a genuinely good reason. How long is 'too long' to wait for Time Machine to finish "Preparing..."? Some times, "Preparing..." is required to perform the normal housekeeping that Time Machine does periodically. Other times, it really is "stuck" and never proceeds after more than 24 hours.
*”Deep Traversal” (Recent Crash / Forced Restart / System Update / Extended Period Between Backups)*
According to the following KB article it can sometimes take quite a long time if Time Machine begins a “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. [http://support.apple.com/kb/TS1516]
You see, Time Machine *+does not+* ordinarily perform file-by-file comparisons to determine what has changed and thus determine what needs to be backed up. Rather, Time Machine relies on FSEvents notifications. This is a log that the system uses to keep track of changes to directories. Rather than scan tens of thousands of files for changes each time, Time Machine simply looks at this log and narrows its’ scan to only the directories that have experienced changes since the last backup. Otherwise, Time Machine would have to be running constantly just to catch every change on its own and thus eat up precious CPU.
Every event that FSEvents records has its’ own ID which includes a time stamp. At the end of every backup, Time Machine stores the last event ID that it processes. When the next backup is initiated, Time Machine looks at this stored ID and determines that it only needs to backup events that have occurred after the time stamp on this last event ID.
If, due to a system crash, power failure, forced restart, or some other major system event, Time Machine cannot find this last event ID in the system logs then it will consider the FSEvents log “untrustable” and it will go into what’s called “deep traversal”. The Console logs may report +“Event store UUIDs don't match”.+ In this event, Time Machine will by-pass the system log entirely and perform its’ own file-by-file comparison to determine what has changed since its’ last backup. Obviously, if tens or hundreds of Gigs are involved, then this process can take quite some time and should be allowed to proceed.
Additionally, it appears that if Time Machine has to go back too far to find the last event ID, then it will give up and simply go into “deep traversal” and do the file-by-file scan on its’ own. This can occur if Time Machine has not been able to perform its’ hourly backups for some time, as is the case for users who only backup once a week or so. This is also the case with major Mac OS system updates that change thousands of files at one time. There are simply too many events logged by the system for Time Machine to bother looking for the last known event ID.
*Consolidation / “Thinning”*
At the beginning, when Time Machine is first used, incremental backups are relatively quick events. But as time goes on, and backup files grow, Time Machine requires time to perform house-keeping on the backed up data. This maintenance is referred to in the Console logs as "thinning". The larger the backup files become, the more time Time Machine requires.
To prevent the backup drive from filling up too fast, Time Machine will periodically consolidate, or 'thin', backups to free up space for new data. After a certain period of time, each hourly backup becomes "expired". This occurs about 24-48 hours after the hourly backup took place. At that point Time Machine begins consolidating, or "thinning", all the hourly backups of a given day into one daily backup. Then, after about a month all daily backups for a given week “expire” and are consolidated into a single weekly backup.
Obviously, since the Time Machine process (backupd) does not run continuously, it has to do this "thinning" during routine backups. That is where "Preparing Backup..." and "Finishing Backup..." come in. It is during these initial and closing phases of a backup that "thinning" occurs. As a result, while not every backup will be accompanied by extended periods of "Preparing..." and "Finishing...", periodically Time Machine will require extra time to perform these space-saving consolidations.
*Anti-Virus Software*
Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
*Software Updates* #
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is “untrustable”. So it is going to go item-by-item comparing the before and after of your system.
*Spotlight Keeps Indexing Backup Drive* #
It may be that Time Machine can’t proceed or complete a backup due to Spotlight indexing. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then, stop the backup, turn Time Machine OFF, and let the indexing continue.
However, at times Spotlight may hang and never progress after many hours, preventing further backups from taking place.
Go to System Preferences --> Time Machine.
Using the slider on the left, turn OFF Time Machine backups for now.
Next, click “Show All” in the toolbar.
Select the Spotlight Preferences.
Click the Privacy Tab.
First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:
+“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+
...and a progress bar will indicate the time remaining.
Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
Spotlight will now initiate a reindex of the hard disk.
Once completed, if you have any other hard disks attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.
Then turn Time Machine back ON and initiate a backup.
*Run Away System Process*
It’s possible that Time Machine is stuck “Preparing…” because another process is monopolizing your Macs’ CPU. Launch Activity Monitor and sort the items by “CPU”. Is there a process that is at or near 100% that might be preventing the backupd process from moving forward?
One poster stated, “I took it to my local Genius Bar and they found a Syslogd daemon running, taking up 100% of my CPU….This resulted in the "Preparing..." mode running forever.” [http://discussions.apple.com/thread.jspa?threadID=1755600&tstart=15]
You may be able use Activity Monitor to “kill” the offending process. Or you may be able to resolve it simply by rebooting your Mac. Then try backing up again.
*Verify/Repair Mac Hard Disk & Permissions*
It may be that your Macs’ internal hard disk has so many file/directory issues that Time Machine simply has trouble making sense of it. Some users have had success using Disk Utility on their Macs’ hard drive.
Launch Disk Utility and click “Repair Disk Permissions”.
Once complete, attempt a backup.
If Time Machine appears to hang at “Preparing…” again, then do the following:
Insert your Macs’ original install DVD and reboot holding down the “C” key.
At the Welcome screen go up to the “Utilities” menu and select Disk Utility.
Select your Macs’ hard disk on the left and click “Verify Disk” on the right.
If problems are found click “Repair Disk”.
Reboot to your normal desktop and try backing up again.
*For Time Capsule Users* #
If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
Wait 10-15 seconds.
Re-plug it in again.
After it has restarted (30-60 seconds), attempt another backup.
Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
Let us know if any of the above was helpful in resolving your issue.
Cheers! -
Time Machine stuck in "preparing" endlessly.
I have been able to successfully back up my MacBook Pro twice in the past two months using Time Machine, but both times I had to monkey with it, and I'm not even sure what exactly I did to make it work.
Today I've tried several times to back up my machine, but it seems to get stuck "preparing" for hours.
I don't keep Time Machine plugged into my laptop because I need that USB for my printer. Rather, I periodically plug my Sea Gate FreeAgent external drive in and attempt to manually back up. But it never just works without a lot of clicking around.
What am I doing wrong??? How can I get it to work??
Thanks so much!xtine,
Your situation is explained in the first section of the info below:
*_Time Machine May Report "Preparing..." For a Long Time_*
Consider these factors regarding an extended period of "Preparing...". Consider each topic separately and do not attempt to act on all of them at once.
*Recent Crash or Other Major System Event* (Deep Traversal)
The reasons for this process are described in an article by George Schreyer. “During the preparation step it checks the FSEvents log for consistency. If it determines that something isn't quite right it has to rescan the whole disk. This can take quite awhile. A full rescan is always triggered by a crash, an unplanned shut down event or by booting from some other bootable disk between backups…. After a crash, Time Machine must scan the whole disk to determine what it has to do because it cannot trust the information that it left behind. Connected via an Ethernet connection, this phase would typically take 20 minutes on an older PowerBook. Being connected wirelessly stretches this phase out to over 3 hours.” [http://www.girr.org/mac_stuff/backups.html]
According to the following KB article it can sometimes take a very long time if Time Machine begins this “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. (http://support.apple.com/kb/TS1516) Additionally, if Time Machine has not been able to perform its’ hourly backups for 24 hours or more, then it will perform a “deep traversal” once backups are renewed. This is the case for users who only backup once a week or so.
*Anti-Virus Software*
Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
*Software Updates* #
Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
If you take a look at the Console logs Time Machine may be reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. If you have a great deal of data, it may take quite awhile.
After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system. If you have just performed an OS Update then Time Machine knows what it's doing - let it do it!
*Spotlight Keeps Indexing Backup Drive* #
It may be that Time Machine can’t proceed or complete a backup due to a Spotlight indexing error. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then let the process contiune.
However, at times it may hang and never progress after many hours, preventing further backups from taking place.
Go to System Prefs --> Spotlight --> Privacy Tab.
Drag your Time Machine disk into the window. It should now be among the items to exclude from indexing.
Now quit System Prefs.
Reboot your Mac.
Reopen System Prefs and remove ("-") the Time Machine disk from the window.
Now initiate a backup.
This should clear out Spotlights cache. Naturally, Spotlight should begin indexing again (maybe even for a few hours depending on how much data there is), but it should eventually stop.
*Reboot Time Capsule* #
If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
Wait 10-15 seconds.
Re-plug it in again.
After it has restarted (30-60 seconds), attempt another backup.
Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
Let us know if any of the suggestions above helped in your case.
Cheers! -
Using time machine for the first time in a while
Hi all,
I just tried backing up my laptop for the first time in ages with time machine. However , it seems to get stuck on "preparing the back up" and never actually starts the backup.
The external drive I'm using has been used before for backups,and the icon is the bluey colour it should be on my desktop as the back up location, however the back up simply won't start.
I should mention that I have upgraded this laptop to another newer model which I since returned and went back to this older model. I also replaced the hard drive, and this is the first time im trying a time machine backup since those two changes
Not many options I can play with so I can't see why it doesn't start the back up...it never took a longtime before to start...
Could it be anything to do with space? Now the comp has about 490gb needing back up and there's only 100gb of space on the ext hd,because there's about 400gb of previous back ups on there. I didn't think this would be a problem though as I understood time machine just erases old backups when it doesn't have space
Any suggestions welcome! Thx in advance!
Both laptop capacity and ext hd are 500gbCouple of clarifying questions:
1) How long are you waiting?
2) Have you upgraded the OS to Lion?
When I upgraded from Snow Leopard to Lion, the first few time machines took hours 'preparing to backup' before the actual backup to occur. We're talking 6+ hours. I'd usually leave it over night to backup. Even my last fresh reinstall of Lion took about 20min to prepare the first time. Now the hourly backups take maybe 1min total.
My suggestion is to leave it over night and see what happens. It very well could be that the differences between your last backup and current machine state is so different it's taking a long time to determine all the changes. -
500 GB Time Capsule Working Fine UNTIL Time Machine tries to Backup
Hi There-
My 500 GB Time Capsule seems confused. It is extending a wireless network (from another Time Capsule).
The light is green, and the signal is great---until I tell Time Machine to backup. Time Machine says that it is "Preparing Backup...". After an hour or more of "Preparing" I get an error message that says the backup failed and it was unable to connect. Then I go to the Time Capsule, and the light is blinking Amber and I can't find it.
I unplug the power source from the Time Capsule and plug it back in...and the light is back green! Furthermore, I can see the Time Capsule mounted in "Finder" under "Shared."
My computer is completely updated. The Time Capsule was working fine at one point. Now it isn't.
Thanks, guys & girls.I'm in a similar situation with 3 Apple laptops (Macbook Pro 15" 1 week old, Macbook Pro 17" 2.5 yrs old and iBook G4 4 years old) and Time Capsule 500GB (latest model dual WIFI, bought 2 weeks ago).
Macbook Pro and iBook did backups without problems, iBook on the 2.4GHz and the other on the 5GHz band. The Macbook Pro 17" is 5 to 10 times slower in the backups than the iBook. But - still - it works.
When I connect the second Macbook Pro (15"), Time Capsule become instable and reboot casually without reasons. It reboots casually, and frequently (from 5minutes to 30 minutes intervals).
Now: turned off the iBook and connected the computers via cable LAN to TC and the problem remain the same. These 2 Macbook Pro backing up at the same time : Time Capsule become instable. Strangely only with the 2 macbook pros, not the iBook.
I really don't manage to understand why, and from where to begin to search to solve the error. The only think I did was checking the logfile in the Time Capsule but no bessages about errors. Simply the message when it restarts.
I never arrive to complete one backup. BUT only when the 2 Macbooks Pro are doing the backup at the same time! One at time works. Slow, but works.
TC worked well during these 2 weeks until I added the Macbook Pro 15" to the WIFI net. Someone knows if one "maybe somewere faulty" computer can hang TC ?
Other infos:
All the macs are on 10.5.7, all updates done. TC is on the 7.4.1 firmware. All the units are in the same (small) room. Except for these backups, all the computers works well (internet browsing, email, printing via TC, downloads, ...).
Appreciate any help / question that can help me to investigate
...sorry for my spaghetti english (-:
damon -
Time machine ethernet backup to time capsule works, wifi does not
Hi all.
I recently updated my old time capsule to one of the new tall ones ME182X/A with a 3GB drive. I transferred over the backup file of my Macbook Pro according to the Apple instructions (Time Machine: How to transfer backups from the current backup drive to a new backup drive) and whilst connected via an ethernet cable, time machine works fine with the new time capsule.
However, when I disconnect the ethernet cable and connect to the time capsule over wifi, time machine hangs on "preparing backup". I do not get to "xxMB of xxMB" or any error messages. I've tried the following:
reconnecting via ethernet after restarting my Macbook Pro (running 10.9.5) allows time machine to start and complete the backup.
I've tried deleting the ".inprogress" file, as per some websites, but this doesn't solve the problem
turning off spotlight, doesn't help
I have no anti-virus software running
restarting the computer, resetting SMC, restarting the time capsule - no help.
The wifi side of the TC is working perfectly otherwise. I can "see" it with Airport Utility, and mount the drive and explore it without any problems.
Any suggestions?
Thanks again,
JohnHere are the steps I would use.. do not connect by ethernet at all whilst you do them.
Factory reset the TC.
The Factory Reset universal
Unplug your TC/AE. Hold in reset. and power the TC/AE back on.. all without releasing reset and keep holding in for about 10sec. The time is not important.. it is the front LED rapid flashing that indicates you are in factory mode.
Release reset.
If it doesn’t flash rapidly you have released reset at some point and try again.
Be Gentle! Feel the switch click on. It has a positive feel.. add no more pressure after that.
TC/AE will reboot after a couple of minutes with default factory settings and will wipe out previous configurations.
No files are deleted on the hard disk.. No reset of the TC deletes files.. to do that you use erase from the airport utility.
Redo the setup with different names. Short, no spaces and pure alphanumeric. eg TCgen5 as base station name. TCwifi for wireless name.
Make sure the password for disk and wireless etc.. are 8-20 characters pure alphanumeric mix of case and numbers.
Reset TM then to the new drive location.
See A4 pondini for a full reset.
http://pondini.org/TM/Troubleshooting.html
Strongly recommend you also verify the backup and install the Widget.. A5 and A1. The log you get from the widget is a big help to see what is going wrong.
Ensure the ipv6 is set to link-local only in wireless.
I would do the whole lot but you can test at each step if you want.. I just had it happen to me.. first time in 12months and regular posting in this area. Doing the above got me going again.. although it takes a bit of patience to work through the lot. -
Forgot password to access my Airport Time Capsule, can't restore Time Machine backup
It is stupid, I know, but after the first time I setup Time Machine in my Airport Time Capsule (6 months ago) i never had to use the password because it stayed stored in my Keychain.
Anyway, couple days ago I had to format the hard drive of my MacBook Pro and I did it thinking that I had a complete data backup stored in my Airport Time Capsule (encrypted data). It was late when I realized that I did not have the password written/stored anywhere. Nothing to do about it, just move on and start all over again.
I need to clean up my Airport Time Capsule and set it to factory default. I already accepted that I will lose all my data and it is okay. So far all I found was how to reset the wifi user/password but nothing about deleting stored data or reset to factory default without having the encrypted password. Can you please help me? Thanks in advance!The encrypted data is not related to the Time Capsule.. that is purely Time Machine.
Very sorry for you.. it is one big danger when you encrypt.
Reset to factory.
Factory reset universal
Power off the TC.. ie pull the power cord or power off at the wall.. wait 10sec.. hold in the reset button.. be gentle.. power on again still holding in reset.. and keep holding it in for another 10sec. You may need some help as it is hard to both hold in reset and apply power. It will show success by rapidly blinking the front led. Release the reset.. and wait a couple of min for the TC to reset and come back with factory settings. If the front LED doesn’t blink rapidly you missed it and simply try again. The reset is fairly fragile in these.. press it so you feel it just click and no more.. I have seen people bend the lever or even break it. I use a toothpick as tool.
N.B. None of your files on the hard disk of the TC are deleted.. this simply clears out the router settings of the TC.
Wipe the hard disk. Open the airport utility go to the disk tab. Click on erase disk.
Select just quick erase.. it just deletes the file table and is not secure but fine for your purposes. -
How can one share iTunes Library across two machines at the same time?
**I have setup 1 of 2 machines to host all the songs in my iTunes library. I then went to machine 2 of 2 and held down option key on start up of iTUnes, changed the location of the liobrary on machine 2 to a shared folder on machine 1.**
**This works awesome and I can use itunes on each of the machines 1 and 2 with no duplicate library in my home.**
**Problem: I can only run one machine at a time. I can not run itunes on both machines at the same time. The error message from machine 2 is ITUNES library is locked and cant write to the folder. iTunes works correct if I QUIT iTunes on machine 1.**
**Can iTunes run at the same time on 2 machines and access the same library?**
*Thank You Troy*Troy Yoho wrote:
Can iTunes run at the same time on 2 machines and access the same library?
in a way, yes.
set up _*Home Sharing*_ on both machines.
JGG -
How can I copy a time machine backup from one Time Capsule to another ?
How can I copy a time machine backup from one Time Capsule to another ? I bought a 1 Tb Time Capsule to replace my 512Mb Time Capsule. Now, I like to copy my time machine backup from the old Time Capsule to the new one so I can keep using my backup.
from this support article:
(click on image to enlarge) -
Run invoke-command on multiple machines at the same time
Hey all so I read that if I store my New-pssession in a variable then used that in my invoke-command it would run all computers at the same time.
$a = Get-Content "C:\Users\cody-horton\Desktop\list.txt"
$session
for($i=0;$i -lt $a.Length;$i++){
if(!(Test-Connection -Cn $a[$i] -BufferSize 16 -Count 1 -ea 0 -quiet)){
Write-Host $a[$i] -foregroundcolor red
else{
$session = New-PSSession $a[$i]
Invoke-Command -Session $session -FilePath "\\My computer\C`$\Users\public\Documents\zip folder.ps1"
What exactly am I doing wrong I just need to run this script on multiple machines at the same time.
Thanks.
Edit: Also what would be the best way to close all the sessions thanks.Hi there,
So what I think you are doing wrong here is that you are overwriting the value in $Session everytime you executed code inside for loop. try the below:
$a = Get-Content "C:\Users\cody-horton\Desktop\list.txt"
$session = @() #define this as an array
for($i=0;$i -lt $a.Length;$i++){
if(!(Test-Connection -Cn $a[$i] -BufferSize 16 -Count 1 -ea 0 -quiet)){
Write-Host $a[$i] -foregroundcolor red
else{
$session += New-PSSession $a[$i] #add the new session to the array, at the end it will be a collection of sessions
Invoke-Command -Session $session -FilePath "\\My computer\C`$\Users\public\Documents\zip folder.ps1" #I think the above one won't work..first you need to copy the script locally on the machine and then execute it#Why this won't work because of Second-Hop Authentication
Have put comments where I edited your code.
Hope this helps
Knowledge is Power{Shell}. http://dexterposh.blogspot.com/ -
How can I resolve OSStatus Error 13 on Time Machine when connecting to Time Capsule on Lion?
This is a semi-rhetorical question: I have now resolved this for my own setup, However, there was very little information on this error in the fora, so I thought I would post my experience with getting a Time Capsule (2TB, 3rd edition) to work on OS X Lion after the AFP/NAS debacle.
Background
My third party LaCie Big Disk Network* NAS died when Lion came out.
I could access neither Time Machine nor the drive through Finder.
The excellent thread on "Lion: Connecting to legacy (pre-Lion) AFP services - and Mac OS X (server)" (https://discussions.apple.com/thread/3258472?start=0&tstart=0) allowed me to access the drive via Finder to save my files but, of course, Time Machine was still broken. That guide showed you how to lift security restrictions on AFP shares.
For reasons explained below [disclaimer: rant follows] I decided to ditch the LaCie and purchased a Time Capsule.
The Problem
Time Capsule connected via DSL to the net and set up a wifi network with a green light.
The "Data" mount for Time Machine was visible in Time Machine, but trying to access it showed the following error:
The operation couldn’t be completed. (OSStatus error 13)
Trying to open the share in Finder using the appropriate credentials showed:
The operation cannot be completed because the original item for "Data" can't be found
Things that didn't work
Turning lots of things on and off
Resetting the DSL modem, the router (Time Capsule), the computer
Repairing permissions
What DID work
Undoing the modifications made during the process of mounting the old LaCie NAS
To do this, open Terminal and enter:
sudo -s
chmod o+w /Library/Preferences
cd /Library/Preferences/
rm com.apple.AppleShareClient.plist*
(from https://discussions.apple.com/thread/3258472?start=0&tstart=0)
Then restart your computer.
This worked for me. I don't UNDERSTAND any of why this did or didn't affect the computer, so please don't ask me to explain how it worked or what else to try. I thought I would just put this out there for knowledge.
* LaCie have really got my goat. Unlike other manufacturers who seem to be trying to provide support for their drives (Western Digital MyBook), LaCie have stated outright that they will not be providing any updates for their Big Disk Network. This is a hard drive they describe as a "Professional NAS", though I can't think of many professions where £200 backups need to be replaced every two years to keep abreast of security updates. In their defence, the drive is no longer manufactured… but, IMHO, I don't see that as sufficient reason to abandon all support or updates immediately. Boo! On the upside, loving my shiny new refurb Time Capsule.Our true genius died a little while ago.
But up to Mountain Lion he has tones of info ..
http://pondini.org/TM/Troubleshooting.html
Try some of the section C solutions.
It is more than likely network.
BUT do the following.
1. Install the widget A1
2. Reset TM, A4
3. Verify the backup, A5
4. Reboot the whole network and restart it in order.. modem.. TC.. MB Air.
No luck to this point.
Tell us exactly what OS you have.
The worst possible is Mavericks. If you are trying to connect to old backups after an upgrade it is hopeless.
I recommend you start over.
Simply wipe the TC and start afresh.
Manually mount the TC disk in Mavericks so you are sure it is working. Tell us if you run into trouble.
Most important.. in wireless network preferences are you running ipv6 in link-local mode. -
Time Machine over AirPort to Time Capsule... maybe a solution
Like a lot of people on this forum, apparently, I have been suffering from the inability to make reliable Time Machine backups to a Time Capsule over AirPort. Here's what I did to solve the situation.
Here's my network setup:
I have an ADSL wireless box with b/g network connected over ethernet to a 1-TB Time Capsule which has a 5 GHz 'n' network. Using 5 GHz 'n' network where I am means no interference. All equipment that is not capable of 'n' is on the wireless box, 'n' equipment (basically, only my MacBook Pro) gets on the Time Capsule. It doesn't make internet faster, but sure makes the Time Capsule accessible. Both networks are hidden and secured with WEP (b/g) or WPA2 (n).
(the Time Capsule is double-NATted, unfortunately, to cut down on network chatter in the system log)
After upgrading to 10.5.6, I think I haven't been able to make a reliable Time Machine backup over AirPort. It may have been well before that (possibly with the AirPort Extreme update) but I don't remember. Most of the time, before the wireless box arrived, I have been making far-too-irregular backups over ethernet to the Time Capsule.
Anyway, I had been trying to get Time Machine to work over AirPort to the backup on the Time Capsule. I had made the original backup over ethernet (all 500 GB worth over a weekend). For the incremental backups, though, I would prefer AirPort because keeping a cable attached really is a pain. Of course, it didn't work right away.
What I couldn't figure out was why. Time Machine mounted the sparsebundle volume on the Time Capsule, but after that it seemed to do nothing with it. I left it for half a day and found little by way of relevant network activity. I tried the following to no avail:
* disabled Little Snitch (outgoing firewall) and the OS X firewall (incoming firewall)
* disabled security on the network
* disabled and re-enable Time Machine
* changed the name of the sparsebundle volume (that was dumb!)
* trash Time Machine preferences and re-select the backup disk
* reboot, reboot, reboot
Whatever I did, it sucked. Connecting over ethernet was excellent, and incremental backups went really quick, but AirPort just didn't fly. It would have been worse if it were slow; chances are then it'd be a hardware problem. But nothing was going over AirPort with Time Machine.
In amongst the surfing, I found somewhere how to downgrade the firmware on the Time Capsule. Worth a try since nothing was working. I opened up the AirPort Utility and checked, but it would only give me 7.3.2 (AirPort Utility 5.3.2). I searched and found the AirPort 5.3.1 software, and using Pacifist extracted the AirPort Utility application. That would let me 'downgrade' the Time Capsule firmware to 7.3.1 (and 7.3). It downloaded the 7.3.1 for me and put it on the Time Capsule without problems.
I then made a test run with Time Machine over ethernet, that was fine. The I tried over AirPort - and hey presto! it worked! I re-enabled my network setup (firewalls, security) and it's still working fine.
So, if your Time Capsule is on 7.3.2 firmware and Time Machine over AirPort *****, try downgrading to 7.3.1. The AirPort 5.3.1 software, which can download and install the 7.3.1 software (5.3.2 doesn't) can be found here:
http://support.apple.com/downloads/TimeCapsule_and_AirPort_Base_Station__802_11n__Firmware_7_31
Note: you need Pacifist to extract the AirPort Utility application;
do not install the software over your existing AirPort softwareThis may be tough because TM isn't supported over wi-fi unless you're using a Time Capsule. There are a couple of resources available to you and I'd also recommend posting in the Snow Leopard forum because TM is part of OS X the OS X forum would be the right venue. The first thing is I'm guessing you are using a router, if so make sure the firmware on it is up-to-date. You will need to refer to the router's manual. You also should do the same with the modem too. Some written resources are:
Time Machine FAQs
Time Machine Troubleshooting
Pondini Time Machine Tips
That's about all I can help you out with.
Good luck! -
Cannot open 2 Virtual Machines at the same time to access the same Database
Folks,
Hello.
I am installing Oracle Database 11gR2 RAC system using 2 Virtual Machines (rac1 and rac2) on the top of VMPlayer 3.
The VM rac1 and rac2 run correctly when one of them is shutdown.
Their locations are F:\VM_RAC\rac1 and F:\VM_RAC\rac2.
While rac2 is running, I open rac1. But this error message comes up:
Error: "Cannot open the disk F:\VM_RAC\sharerac\asm1.vmdk or one of snapshot disks it depends on. Reason: failed to lock the file."
While rac1 is running, I open rac2. But this error message comes up:
Error: "Cannot open the disk F:\VM_RAC\sharerac\asm1.vmdk or one of snapshot disks it depends on. Reason: failed to lock the file."
The 2 error messages are the same. This means I cannot open 2 VMs rac1 and rac2 at the same time. When we run RAC system, we have to open 2 machines or more than 2 machines at the same time so that all machines can access the same Database Server.
My question is:
Can any folk tell me how to have rac1 and rac2 run at the same time ?
Thanks.You need to disable disk locking, which ordinarily is performed by the first VM to prevent any other VMs from corrupting your vmdk files via uncoordinated writes. You will have to shutdown both of your VMs and edit the *.vmx flat file for each, adding lines like the following (settings taken from workstation 6, but should be nearly identical settings for VM Player 3.x):
http://crosbysite.blogspot.com/2007/10/clustering-in-vmware-workstation-6.html
scsi1.sharedbus = "Virtual"
disk.locking = "false"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"
A few comments:
- your shared disks (scsi1) must be on a separate virtual scsi bus than the boot disk (scsi0), to allow setting the sharedbus flag as seen above.
- you must also ensure the cache parameters and unsynced writes settings are set to guarantee that all IO is immediately flushed to the vmdk file so the other VM can immediately access the latest version of data.
Maybe you are looking for
-
Hi all. I have recently installed MSSQL Server 2008, and was not able to access the URL when I clicked on it. It gave me a 404. When I installed 2012, I tried the same thing and it also throws me a 404 error. How should I go about solving this? What
-
Can't disable my FTP Access ports!
Hi. I'm running MacOS X 10.3.9 on a Mac Powerbook with all of Apple's latest Security Updates installed. I did a virgin installation and no other software programs has been installed yet, and I need to find out if my current indicated FTP settings in
-
Sub contracting Process issue for A/c entry
Hi All, While doing the GRN for subcontracting process ,cost object error is appearing for stock change SFG account ( BSV). Business would like to do not assign the Default cost object for change in stock account. Kinldy confirm whether it is possibl
-
After Hard Drive Erase...Macbook Pro Won't Boot
Hi, So I was trying to do a fresh install of OS X on my 15" Mid 2012 Macbook Pro (Modified with a 512GB SSD and 16GB RAM). I turned the computer off and booted it into recovery mode. Then I went to Disk Utility and erased the Macintosh HD partision.
-
Line Item Display for Gl, Vendor & Customer Accounts
is there any standard report which gives line item details upon running it and not after going through the process of selecting the document listed by the report and then veiwing the line items..?