Problem I hear people talking about:
Backups used to backup to destinations looking like this
It is now looking something like this:
This is a really big change. Does anyone know if the folder is actually being renamed from the old to new or is it creating a whole new folder? Also, I have heard that after the upgrade it kicked off FULL backups on every BUDR out there upon the next backup. Can anyone confirm this?
arobarHere is what we experienced:
Roughly half of our servers RENAMED their existing folders to , and proceeded with an incremental backup.
The other half created a NEW folder (leaving the folder alone), threw the error "No previous backups found", and proceeded with a full backup.
Obviously the intention was to make them rename their folders... But that didn't happen in all cases, and we've now got tons of new backups out there that we really weren't planning for.
What seems to work to prevent that though... If you manually rename the folder to , the backup software will look for that folder automatically and will perform an incremental.
mjezard(What the heck was wrong with the old way?)
Nathan CoulthardJust a thought, but can they put in the "DO NOT DELETE" text file, a list of all GUID and Associated Agent Names? Thus if we are searching manually through the backup device we can check this file to find what machine the data came from?
mjezardWhat's really got me stumped is where those new numbers are coming from and how to find out which folder equates to which machine now.
We seem to have a had a bunch of machines kick off Full backups which filled up the backup drive and now I can't find out which folder is which so that I can delete some old backups from machines that are not so critical.
Anyone know where these stupid numbers are coming from and how to cross reference them?
(What the heck was wrong with the old way?)