Wu,
I have a very similar NT machine with this same problem. (The stats
for it are listed below).
This machine did not have enough memory to do a normal backup. I had to
turn on the 'memoryefficient yes' option in the dsm.opt file. This
actually helped speed it up from 10 hours down to 6 due do the amount of
memory to disk swaping caused by the dsmc process.
You may want to try the 'memoryefficient yes' option, or add in 1 GB of
memory for every million files.
Due to a really slow network I turned on client compression and saved
some time there.
I have found that other operating systems backup 1 million+ files much
quicker than NT. (maybe due to some overhead caused by the 8.3 file
aliasing, which (so I have heard), if turned off, speeds up certain
things by 15%)
What also doesn't help is that all 2.8 million files are on one 'volume
set' wich is using NTFS compression. (A disaster waiting to happen). I
blame this on 'desktop' application designers not understanding how to
plan a system for enterprise class applications, and forcing all data to
have to live under one disk drive E:... which must be able to expand as
more data is added to the system. I have some work to do so I wont have
to sit and babysit the full restore (for a week) when one of the disks
fail this year....
Total number of objects inspected: 2,818,870
Total number of objects backed up: 905
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects failed: 2
Total number of bytes transferred: 983.01
MB
Data transfer time: 122.61 sec
Network data transfer rate: 8,209.30 KB/sec
Aggregate data transfer rate: 48.31 KB/sec
Objects compressed by: 67%
Elapsed processing time: 05:47:15
"Wu, Jialin" wrote:
>
> I have an ADSM performance question. It takes more than 11 hours for ADSM
> to backup one of our big NT file/printer server. There are about 4 millions
> objects on this server. One filespace has 60 GB data and it takes 2 hours to
> backup. The another filespace has 125 GB data and it takes 9 hours to
> backup. Everyday normally only 2-3 GB data are transferred and backed up.
> Look like the most of time are spent on file comparing. I'd like to know if
> it is normal for ADSM backup. I also have a local DLT tape drive running
> incremental backup using BackupExec. It only takes 3 hours. The following
> is a summary of performance data. ADSM server version is 3.1.2.40 and
> client is 3.1.0.7.
>
> Date/Time Message
> --------------------
> ----------------------------------------------------------
>
> 01/28/2000 06:51:07 ANE4952I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects inspected: 3,992,440
> 01/28/2000 06:51:07 ANE4954I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects backed up: 4,220
> 01/28/2000 06:51:07 ANE4958I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects updated: 159
> 01/28/2000 06:51:07 ANE4960I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects rebound: 0
> 01/28/2000 06:51:07 ANE4957I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects deleted: 467
> 01/28/2000 06:51:07 ANE4959I (Session: 4258, Node: CRRY0F03) Total
> number of
> objects failed: 59
> 01/28/2000 06:51:07 ANE4961I (Session: 4258, Node: CRRY0F03) Total
> number of
> bytes transferred: 1.24 GB
> 01/28/2000 06:51:07 ANE4963I (Session: 4258, Node: CRRY0F03) Data
> transfer
> time: 74.78 sec
> 01/28/2000 06:51:07 ANE4966I (Session: 4258, Node: CRRY0F03) Network
> data
> transfer rate: 17,432.23 KB/sec
> 01/28/2000 06:51:07 ANE4967I (Session: 4258, Node: CRRY0F03) Aggregate
> data
> transfer rate: 33.38 KB/sec
> 01/28/2000 06:51:07 ANE4968I (Session: 4258, Node: CRRY0F03) Objects
> compressed by: 0%
> 01/28/2000 06:51:07 ANE4964I (Session: 4258, Node: CRRY0F03) Elapsed
> processing time: 10:50:52
> 01/28/2000 06:51:07 ANR0403I Session 4258 ended for node CRRY0F03
> (WinNT).
>
> Thanks!
>
> Jialin Wu
--
matthew.glanville AT kodak DOT com
matthew.glanville AT kodak DOT com
(716) 477-9371
|
