Node Replication - Windows Clients - Poor Performance

booman55

ADSM.ORG Senior Member
Joined
Feb 21, 2007
Messages
259
Reaction score
11
Points
0
PREDATAR Control23

I'm trying to get my head around why my Windows Node Replication groups are running waaaayyy longer than my AIX\Linux groups even though the data being replicated isn't larger. What I've determined is the number of Files Updated is alot larger than the Unix groups. Files Updated is related to metadata. So does this mean there are a lot of ACL updates going on within the backups?

Anyone else have similar issue replication Windows clients? Any solutions to suppress this?
 
PREDATAR Control23

The ACL is part of the file metadata, not part of the metadata TSM keeps for each file. The info TSM keeps for files is the same on all platforms, but if the number of files to replicate is larger, this means that there is a lot more database updates to do during the replication.

So I'd look at your database performance:
- number of directories/LUNs
- speed of disks

Here would be a good start:
http://www-01.ibm.com/support/knowl...com.ibm.itsm.perf.doc/r_chklist_srvdbdsk.html
http://www-01.ibm.com/support/knowl....ibm.itsm.perf.doc/c_noderep_optimconfig.html
 
PREDATAR Control23

Here's output of 2 groups from same source to same target.
Windows:
. Files current: 3,164,286. Files replicated: 7,912 of 8,153. Files updated: 649,832 of 649,837. Files deleted: 9,524 of 9,524. Amount replicated: 9,557 MB of 9,961 MB. Amount transferred: 9,557 MB. Elapsed time: 0 Day(s), 5 Hour(s), 49 Minute(s).

Unix:
Files current: 23,978,948. Files replicated: 107,509 of 107,509. Files updated: 220,765 of 220,765. Files deleted: 45,790 of 45,790. Amount replicated: 141 GB of 141 GB. Amount transferred: 141 GB. Elapsed time: 0 Day(s), 0 Hour(s), 57 Minute(s).
 
PREDATAR Control23

The response I got back from IBM Support was that it was related to Windows System State, which is what I originally suspected. Still trying to work through whether this is normal activity or how I can suppress this outside of disabling replication for System State file spaces.
 
Top