Sudo nano /Library/LaunchDaemons/Ĥ.Edit that line to something larger such as 640, 768, 896, or 1024. Run this command to edit the backup engine: Sudo launchctl unload /Library/LaunchDaemons/Ģ. Stop the backup engine by typing this into the Terminal application: Open the Terminal and follow these instructionsġ. This seems to be more important for especially large file selections.
Even Crashplan has advised me to move to newer hardware as they are dropping support and I am currently maxed out as far as my Crashplan versions.Įditing the CrashPlan engine’s file allows java to use more memory. My Master and Storage servers are on PowerPC G5 Mac, stuck in time on 10.5.8. This seems to be especially important in my case because I’m running Crashplan on very old hardware.
#CRASHPLAN FOR MAC HOW TO#
Then I ran into the instructions on how to increase the amount of RAM that Crashplan has action to. At first I would unload and reload the engine until It eventually seemed to take. Occasionally I run into this issues where I open the client app on a workstation and it hangs on the splash screen and then crashes. I run Crashplan PROe at work on 13 clients, backing up in the LAN and across the WAN. That why admins came be assured action is happening. Why not add a progression bar, verbose log out out, or even a simple ETA on migrated jobs …. Why do I as the customer have to go snooping around hidden folders to find a piece of simple information. So I replied back and still have not heard back on the officially ticket. And when I opened a ticket I didn’t get a response for 5 days, and when Crashplan responded, they said “Is this still a problem?” REALLY! that’s how you support paying customers. The frustration comes from not being able to find this information anywhere in the web ui. If you watch the folder size it slowly gets larger leading me to believe the job is migrating over, just very slowly. Instead I find a folder with the same GUID as the job I was migrating over. Once you turn on hidden folders you’ll see a folder named “.balance.moveguidtomount-109”. That got me to looking at the destination folder on my HP server. But for very large backups, like my 3TB’s it’s a pain because there is no progress bar to show if the job is actually migrating over, and nothing writing to the log files.This was a feature in Why did Crashplan remove this feature? For administrators, we want to know everything going on about our machines. You log in select “Devices”, select the client name, and from the action menu to the right of the job (the folder/arrow icon) select “Migrate Archive. This is a fairly easy process in the web ui. My first task though is migrating all those backup archives off the external drives and onto my HP internal Drive.
#CRASHPLAN FOR MAC UPDATE#
More more worrying about drives not mounting and I will be able to update to the latest version of Crashplan. My new setup is a HP D元80 G8 with 18TB of internal storage.
#CRASHPLAN FOR MAC UPGRADE#
I have several bugs/issues with the Crashplan web ui that can not be resolved unless I upgrade and the external drives occasionally don’t mount on restarts … all of which requires me to spend more time then I want administrating backups. I’m as updated as I can get with Crashplan because I can’t upgrade the Java any more on the powerpc Mac. Long story short, that setup didn’t work. My old setup included a powerpc Mac running 10.4 and five external drives. I’m in the middle of setting up a new Crashplan PROe server.
0 kommentar(er)
