FUll backup is taking 2 days to complete

i have a maintenance plan setup for full backup and the total size of databases is around 4 TB. compress backup option is also enabled.
it takes around 2 days to finish every week, what can be the potential problem?
Regards
k

Hello,
Could you please describe that local drive? Is that local drive part of RAID?
Is that drive dedicated for backups or it is shared with the operating system and SQL Server databases/binaries?
How many cores/cpus on that computer?
Could you please share the result of the following query?
SELECT
TOP 40 *
FROM
sys.dm_os_wait_stats
ORDER
BY wait_time_ms
DESC
Could you please share with us the average values of the following Performance Monitor (Control Panel) counters?
Object: Physical Disk / Logical Disk
Counters: Avg. Disk sec/Read, Avg. Disk sec/Write, Avg. Disk sec/Transfer, Avg. Disk Queue Length
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

10.5.5 Initial backup is taking DAYS (!!) over firewire 400

I ran into an issue where I had to erase my Time Machine backups on my external FW400 OWC Neptune backup drive. Not a big deal as I also use Superduper for bootable backups.
so last week I tried doing a new initial backup and it's taking days literally to get just under half done. Did 10.5.5 fry firewire somehow? up until now I had normal firewire 400 speed.
my work machine is 10.5.5 MDD dual 867 G4, 200/80 GB drives, 2 GB RAM backing up to an OWC Neptune FW400 drive with 500 GB drive partitioned as 350 and 114 gb paritions.
I tried running Disk Utility and found no errors, I repaired permissions for good measure
Any thoughts?

Ok I ran Diskwarrior 4.1 on the G4 and fixed a few minor errors
I then ran it on my backup partition (the 350 GB partition of the Neptune drive)
I got speed inhibited by disk malfunction error followed by the number. I've used DW enough to know that that that's not good.
Just for kicks I ran DW on the 114 GB partition of the Neptune drive and it reported no problems. Does that mean it's not a hardware failure????
I then rebooted the G4 and attached the drive via firewire 400 to my mid 2007 MacBook Pro and ran disk utility (my thoughts were it might be bad firewire ports on the G4. I have the standard 2 plus 4 more on a PCI card).
Disk utility reported no errors.
Now I am using DW to check the files and folders on the backup drive for problems....

FileVault is taking days to complete the process

