BackupExec deduplication manager service failed to start
Hi all I have a backupexec appliance 3600 R4 wint BE15. This appliance is EOX, I know it, but our client maintains this old infraestructure and now I have a problem. This appliance had 2 disks failed and the the RAID was offline. Our client bought the 2 disks and we replace that on the appliance. The rebuilding RAID process was apparently successful and now on the appliance web UI show us all disks online an also the RAID. But now, when I try to start the BackupExec services I have this error for BackupExec deduplication manager: I can see this detailed status on Windows EventViewer: But when I try to verify the D:\Appliance_Dedupe\etc\pdregistry.cfg file I can't access to the folder (D:\Appliance_Dedupe is the appliance's deduplication folder): Anyone can help me with this? Thanks in advance. Regards Toño
Duplicate Jobs stuck in Active Queued
Veritas support has been worse than useless. We have a CAS MBS enviroment, duplicate jobs are scheduled to run every week from MBS to Deduplication storage on CAS but will get stuck in the active queued state for hours without any data transfer. No failure and no events in logs. Many weeks ago there was an Alert about Robotic Libraries but it has been cleared and not appeared since. Vertias support had me run an inventory on Dedupe storage, recreate storage, update all servers to 20.5, and generate several different logs. All to no avail. Any ideas are welcome.
What you can store and transmit with deduplication seems to very sensitive to deduplication rates.
The charts in the PDF are theortetical it would be interesting to see if others are getting results like these? From what I can see the ability to deupe data can have a significant impact on storage and transmission.
Access 7.4.2 GAs on October 1 2018
Today (10/1/18) marks the release of the 7.4.2 version of Access. The new release has several new features, but by far the most important of those features is support for NetBackup deduplication on the Access Appliance. Deduplication targets cost-of-ownership reduction (a key focus for the Access Appliance) with features like support for client-direct data deduplication, and multi-domain global deduplication. Most of the Access collateral has been rewritten for this new functionality. Check out the blog here, or visit the Access web page here.Duplicate deduped NDMP backup (block-level) to cloud?
Hello, we have a Backup Exec (16 FP2) job which backups data (mostly vm images) from a NetApp to a deduplication storage via NDMP. As it is a file-level-based backup and the data of the vm images changes rapidly, no real incremental or differntial backups are possible. Is it possible to duplicate this deduped backup-set to a cloud storage (as offsite-backup) on a block-level base, so that incremental backups can be used and the data sent can be reduced? And can I use this duplicated backup to restore (single files) back directly to the NetApp or do I have to restore it first to a local storage and then back to the NetApp? ThomasHow to backup deduplication storage to external drive?
What is the proper procedure to make a backup of an entire deduplication storage directoryto external storage? In the backup job setup, there is both the raw directory structure of the drive letter and directory name "E:\BackupExecDeduplicationStorageFolder\" .... but there is an additional section under "Shadow copy components" with "Configuration" and "Storage" as possible selections. So which do I choose to backup? Both of these? Or only the shadow copy components? The target of the backup is a large external USB drive, with backup compression enabled. , Also, is this really enough for the dedupe data to be usable if restored in the future, or do I need to be backing up some additional SQL database that is associated with the deduplication disk directory?Exchange backup to deduplication storage or not?
I'm wondering what are your thoughts about this process... We currently backup our Exchange 2010 server like so. Full backup (MB database and logs) once a week, send it to our deduplication storage and then, duplicate the job to another deduplication storage offsite and also duplicate it to the tape. Incremental everyday to simple disk and duplicate it to another simple disk offsite. When the duplicate job for the tape run, the speed is very slow, yes I know, it's because of the rehydratation process. The total size of the data is almost 1 TB. So the job take, on average, 2 days to run, plus or less 48 hours. During that time, the tape is unavailable for other, critical jobs. I need that tape drive for other jobs, 2 days is too long for me, I want to submit to my boss, the architect of the infrastructure, the point that we should store the full backup to a simple disk storage instead of the deduplication store so that the job of the duplication to the tape is much faster. The point that he will make is that we save a lot of space when storing the full exchange backup to the deduplication storage. But I'm wondering if we save that much space by sending the backup to the dedup storage. I can't find the info of the space that the backup of Exchange take on the dedup itself. What is your experiences and thoughts about this process? Thx for sharing.
