Many small files isn't too much of a problem on fulls, but is painful for incrementals. I have a 650GB qtree with 10 million files. The full takes about 16hrs, and the incremental takes 3-4hrs, most of which is just figuring out which files to back up. On both full and incrementals, no data is written to tape for the first 2+hrs. This isn't as big a deal on fulls (~40GB/hr average), but makes incrementals take much longer then similar sized volumes with fewer files.
Once either the full or incremental starts moving data, the speed is similar to any other data.
John
John,
I am in the same boat with you are. Have you try to do restore yet? It is painfull. The reason is, depends on how large your index for NDMP backup. With 650GB and then your index size will be very large. I have two volume vol0 and vol1. Vol0 is about 770GB and vol1 about 350GB. I break them up into 4 different qtree NDMP back up will be with in or under 8 hours for Full backup. But the restore it can take about 24 hours to restored about 100 files with 5k sizes.
All I can think about NDMP back up is: it is fast, but you need to have lots of small qtree about 200GB or under or. The reason is to help for restore file(s) when needed.
This is just my two cents.
Thanks,
C-
Many small files isn't too much of a problem on fulls, but is painful for incrementals. I have a 650GB qtree with 10 million files. The full takes about 16hrs, and the incremental takes 3-4hrs, most of which is just figuring out which files to back up. On both full and incrementals, no data is written to tape for the first 2+hrs. This isn't as big a deal on fulls (~40GB/hr average), but makes
incrementals
take much longer then similar sized volumes with fewer files.
Once either the full or incremental starts moving data, the speed is
similar
to any other data.
John
-
Courier -
John Clear