12-10-2014 04:40 AM
I have files servers with several millions of files... Even with NBU Accelerator, backup is still long.
Exemple : 6 Heures pour 3,6 millions de fichiers et 376 Go.
Do you think this is normal behavior - is there some "best pratices" to do this backup faster ?
Note : there is less than 1% of files modified.
12-10-2014 07:01 AM
Do you see the time difference between the first Full backup after enabling the accelerator and the later full backups?
does it taking the same time?
or in other words.. how much time is it taking without accelerator ?
12-10-2014 07:27 AM
I think the first backup was slower but I do not remember of the exact duration.
Even if no file has been modified, the backup is very long.
Below, you can see a copy of the Job monitor report... there are no new file (accelerator savings is 100%), but backup duration is about 6 hours.
Client Name | Job Duration | Job File Count | Schedule/Level Type | Protected Data Size(MB) | Accelerator Enabled | Accelerator Data Sent (MB) | Accelerator Savings(MB) | Accelerator Optimization % | Deduplication Enabled | Post Deduplication Size(MB) | Deduplication Savings (MB) | Total Optimization % (Accelerator + Deduplication) | Job Status |
p01 | 05:56:05 | 3657582 | Full | 385556,96 | Yes | 0 | 385556,96 | 100 | No | 385556,96 | 0 | 0 | Successful |
12-10-2014 11:20 AM
On Windows the use of Journal should speed up the backup especially one with few changes, worth looking into if are not already using the journal and the file server in question is Windows
We will be better able to answer you question if you post Job details from this backup
12-17-2014 01:23 PM
Be VERY carefull using change journal....it will create a change journal file on your default netbackup client install drive. I have a couple servers with multi-million files on them. I turned on change journal to try to speed up the backup....since I had the client agent installed on the C:\ drive....the change journal file filled up my C: drive and crashed the server. I un-installed the agent and re-installed on another drive and re-ran the backup. When the backup finished...the change journal file turned out to be 120GB and the backup ran 30minutes less than it was running. To me it was NOT worth it. The best method I have found for LOTS of little files is flashbackup.
12-18-2014 01:15 AM
I have another case (server is a W2008R2 with MSDP) :
After migration from 7.5 to 7.6, deduplicated backups with accelerator are 4-6 times longer.
But even in 7.6, just after a reboot, duration become fast again only one time... and then subsequent backups are again 4-6 times longer !
I was ine 7.6.0.3... I have applied 7.6.0.4 but nothing has changed !
Is anyone seen something similar ?
02-09-2015 05:12 AM