Hi,
I activated FileVault when my Mac started with keyboard issues as I knew I had to take it to a technician. It did not completed the process then, as my keyboard died and I forgot about FileVault. After my keyboard was replaced I noticed it too slow and I believe it is because it has still not finished the process (it's been days!). What can I do?
Thanks.

Back up all data before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe.

Aperture 3 Importing Folders as Projects is taking days to complete

Hello,
I acquired Aperture 3 a week ago and decided to give it a try. I've been using Lightroom since version 1. All my photos are in NEF (Nikon RAW) format and stored on an External HD. I used the A3 option FILE > IMPORT > FOLDERS AS PROJECTS command and selected folders from year 2008, 2009, 2010...this are 109 folders (13401 photos) from a total of 348 from year 2003 to date, meaning I am importing a fraction of all photos.
A very important note: I use the import option "Store Files: In their current location"...so that A3 is not moving, copying and so on, any files - it's just referencing them.
The problem starts here - it took Aperture 3 almost 24 hours to complete the "import"...i.e. to fill all the Projects with the corresponding photos. But the IMPORT PROCESS continues forever, today is day 4...the Aperture Library on this has grown to 18 GB and still growing. There is small but constant Hard Disk activity between the External HD with the Photos and the internal HD with the Library.
If I try to quit Aperture I get a message box:
+"Do you want to continue importing? Aperture is currently importing files. If you quit, the import task will be canceled and any files that have not been fully imported will be removed. | Quit | Continue |"+
How much longer shall I wait? Is it really importing or is this a bug? Why is there no progress bar or counter to give an estimate or idea of what is going on?
Just as reference: I imported the same folders (109) into Lightroom 3 Beta with the option "Store Files: In their current location" and it took only 1-2 hours.
Any help is highly appreciated.
Regards,
Kostadin

Kostadin,
I'm noticing same thing today. This morning I imported about 100 Canon 7D RAW images from my memory card, which took about 5 minutes upon which I got the "Delete Images and Eject Card?" dialog. I accepted and removed the card.
4 hours later, I still have a "Importing..." spinning ball on Aperture. For the first couple of hours, I was trying to send emails with a few images and it would take 20 minutes for Aperture to generate the JPEG in the email. Now it only takes 10-15 seconds. BUt it is still "importing". So aperture continues to function, but it has some process going which keeps my CPU fans running on the MacBook Pro.
I am anxious to see just how long it takes to IMPORT... after it finishes importing.
What's it doing for this long?
Jim

Time Machine won't create a bootable full backup

Equipment : Mid 2010 13" Unibody MBP, Late 2010 1Tb Apple Time Capsule, 4Gb RAM, 240Gb HDD, OSX Mavericks
Upgraded to Mavericks a few months ago, Time Machine has been backing up incrementally to my 1Tb Time Capsule no problem for years.
I have just bought a SSD so , feeling very confident, popped out the Seagate Momentus and replaced with PNY 240gb SSD. Booted off my Mavericks recovery CD, selected restore from a previous Time Machine Backup, selected My Time Capsule, MyMac.sparsebundle,Continue
To my horror, the last full backup was June 2012, kind of worked out why - I had some Exclude options in Time Machine preferences that excluded /Caches , Download folder, Trash so wasnt creating any Full backups
In order did the following
Put the Seagate HDD back in and booted up successfully
removed all the excludes in Time Machine ,
renamed MyMac.sparsebundle to MyMacX.sparsebundleX ,
kicked off Back Up Now in the confidence that this would create a brand new backup and do a full backup of the disk
It didnt, what looked like a full backup started taking about 2h though no full backups found in the newly created MyMac.sparsebundle, so something isnt being backed up to make a full bootable backup
Checked to see if there were any other system excludes with
sudo defaults read /Library/Preferences/com.apple.TimeMachine SkipSystemFiles
Answer came back as 0, so obviously not that
Rebooted my Mac and Time Capsule, deleted MyMac.sparsebundle, did step 4 again
Exactly the same result.
So at this time, I cannot create a full backup to enable a HDD swap out with my SSD
Help, Ideas anyone

You need to partition and format the drive first.
Drive Partition and Format
1. Boot from your Snow Leopard Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
Quit Disk Utility after formatting is finished. Install Snow Leopard. Upgrade to Mavericks.

Keeping ARCH and Deleting FULL backups on RMAN

Dear all,
RMAN deletes all my full backup and archivelogs in 2 days with;
DELETE NOPROMPT OBSOLETE RECOVERY WINDOW OF 2 DAYS;
But I want to keep archivelogs at least 9 DAYS and delete just the FULL backups after 2 DAYS. How can i set this?
Any recommendations?
Regards

You reported the Sybrand's post as an "abuse to consider" to the mod. Not to take a part or the other, but Sybrand made several points you should yourself to consider up front :
1. you claimed your problem as an emergency case, it is considered as rude in a public forum based on volunteers.
2. also you did not provided any information which can make difference, as the minimum of Oracle version (and OS...), for one who want to be considered as an emergency, that's rather strange, no one here is sitting next to you
3. Sybrand gave you a command to run that you should see the suggestion resulted
4. He also made a point about the documentation, whether it can appears rude to you, it's always, ALWAYS, good to show exactly to your peers what you have done so far to solve your problem, based on what docs...
5. We could also point you a link such as How to ask question
Please, keep it in mind, and come down.
Nicolas (moderator).
PS: without saying that 2 mods spent their time to proceed with your faulty reported abuse case
Message was edited by: Nicolas.Gasparotto

2 full backup's at one time

Hello!
We use IBM Tivoli Storage manager for backup our database 11.1.0.7 to SBT_TYPE.
Can we do 2 backups at one time, if we use 2 dsmc schedulers and 2 TYPE's (Not same SBT_TYPEs) - drive's ?
Backups are full (using RMAN).

We do not delete our full backups for 22 days and do 1 arch copy at month to another device. (and save it for 1 year)
I tested that full backup to SBT_TYPE with archive copies running ok with level1 backup and with incr backup arch files at every 1 hour.
I only intersting is it possible to take 2 backups at 1 time...

Backup taking days together

Hello Everyone..
Let suppose, a backup process is used to get completed in 2 hours.
All of a sudden, if it is taking days together to be completed, what might be the reasons?
Thanks and Regards, Junior SQL Server DBA, Miracle Software systems, Inc.

Hi,
Further of Shanky and Saeid posts, and as mentioned, we need much more information in order to point the finger on the specific problem. I do agree with Shanky that locks and waits will not be my first monitoring operation (it will come later on). We can
try to throw some idea of what can be the problem for several ays without more information. So I will add some ideas till we will have more information.
* Check the Machine general performance (CPU, Memory, Disk IO, etc), especially if you are using compress check the CPU (check the time/cpu without compress).
* check for waits and locks
* Check for too many VLF in the log file
* Check How big is your log file and how much of it is in use
* Check if the bottleneck is on the write speed. You can check it using Backup to nul (ont forget to use WITH COPY_ONLY)
As I mentioned this is only some points need to be checked/change... there is much more on this subject :-)
I will try to write a short blog maybe on this issu
I hope this is helpful :-)
[Personal Site] [Blog] [Facebook]

