In this last post of my series about Backup Exec 11d and Continuous Protection Server (CPS), I will sum up my view about Symantec's CDP solution.
- Pip install Boto3 - Thu, Mar 24 2022
- Install Boto3 (AWS SDK for Python) in Visual Studio Code (VS Code) on Windows - Wed, Feb 23 2022
- Automatically mount an NVMe EBS volume in an EC2 Linux instance using fstab - Mon, Feb 21 2022
I don't know, if you were always able to follow me in my review about Backup Exec 11d and CPS. The interaction between these two tools is quite confusing, sometimes. It took me quite a while to figure out how everything works. The fact that one has to configure continuous backups of files in CPS and continuous backups of Exchange in Backup Exec is quite strange in my view.
Symantec tried to unite two different backup paradigms in one product using two separate tools. From my point of view, this unification is a complete failure. Continuous data protection and conventional backups don't fit together.
I mentioned it already in a former post. It makes much more sense to use a CDP tool which also supports backups to tapes. Microsoft's DPM v2, for example, is much easier to configure and to handle than Backup Exec 11d and CPS, because it doesn't have all these functions needed for conventional backups.
Symantec obviously wants save its investments in Backup Exec. If you just need continuous data protection, you have to buy the whole product even though you don't intend to run conventional backups, anymore. This makes Backup Exec more expensive than it has to be. In the long run this might be a big handicap.
Subscribe to 4sysops newsletter!
We've been using Backup Exec since the time it was still owned by Seagate. As things stand now, it is quite probable that we'll move to DPM v2 as soon as the final is out. It is really a pity!