Backup Exec 2010 Deduplication Set Up and performance
I would like some feedback on the following scenario. We are undergoing a refersh of our Novell Netware environment and it's dovetailing into a new implementation of Backup Exec 2010.
We have implemented SLES/OES with NSS volumes. I have installed the Linux agent on the servers. There is a new install of Backup Exec 2010 installed on Windows 2008 Standard 64bit. I have a separate partiton of a RAID 5 violume designated as deduplication folder. (it's a 800GB raid 5 with 100Gb dedicated for C: and 700GB dedicated for D:). We have purchased the DeDuplication option to back up two remote servers over WAN links.Iknow that the dedup folder should be a separate volume, does it need to be physically separate?
Do I define the jobs the same as I would backing up to tape (full Fri. nite and incrementals M-R)? As it is right now, they are. The back up everything on the server (OS and NSS volumes, not the iFolder storage however). When the first incremental ran, it ran pretty much as a full and I expected that since it was all new data to the server. The full ran and backed it all up again, then the incremental is also backup it all up over again. What have I configured wrong? Also, performance over the WAN links degrades over time. It will slow to 23MB/min.
I've tried looking for some docs online and I have found the best practices docs. They are not granular enough to define the job, retention level, etc..
Let me know your thoughts.