I have a customer who backs-up a folder called clients which contains 150,000 sub folders in it with the customers ID as the folder name. Within these folders are subfolders for each incident the client raises. So the folder structure is similar to:
\\Server\share\documents\1\1\
\\Server\share\documents\1\2\
\\Server\share\documents\1\3\
all the way to:
\\Server\share\documents\150000\1\
\\Server\share\documents\150000\2\
\\Server\share\documents\150000\3\
The customer users Backup Exec 2012 SP3 v14. Rev 1798 (64-bit)
When we try to expand the restore wizard to restore some accidentally deleted files, it takes ages for the tree structure to expand the 150,000 subfolders in the documents folder. That is if it doesn't error with "Query Failed"
We seem to have found a pattern to the "Query Failed" message when expanding the folder, in that, if you have expanded the folder previously without re-starting the backup exec administrator, it will usually fail on the second attempt to expand the folder, memory for BackupExec.exe will continue to grow above 3Gb and CPU usage consumes a logical processors time. If you load BE 2012 and go straight to the restore Wizard it eventually opens the folder, after a long wait (which is expected as there are so many folders).
After being able to expand the folder, if we then try and open a sub folder from within the clients folder e.g. \\Server\share\documents\150000\2\, the wizard hangs. CPU usage goes up, and the backupExec.exe keeps consuming more and more memory (I killed the process when it hit 6gb), but it didn't look like it was going to stop growing for 20 minutes.
Is there another way to restore the files?
why does the memory usage increase so much?
why does backup exec hang?
Any help appriciated!