HT3275 For the past several days, I have been getting this message during backups: Time Machine could not complete the back up. The backup disk image "Volumes/Data/iMac.sparsebundle" could not be accessed (error-1).

For the past several days, I have been getting this message during backups:
Time Machine could not complete the back up. The backup disk image "Volumes/Data/bhoppy2's iMac.sparsebundle" could not be accessed (error-1). When I click on the 'help' icon on the message, it reverts to a blank page, and I cannot find anything online regarding the term 'sparsebundle.' In addition, I cannot access previous backups any longer.
Help?

See C17 in Time Machine Troubleshooting by Time Machine guru Pondini:
http://pondini.org/TM/Troubleshooting.html

First backup is taking forever (more than two days) in my MacBook Air

First backup is taking forever , painfully slow, I am using MacBook Air, what can I do to speed things up. is there a particular way to set TC up ?? I set it up to join an existing wireless network, is this right or wrong? I just need a few tips to make the backup faster.

Answer: yes, the Time Capsule is junk - in my opinion. I was excited about an all-in-one router plus 1TB of backup wirelessly available, but if you check the many posts about this thing, you'll hear about numerous problems:
- unbelievably slow backups, overnight or longer for the first, very long for even small backups after minor activity - and not necessarily due to network speeds.
- heat issues - this thing runs very hot, even with fans running, and people have had to put little rubber feet under it to improve airflow, etc. - not something I think is reasonable for a $500+ item - some get an "overheating" message from the utility app.
- problems with hanging - it hangs on "Preparing Backup" (as it did for me for days) and doesn't backup - thereby making the unit useless as it was designed.
- mounting and recognition issues - not so much with me but for quite a few others.
SEND IT BACK... I am sending mine back and going back to manual backups where I can see exactly what is being backed up to my external HDD and where it is. The opaque nature of the entire Time Machine backup is irritating to me - TC was "backing up" say, "75MB of 125.3MB" but I had no idea what it was backing up, and why only 125.3MB? Was that all my activity changed during the session? Or all sorts of system files, etc. being backed up? I'm not techie enough to get into the guts of it, so I am going back to my usual external HDD to do it by hand. It's a good habit to get into (if inconvenient compared to the TC) but at least I am secure with it.
I am also not sure if TC can be used as a plug-and-play USB storage drive if I were to, say, just connect it to a Windows machine and try to access files in folders. I suppose not?

