Justin, Thought I'd follow up with details before and after the changes based on the Microsoft link: OS with small files: W2K3 Standard (NTFS) Backup infrastructure: Media Servers with FC LTO II tape drives Before: 190.6 Gb of just small files - Backup time: 24 hours - Restore time: still didn't finish after 4 days After: 191.1 Gb of just small files - Backup time: 2:55 - Restore: 3:05 Scott
>>> Justin Piszcz <jpis...@lucidpixels.com> 11/30/2012 2:20 AM >>> Hi, Very interesting, thanks! Justin. On Fri, Nov 30, 2012 at 1:26 AM, Scott Jacobson <sjaco...@novell.com> wrote: Justin, Wish I knew about this years ago, it fixed an issue you've similarly described that we've had with legacy W2K systems. We created a VM with the settings below, copied the data over - yes it took time, but once finished; in one case keep the VM and in another case copied another servers data set back to Bare Metal. It worked. Backups are much better, but more importantly - the restores! http://support.microsoft.com/kb/121007 Scott Jacobson >>> "Justin Piszcz" <jpis...@lucidpixels.com> 11/28/2012 4:34 AM >>> Hello, Using 220.127.116.11, restoring 1m+ files in a single directory, obviously this would take hours/days (bpdbm just runs forever) to start so what I am doing is splitting it into chunks and that is helping (it works) but was wondering if anyone on this list knows of any special: DIRECTIVES for bpdbm in the bp.conf to optimize/help speed it up for restores? It seems there are some interesting ones: IS_ASCII_CATALOG_FILE_FORMAT SKIP_NOTIFICATION_FOR_UNIT_TEST INSIDE_CATALOG_CLEANUP CLEANUP_KILLED_BY_SIGNAL CATALOG_BACKUP_PARENT_JOBID INSIDE_ASA_BACKUP NB_BPDBM_TEST_DELAY_SOCKET_CLOSE KEEP_EXISTING_DOTF_DURING_IMPORT NB_BPDBM_ALIVE_LOCAL_TIMEOUT There are more as well, does anyone have any tips to improve restore performance of lots of files? Justin.
_______________________________________________ Veritas-bu maillist - Veritasemail@example.com http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu