Unsolved
This post is more than 5 years old
8 Posts
0
1843
March 25th, 2010 05:00
How Centera replicates delete and other questions
Hello,
last time I asked about compliancy, and they (data owners) are now investigating if we really need it. In the mean time, we are faced with bandwidth problem. We replicate 4 pools and now there is 114,340,752 MB to be replicated, at least this is what I get in Centera Viewer. Is this really the amount of data that has to be transferred to another side, or this should be interpreted in some other way?
This is output of 'show replication detail' command:
Number of Blob Writes to be replicated: 4,583,725
Number of MB to be replicated: 114,340,752
Number of C-Clip Deletes to be replicated: 64,811
Number of C-Clip Event and Hold Updates to be replicated: 0
Number of Parked Entries: 4
Replication Speed: 0.00 C-Clip/s
Replication Speed: 1,876.53 Kb/s
Replication ETA: N/A
Replication Lag: N/A
Pool Name C-Clips to be replicated Ingest in C-Clip/s
--------------------------------------------------------------------------
Arhiva 170 0.00 C-Clip/s
MASVZpool 2,354 0.00 C-Clip/s
TSMpool 45,284 0.00 C-Clip/s
--------------------------------------------------------------------------
Total 47,809 0.00 C-Clip/s
Are deletes included in this total amount of MB and how? Is there a way od knowing how much MB comes from each pool?
What would happen if we stopped replication of one pool, in order to temporarily releave some BW for other pools? Would data that is already in the queue for replication have to be transfered anyway?
I am trying to find a way to replicate at least data from some (more important) pools, and give us some time to negotiate more BW or something else.
Any suggestion would be appreciated.