Maximum Express full backups per day per Datasource?

I have 3 DB server having 24 databases. Some of these are SIMPLE recovery model and some are FULL. Express full backups are set one in a day at 8:00 PM and Synchronization is set to every 4 hours.
Now customer want to keep backup of every 2 hours. So I have some queries on this.
1) Its not possible to set EXPRESS full backup after 2 hours. So what should I do here, Should set synchronization frequency to 2 hours?
2) If I set Synchronization Frequency to 2 hours, it will backup only FULL Recovery model databases only? SIMPLE one will be backed up 8 PM only?
3) Incremental Backups recovery is only allow to restore Instance? cant be copy to Network folder? As when I tried to restore 4 hours synchronization backup it shows cant be copied, only recovery point associated with express backup will be copied.
4)Based on my understanding, I should change all recovery models to FULL and should set Synchronization to 2 Hours to achieve customer demand. It will allow me to restore 2 hours recovery point to directly Instance or another instance (But not to Network
folder and tape in case of Incremental recovery)
Am I right? Thoughts!
Thanks in Advance
VJay

See.
My 4 hours Synchronization frequency/Incremental backups are creating recovery points successfully and I can see these from recovery tab. But when I am trying to restore Incremental recovery point, it doesn't allowing me to restore. See in below image, I
am trying to restore Incremental recovery point which was created yesterday at 4:00 PM but its asking me to restore yesterday's 12:20 PM. This incremental backups tooks place after 12:20, doesn't mean anything in terms of recovery!
As my final decision, should I choose EXPRESS Full backup for evry 2 hours and Synchronization just before Express backup for these 24 databases since these are now in FULL model.

Full backup every day

Hi All,
for the last few days for some reason, Time Machine (using Time Capsule) is backing up entire content of my disk (86 GB) once a day. After this is done, it creates incremental backups as it should, but on the next day, again full backup is being taken
I'm not sure what's causing this behavior, I did permission repair but this is still the case
Any help is most appreciated.

DanInDub wrote:
Hi All,
for the last few days for some reason, Time Machine (using Time Capsule) is backing up entire content of my disk (86 GB) once a day. After this is done, it creates incremental backups as it should, but on the next day, again full backup is being taken
Is that on the first backup after powering-up your Mac? If so, the preferences file may be corrupted. Try a "full reset," per #A4 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

After a complete restore of Mac from a Time Machine volume, I don't want a full backup the next time Time Machine backs up.

After performing a complete restore of my Mac from a Time Machine volume, Time Machine wants to perform a full backup the next time it backs up.This is normal: http://support.apple.com/kb/TS1338
But I don't have enough free space on my external hard drive to do this because my external hard drive already contains one complete backup. My hard disc on my MacBook is 320 and my external drive is 500 GB, so it doesn't add up. I don't want to delete the original backup in case something goes wrong during the new full backup. What can I do?

You don't have too many options. The best approach would be to buy a larger external drive. The guideline for Time Machine is that you should have 2-3 times as much capacity on the external drive as data you're backing up. See item 1 of Time Machine - Frequently Asked Questions. In any case, you can't prevent that first full backup unless you're willing to turn off Time Machine permanently.

How is taking a full backup on a new computer?

I now have a new computer I want run itune him, but the old data and backups do not appear on the new device, and whenever I took Backup, are not taking the program as it was before
How is taking a full backup on a new computer?
How is retain the photos and files on the iPhone?

You can authorize more than 1 computer with the same iTunes account. Of course you remember the iTunes account information you used on the PC right?

ACS 5.3.0.40 On-demand Full Backup failed.

