Same answer: it doesn't seem that the hardware is up to snuff. Backups are taxing on the server but in a good deployment it should not affect the users. How big are the files? What hardware do you use?
Could you give som extra information:
- How many files.
- Size of the files (sum)
- Size of the largest files (MB/GB for each)
- Did you turn Verify Backup Integrety on?
- Computer - OS, GHz, amount of RAM, 64 or 32 bit (PC).
- Disk system, bus, disk type how large, how fast. Do you have a fair amount of free space on the disk?
My first advice: If the backup is to slow, turn "Verify Backup Integrity" of for the backups running each hour. Make a verified backup before the workday, during lunch break and in the evening ... or at some other time according to your schedule.
But if the computer is well configured backup should not cause problems.
Thanks Carsten, got the info.
How big are the files? Can you specify what kind of hardware and OS you're running?
10 FP7 files, the largest are:
Hardware and Software Platform:
MS Windows 2003 Standard, SP2, 32-bit
Dell Poweredge 2950
- 16.0Gb RAM (only 4 register w/ Windows 2003 32-bit)
(2) Xeon E5430 Processors, Quad Core
Drive C: 67.7 Gb, 48.0 Free
Drive G: 122.0Gb, 111.0 Free
Drive H: 286.0Gb, 238.0 Free
Verify Backup Integrity = On
What do think Carsten? Not too many files? Hardware and software platform pretty good?
But your idea about turning off Backup Integrity seems worth a trial. Do you think that is where we should begin.?
Finally, when we have hourly or periodic backups what is your recommendation for reporting. Should we pull a copy of the backup to a desktop to do reporting with FM Pro?
The backup problem
Yes: Set the backup schedules running during the day to Verify Backup Integrity = Off
This should solve or minimize your problem at once.
But at the same time you should create a backup schedule running during the evening/night set to Verify Backup Integrity = On
Your hw and sw setup seems to be OK and it is absolutely correct to run with 32 bit with FileMaker 11. For FileMaker 12 I would recommend 64 bit.
I would consider finding a solution to do the reporting online instead of taking a copy offline. It would be a good idea to isolate why the generation of reports is so slow.
In the meantime you can of course do the reporting with off-line copies of the database.
Ps. FileMaker Server 12 will be a lot faster than 11 for most tasks. You should of course consider upgrading to FileMaker 12 within the next 1-6 months.
Thank you Carsten. We are going to try running backups without "backup integrity on." Then later we will look to converting to FM Server 12.
Sounds good. I would suggest that you take the first step (disable the integrity check) and then start testing your solution with a test conversion to FileMaker 12 later this year.
Could you report back, whether the problem is solved or at least minimized by disabling?
Carsten, I will be happy to give you the results. -Ken