By. 6:27 am, June 11, 2014. Tune up your Macintosh and clean out the cruft. Macs are solid machines, but just like their owners they have a tendency to get lethargic as they age. Launching and switching programs takes longer, simple tasks become arduous, and the dreaded beach ball of doom appears more often than it did when your machine was new. The operating system just starts to feel crufty, and can get worse over time. I see these issues in my IT consulting business regularly.
- Slow Network Backup From Agent For Mac Download
- Slow Network Backup From Agent For Mac Mac
- Slow Network Backup From Agent For Machine
You may be asking, why does this happen? There are many reasons, but some are more common than others.
Sometimes your hard disk (or solid-state drive) gets too full and interferes with normal computer operations. Crashes or misbehaving programs can corrupt the disk directory or application cache files. Remnants from old software may still be running behind the scenes, or you don’t have enough RAM to deal with your OS and workflow. Is there some sort of tune-up you can do to sort it out?
Slow Network Backup From Agent For Mac Download
Your tech always tells you to just reboot the computer, but there’s got to be more than that. The good news: Yes, there are some things you can do. And, perhaps, adopt some more-efficient computing practices for yourself along the way. This post is sponsored by MacPaw, maker of CleanMyMac. 4 things to check if your Mac runs slow Here are four common things I perform or check for clients when they complain that their Mac is sluggish:.
Let’s look at each of these. Free up Mac disk space Far and away, the most common issue I find when computers are running slowly is that the hard drive is nearly full. When your hard drive gets too full, performance suffers. There is always a constant stream of information going between RAM and disk storage. The operating system uses disk storage for temporary data: virtual memory swap files, application cache files, etc.
Programs and data you’re actively using get loaded into RAM and old data or background tasks are temporarily saved or cached to the hard drive. When free space on the hard drive gets too low, the OS can’t operate efficiently and spends more time doing smaller read/write operations. You start to see that more often.
When space completely runs out, the machine becomes unresponsive and virtual wheels grind to a halt. You can find out how much space is left by going to the Apple Menu – About this Mac – More Info. The Storage tab will show the amount of available free space your Mac still has. If the remaining space is less than 2GB, your computer is struggling. A good rule of thumb is to keep at least three times the amount of installed RAM free.
For example, if you have 2GB of RAM installed, keep at least 6GB free on the disk. To free up space, delete unneeded files, old downloads and installer files ending in.dmg or.pkg. Movies, TV shows, music and pictures can also take up lots of room. You can copy some of these files to an external hard drive, then delete the originals to make more room. Remember to empty the trash after deleting to actually free up the space. When you can’t clear out enough data to make room, it’s time for a bigger hard drive. Rebuild Mac disk directory and clear caches The disk directory is the list of files stored on your hard disk along with their locations.
Sometimes this can get out of sync with the actual files on disk. If a program crashes or doesn’t complete saving a file correctly, the information in the directory may not match what’s actually on your disk. Various small read/write errors also slowly build up over time and can cause problems opening and saving files, again generating the dreaded beach ball of death. Cache files are temporary holding places for constantly changing information, such as installed fonts, graphics from web pages, Spotlight indexing, etc. As above, program errors and crashes can corrupt cache files, making them fully or partially unreadable. This, in turn, causes individual programs or the OS itself to misbehave. There are a number of utilities on the market to help with these problems, but a very simple solution is built right into your Mac: the.
Among other things, a Safe Boot runs a full scan on the hard drive sector by sector and fixes problems found in the disk directory. It also clears cache files of old data, so you get a clean start on your next reboot.
To perform a Safe Boot, restart the computer and hold down the Shift key until you reach the desktop. This may take a few minutes, and depending on your OS X version you may see a progress bar onscreen for part of the process. Once you’ve reached the desktop, release the Shift key and restart normally. For more advanced disk directory repairs, I highly recommend. If your Mac won’t boot at all (even in Safe Mode) you can often get things working again with this useful utility.
One common step people take to try and solve disk problems is to. Back in the early days of Mac OS X this was helpful, but it has become much less necessary in current versions.
Slow Network Backup From Agent For Mac Mac
It won’t hurt to repair disk permissions, but the errors listed and fixed typically don’t affect much. Remove unnecessary startup items and internet plug-ins from Mac When your Mac starts up, programs you use frequently can be set to automatically launch at startup: Safari, Mail, Dropbox, etc. Several background processes may also get loaded to support programs you’ve installed, like backup software. And some programs may have configured themselves to launch at startup whether you want them or not – Skype, anyone? You may have extraneous items or out-of-date tasks vying for attention.
To prune these down, check in a few places: First visit System Preferences – Users & Accounts, and click the Login tab. Here you’ll see a list of items set to open automatically when you log in. Some of these items may no longer be needed or current. For example, if you used to run Symantec AntiVirus on your iMac in 2002 and have just migrated things along ever since, there may be one or two Symantec programs still set to launch at startup. You can also remove any programs that may have configured themselves to run automatically which you don’t use (like Skype).
To remove an item, select it and click the “-” sign. You can also safely remove any items that show an error code or as kind “Unknown.” A long delay at startup could be a sign of a missing shared network drive. If you’ve previously connected your Mac to a server or another networked Mac (say at work), that drive may have been added to the list of items to open at login. If you’re then on another network or the share is unavailable for some reason, the Mac will pause as it waits for a response from the missing disk.
Check to see if there are shared drives or “Volumes” in the Login Items list, and if so remove them. The next few steps are a bit more advanced. You need to be familiar with locating and deleting configuration files on your hard drive. If you are not comfortable with these steps, skip down to the section on RAM. On the hard drive, there are a few more folders you can check: Macintosh HD – Library – LaunchAgents Macintosh HD – Library – LaunchDaemons Macintosh HD – Library – StartupItems Macintosh HD – Users – Your Home Folder – Library – LaunchAgents Macintosh HD – Users – Your Home Folder – Library – StartupItems These folders contain.plist files that launch background processes (backups, VPNs, etc.). You can delete items you recognize as outdated or programs no longer needed; for example, as above you may see some items with Symantec in their filenames, or an old backup program you’re no longer using. An Administrator password will be required.
Not all of these folders may exist on your system. Note that in OS X 10.7 and above the User Library folder is invisible by default; to make it visible, hold down the Option key then in the Finder click on Go – Library VERY IMPORTANT: If you’re not sure what something does, leave it alone!! Internet plug-ins can also cause problems, especially older plug-ins with newer web browsers. Plug-ins tend to get installed automatically as you visit websites over the years, but rarely get uninstalled.
Do you really need the RealPlayer plug-in from 2005 any longer? Check the following two folders and as above, prune out anything you recognize as unneeded or more than three years out of date: Macintosh HD – Library – Internet Plug-Ins Macintosh HD – Users – Your Home Folder – Library – Internet Plug-Ins After removing any Login items, LaunchAgents, LaunchDaemons or old plug-ins, reboot the Mac.
Install more RAM and manage Mac memory better Your Mac uses RAM to store data that the computer is actively using. The more RAM you have, the more programs you can run simultaneously with less need to cache and store data on the much-slower disk storage.
Doubling or quadrupling the amount of installed RAM (if possible) will make a noticeable difference in how smoothly the computer functions. You can see how much memory is installed in your system under the Apple menu by choosing About This Mac. For systems running OS X Lion 10.7 or higher, 4GB is really the practical minimum. If you’re still chugging along on 2GB, adding more will make a big difference. Quitting unused applications can also improve performance. I’ve come across clients complaining about bizarre behavior on their Macs, only to find 30 apps running simultaneously! Quitting (or force quitting) most of them can substantially improve performance.
If you need to force quit, restart the computer afterward. Speaking of restarting — why do techs always tell you to do this? Well for one thing, it tends to solve problems more than half the time, so it’s our default response for a quick fix!
But more seriously, after your computer has been running for a while and swapping lots of things in and out of RAM, or after a program has crashed, small errors can snowball into bigger glitches. The RAM storage itself can get fragmented, or stalled background processes can begin to interfere with running tasks. Rebooting the computer clears out everything from RAM, stops all running processes, reloads the OS and brings things back to square one. Modern operating systems such as OS X, Windows 7 and Linux are much more resilient than in days of old, but the need to reboot has not gone away entirely. If your Mac hasn’t been restarted in several months, it’s time.
Now here’s a user workflow issue: If you tend to have many windows open at one time in a single program — say 20 Microsoft Word files, 34 PDFs in Adobe Reader, six dozen web pages in different browser tabs — this will definitely slow things down. Each open window requires memory to store and CPU power to deal with. In general, try to keep under (say) 10 documents open for any single program at one time. I know, I know, you’re going to complain: “But this is how I work, I need all these things open at once!” Yes, yes. But remember you’ve just complained that your computer is running slowly, and this is one way to fix things. Pick your poison! Is a fresh OS X install worthwhile?
Sometimes problems seem so vast that a fresh installation of the operating system is a tempting fix. In my experience this isn’t routinely needed (OS X is not Windows). It’s definitely worth trying the steps above before replacing the OS. However, if you’ve tried all of the above and are still having problems, an OS reinstall might help.
Remember to back up all your data first — I like either or of the hard drive for this task. I’ve also found it best to have a local copy of the OS X installation software with you — either Apple’s downloadable Lion, Mountain Lion or Mavericks installers, or the install DVD for older OS versions. These work faster and more reliably than online installers, and allow you to start over again if something goes wrong.
You did back things up first, right?
We have been using Azure Backup (MARS Agent) to backup an Azure IaaS VM 2012R2 file server (Files Folders) to an Azure Backup Vault in this clients Azure subscription. About 10 data ago a 'large' DSF/R data set was seeded to the server and synced up using DFS replication. The data set size is 1.5TB in 13.5K Directories and 132K files. The MARS agent is set to create 2 recovery points / day (06:00 & 18:00). The rate of change on the data set is minimal. The data was subsequently protected with the MARS agent.
The MARS agent successfully backup up the initial data. Based on prompting in the MARS Agent and information in KB 3109750 / 3090067, we upgraded the MARS agent about 5 days ago to version 2.0.9028.0 (which I believe is the most current). Since the addition of the DFS/R data the creation of a new recovery point has taken a backup has taken a extremely long time to run to completion - i.e. A recovery point started on 2016/2/07 @ 18:00 UTC completed as at 2016/2/14 @ 05:00 UTC it moved 2.3 GB of changed data. 7+ days to create a recovery point is not acceptable during this time any additional recovery point creation operations fail of course!! The CBEngine process does not tax the server resources (CPU, Disk, Network) to any great extent. A proxy is not configured and the MARS agent throttling is not set.
Observation of resource utilization in Resource Monitor on the server show very low CPU usage (. Hi, Thank you for posting your query here! Monitor the next scheduled backup or use Backup Now to perform another backup immediately. The error should not recur as the file corruptions should be fixed when the backup is performed again.
I see that you have the latest version of Azure Backup Agent. If the problem persist, you may want to send us the CBEngine logs location @ C: program files Microsoft Azure Recovery Services Agent Temp zip them all and send it to v-saahme @ Microsoft dot com. Best Regards Sadiqh Ahmed If a post answers your question, please click Mark As Answer on that post and Vote as Helpful.
I have a brand new Dell PC (Intel i7 processor) running Windows 7 Home Premium 64bit. (OEM) I have about 350gb of data that I have transfered onto the new PC.
I have tried running Windows 7 backup to two different external drives. It seems to take 24 or more hours to run a backup with Windows 7.
On my old PC with Vista it took 3-4 hours to backup the same data to the same drives I can drag and copy files to a portable drive in about 3 hours Here is what I did: External drive shows 99% free space. Ran error check on both PC and external drive. Used settings for automatic fix file system error as well as attempt recover of bad sector.
PC is running normally. Power state is normal.
No other programs running. Logged in as administrator (I have no other uses.
Just me as administrator) Opened Windows 7 Backup. Select 'let me choose' what to back up. Chose Local Disk 'C' and 'Include a System Image' box Executed backup This process should take a few hours, not a day. What else can I try to speed up the Windows 7 backup process?
Hi ColoradoHi, I would suggest you to temporarily disable the anti-virus and firewall, check if the problem still persist. Note: Make sure you enable the anti-virus and firewall once the process is complete. If yes, then I would suggest you to perform backup process in Clean boot.
To help troubleshoot error messages and other issues, you can start Windows 7 by using a minimal set of drivers and startup programs. This kind of startup is known as a 'clean boot.'
Slow Network Backup From Agent For Machine
A clean boot helps eliminate software conflicts. Log on to the computer by using an account that has administrator rights. Click Start Collapse this imageExpand this im, type msconfig.exe in the Start Search box, and then press ENTER to start the System Configuration Utility. Collapse this imageExpand this If you are prompted for an administrator password or for confirmation, type your password, or click Continue. On the General tab, click Selective Startup, and then click to clear the Load startup items check box. (The Use Original Boot.ini check box is unavailable.) 4.
On the Services tab, click to select the Hide all Microsoft services check box, and then click Disable all. Note Following this step lets Microsoft services continue to run. These services include Networking, Plug and Play, Event Logging, Error Reporting, and other services. If you disable these services, you may permanently delete all restore points. Do not do this if you want to use the System Restore utility together with existing restore points. Click OK, and then click Restart.
For further information, visit the below mentioned link: Steps for Normal startup: 1. Click Start, and then click Run.
Type msconfig, and then click OK. The System Configuration Utility dialog box is displayed. Click the General tab, click Normal Startup - load all device drivers and services, and then click OK.
When you are prompted, click Restart to restart the computer. I-o data usb hdds powered by tuxera ntfs for mac mac. You may also refer the below mentioned links. Hope this information helped! Thanks and regards, Fouzan – Microsoft support.
Visit our Microsoft Answers Feedback Forum and let us know what you think.
Troubleshoot slow backup of files and folders in Azure Backup. 4 minutes to read. Contributors. In this article This article provides troubleshooting guidance to help you diagnose the cause of slow backup performance for files and folders when you're using Azure Backup. When you use the Azure Backup agent to back up files, the backup process might take longer than expected. This delay might be caused by one or more of the following:.
Before you start troubleshooting issues, we recommend that you download and install the. We make frequent updates to the Backup agent to fix various issues, add features, and improve performance. We also strongly recommend that you review the to make sure you're not experiencing any of the common configuration issues. If your Azure issue is not addressed in this article, visit the Azure forums on. You can post your issue in these forums, or post to.
You also can submit an Azure support request. To submit a support request, on the page, select Get support. Cause: Performance bottlenecks on the computer Bottlenecks on the computer that's being backed up can cause delays. For example, the computer's ability to read or write to disk, or available bandwidth to send data over the network, can cause bottlenecks. Windows provides a built-in tool that's called (Perfmon) to detect these bottlenecks. Here are some performance counters and ranges that can be helpful in diagnosing bottlenecks for optimal backups.
Counter Status Logical Disk(Physical Disk)-%idle. 100% idle to 50% idle = Healthy. 49% idle to 20% idle = Warning or Monitor.
19% idle to 0% idle = Critical or Out of Spec Logical Disk(Physical Disk)-%Avg. Note If you determine that the infrastructure is the culprit, we recommend that you defragment the disks regularly for better performance. Cause: Another process or antivirus software interfering with Azure Backup We've seen several instances where other processes in the Windows system have negatively affected performance of the Azure Backup agent process. For example, if you use both the Azure Backup agent and another program to back up data, or if antivirus software is running and has a lock on files to be backed up, the multiple locks on files might cause contention.
In this situation, the backup might fail, or the job might take longer than expected. The best recommendation in this scenario is to turn off the other backup program to see whether the backup time for the Azure Backup agent changes. Usually, making sure that multiple backup jobs are not running at the same time is sufficient to prevent them from affecting each other. For antivirus programs, we recommend that you exclude the following files and locations:. C: Program Files Microsoft Azure Recovery Services Agent bin cbengine.exe as a process. C: Program Files Microsoft Azure Recovery Services Agent folders. Scratch location (if you're not using the standard location) Cause: Backup agent running on an Azure virtual machine If you're running the Backup agent on a VM, performance will be slower than when you run it on a physical machine.
This is expected due to IOPS limitations. However, you can optimize the performance by switching the data drives that are being backed up to Azure Premium Storage.
We're working on fixing this issue, and the fix will be available in a future release. Cause: Backing up a large number (millions) of files Moving a large volume of data will take longer than moving a smaller volume of data. In some cases, backup time is related to not only the size of the data, but also the number of files or folders.
This is especially true when millions of small files (a few bytes to a few kilobytes) are being backed up. This behavior occurs because while you're backing up the data and moving it to Azure, Azure is simultaneously cataloging your files. In some rare scenarios, the catalog operation might take longer than expected.
The following indicators can help you understand the bottleneck and accordingly work on the next steps:. UI is showing progress for the data transfer.
The data is still being transferred. The network bandwidth or the size of data might be causing delays. UI is not showing progress for the data transfer. Open the logs located at C: Program Files Microsoft Azure Recovery Services Agent Temp, and then check for the FileProvider::EndData entry in the logs. Ter gusb2 n xp driver for mac. This entry signifies that the data transfer finished and the catalog operation is happening. Don't cancel the backup jobs. Instead, wait a little longer for the catalog operation to finish.
If the problem persists, contact.