02-02-2016 07:09 AM
Run full backup on the weekend and incremental from Monday to Friday.
Use deduplication in policies.
The schedule "Full_Mensal" run in MSDP disk and copy to tape (duplication) SLP.
--> Why Monday's full backup runs? It is set "Incremental"!!!
Thanks.
Solved! Go to Solution.
02-04-2016 08:55 AM
Hi Mak Solution, thanks for the tip. I did exactly this setting.
sdo, I understand you, but do not do dedupe at the client, it is not a very good hardware, moreover have a network of 10G.
Marianne, run backup to disk at night window (faster) and I duplicate out of the window.
02-04-2016 09:11 AM
Your daily diff are quite small relative to the full. Therefore server is fairly static. If you employ Accelerator and NTFS Change Journal and Client Side dedupe - you might drastically reduce your backup time.
e.g. I have a 1TB (yes, 1100GB) Hyper-V lower power VM that is a file server, quite static, hardly anything ever changes on it, full backup in 1 hour (sometimes as quick as 30 minutes), and a daily 25GB differential in 1 hour too - or a 50GB daily diff in 90 minutes.
Your daily diff's are around 40GB to 100GB.
N.B: Because you have a very high file count, then if the disk containing the NetBackup Client binaries is tight on space, or a poor performer, then it might be worth re-locating the accelerator track log quasi-database to another volume with more space, or which is more performant - but preferably empty and not used by anything else - e.g. maybe get a new small-ish LUN presented purely to hold the accelerator track log.
02-05-2016 05:08 AM
Marianne, run backup to disk at night window (faster) and I duplicate out of the window.
If this is the only reason for disk backup, you may as well use BasicDisk.
As per Mark's post:
If you want it to work to its best give it a decent retention period .. you will get better dedupe, faster accelerated backups and a less overworked system
The standard recommendation is 2 weeks on disk.
Retention on disk should not be less than 1 week.
If you cannot keep backups on disk for this long, then MSDP calculations were done incorrectly.
Or your environment has grown faster than anticipated.
02-16-2016 01:05 PM
Hi...
thank you for the tips!!
*retention in disk: 8 day
02-16-2016 01:13 PM
How is your post the solution?
02-16-2016 05:10 PM
02-18-2016 06:25 AM
Hi all,
I always try to be fair with my attitudes, but there was no comment similar to what was effectively configured.
the one who said something was Mark_Solutions still later.
But come on, tell me what was the comment that deserves solution.
02-18-2016 07:51 AM
02-18-2016 07:55 AM