We've had various issues with DLO and have been through several support tickets over the past few years, but the bottom line is we are still struggling to get this working reliably. Are we the only ones? Just recently, we deleted ALL computers via the console, stopped all the agents on all the desktop, and deleted all the LUDF files and settings folders in an attempt to "reset" the backups. After doing this, we ran dedupe Garbage Collection which only resulted in errors in the event log that all the files in dedupe storage were the latest version and therefore wouldn't be deleted! With no computers listed in the console, dedupe was still claiming an 80%+ deduplication savings which can't possibly make any sense since we had no data left in the NUDF.
Now, systems are backing up again after rebooting machines or restarting agents, but only the systems with failed or warning status show any sort of status. All of the successfully backed up machines show a Last Backup of "12:00:00 AM" in Setup->Computers, which basically is DLO saying "I don't know". On the Restore tab, the Last Backup Status of all machines except the failed ones is "Unknown", despite there being backup data available to restore and despite the clients having finished their jobs and being idle. As a further symptom, the only computers/users that show up in any of the reports are the ones with failed status.
Why didn't Garbage Collecion clear out all of the dedupe storage since we deleted all computers via the console? Why are successful machines not reporting status? How can we fix that? Is there a documented process, better than what we tried, to completely reset DLO (delete all data, all dedupe data and all database status for all users and computers) without wiping out all of our profiles and global settings?
Thank you,