Hi,
I have ACS 5.3.0.40 Primary Secondary Authenticators , of which the Scheduled backup has stopped.
When checked the :
Monitoring Configuration >
System Operations >
Data Management >
Removal and Backup
> Incremental Backup , it had changed to OFF mode. without any reason.
The same was observed earlier too.
I have made the
Incremental Backup to ON and intiated the
View Full Database Backup Now. But it wasn't successful and reported an Error:
FullBackupOnDemand-Job Incremental Backup Utility System Fri Dec 28 11:56:57 IST 2012 Incremental Backup Failed: CARS_APP_BACKUP_FAILED : -404 : Application backup error Failed
Later i did the acs stop/start "view-jobmanager" and initiated the On-demand Full Backup , but no luck, same error reported this time too.
Has any one faced similar type of error /problem reported , please let me know the solution.
Thanks & Regards.

One other thing; if this does end up being an issue with disk space it is worth considering patch 5.3.0.40.6 or later since improves database management processes
This cumulative patch includes fixes/enhancements related to disk management to avoid following issue
CSCtz24314: ACS 5.x *still* runs out of disk space
and also fix for
CSCua51804: View backup fails   even when there is space in disk
Following is taken from the readme for this patch
   The Monitoring and Reporting database can increase when as records are collected. There are two mechanisms to reduce this size and prevent it from exceeding the maximum limit.
1. Purge: In this mechanism the data will be purged based on the configured data retention period or upon reaching the upper limit of the database.
2. Compress: This mechanism frees up unused space in the database without deleting any records.
Previously the compress option could only be run manually. In ACS 5.3 Patch 6 there are enhancements so it will run daily at a predefined time, automatically when specific criteria are met. Similarly by default purge job runs every day at 4 AM. In Patch 6 new option provided to do on demand purge as well.
The new solution is to perform the Monitoring and Reporting database compress automatically.
2.       New GUI option is provided to enable the Monitoring and Reporting database compress to run on every day at 5 AM. This can be configured under GUI Monitoring And Configuration -> System Operations -> Data Management -> Removal and Backup
3.       Changed the upper and lower limit of purging of Monitoring and Reporting data. This is to make sure at lower limit itself ACS has enough space to take the backup. The maximum size allocated for monitoring and reporting database is 42% of /opt( 139 GB). The lower Limit at which ACS purges the data by taking the backup is 60% of maximum size Monitoring and Reporting database (83.42 GB). The upper limit at which ACS purges the data without taking backup is 80% of maximum size Monitoring and Reporting database (111.22 GB).
4. The acsview-database compress operation stops all services till 5.3 patch 5 , now only Monitoring and Reporting related services are stopped during this operation.
5. Provided “On demand purge” option in Monitoring and Reporting GUI. This option will not try to take any backup, it will purge the data based on window size configured.
6. Even if the “Enable ACS View Database compress” option is not enabled in GUI then also automatic view database compress will be triggered if the physical size of Monitoring and Reporting database reached to the upper limit of its size.
7. This automatic database compress takes place only when the “LogRecovery” feature is enabled, this is to make sure that the logging which happens during this operation will be recovered once this operation is completed. ACS generates alert when there is a need to do automatic database compress and also to enable this feature.
8. Before enabling “LogRecovery” feature configure the Logging Categories in such way that only mandatory data to log into Local Log Target and Remote Log Target as Log collector under System Administration > ... > Configuration > Log Configuration
This “LogRecovery” feature can recover the logs only if the logs are present under local log target.
9       This automatic database compress operation also performed only when the difference between actual and physical size of Monitoring and Reporting database size is > 50GB.
10 The new CLI “acsview” with option “show-dbsize” is provided to show the actual and physical size of the Monitoring and Reporting database. This is available in “acs-config” mode.
           acsview     show-dbsize     Show the actual and physical size of View DB and transaction log file

FUll backup is taking 2 days to complete

Similar Messages

Maybe you are looking for