Take a look at /usr/local/avamar/var/cron/replicate.log on the replication source. View the file and search for the string "Info <5100>: Status" to see the amount of data being replicated.
With regards to the second question, it's not possible to set a limit to control the amount of data which the replication target will accept. It will simply backup however much you send to it from the source system.
For this reason it's preferable to have a replication target which is at least as large as the sum of the replication source systems which replicate to it.
(on AvamarA) That log seems to give me mutiple instances of data being SENT to AvamarB and I would guess that I would have to add all of these up to get the total replication data. This lists the Total data size for each server and amount NEW.
I want the amount of data INBOUND from AvamarB. Assume the amount of data from the server was constant ( ie 1TB) to get the total stored would I have to look at the first backup, then add all the of the Delta's from the inital backup?
If the systems are cross-replicating and you need to know how much data is coming from AvamarB to AvamarA then that information would be stored in the replicate.log which is located on AvamarB (which is the source system, in that instance).
The replication log is only going to give you information about data which was added during a particular replication session. If you're looking for info on how much replicated data exists on a server I believe you would need to create a custom report.
Admin Console > Tools > Manage All Reports > New and use the v_repl_activities view
The report would need to be run taking into account the retention length of the replicated data, so when you come to run the report you would configure it to pull results from the last XX days.
I ran the report, but to get my answer I will have to export it and sum of the bytes_new?
Yes, that's how I understand it works. However thinking about this a little more carefully I think it is difficult to produce accurate figures if both servers A and B are cross replicating.
There will be a certain amount of commonality between the replicated and the non replicated data.
We have support solution esg103967 but I'm not sure if it is visible globally.
Just In case it isn't I will paste it here. You will need to run it on the replication target machine.
In order to identify the clients which are contributing the most amount of data change on the Avamar system we use the script 'capacity.sh'.
The script can help us analyze the amount of data added and removed from the system on a daily basis and to understand which clients cause the greatest amount of data change on the system in order to tune retention periods.
To run the script:- =================== a) Login to the utility node as the admin user b) run /usr/local/avamar/bin/capacity.sh
NOTE: In older versions of Avamar, this script is not present on the systme and needs to be manually copied to it. See below for details.
1) Upload capacity.sh to the Avamar utility node using SCP on a Linux command line or with WinSCP on Windows.
2) Place the script in the /home/admin directory.
3) Log in to the Avamar system as the 'admin' user.
4) Change to the directory where you uploaded the script.
5) Copy the script to the /home/admin directory: cp sched.sh /home/admin/ 4) Change the permissions to allow the script to be executed:
chmod 744 /home/admin/capacity.sh 5) Run the script: ./capacity.sh
Understanding the output from the script:
The top part of the script output shows the date, the amount of new data added, the number of backups taken, the amount of data removed by garbage collection and the net change rate on the system (data added minus data removed). This section gives you an idea of what is happening on a day by day basis. You can use this to understand, at a glance, on which days experienced large increases in backup data and how data has been removed in the garbage collection sessions.
It will be very clear if there were an unusual amount (or lack of) backup data or if garbage collection failed to run on a particular day.
The bottom part of the script shows which clients added the most data in the last day. Below we see that 7923mb was added to the system in the last day. We are given a breakdown of this amount by the three clients which most contributed to this new data.
In this case, if we needed to reduce retention periods to lower the amount of data stored on the system we would concentrate on these clients.
Top Three High Change Clients: -------------------------- Total for all clients 7923 mb 100.0% aaaaa.xxxx.emc.com 2381 mb 30.1% bbbbb.xxxx.emc.com 1990 mb 25.1% ccccc.xxxx.emc.com 1282 mb 16.2%
Further information: 1) View the output with courier font for best results. 2) Run ./capacity.sh --help for further options. 3) mb as noted in the script should actually be taken to be'Mb'
Let me pose the quesiton a different way. I have a fixed amount of disk space. I see it being consumed (this is about as informative as the web console provides) and I suspect that data being replicated from AvamarB is a major consumer.
Is there a way to determine what is consuming the disk space? By answering this question, I can then make a decision if I need more nodes or if I need to call the AvamarB admin and request he replicate less data.
Although you can't see the MB/GB consumed you should be able to see the Capacity and % comsumed the EM (enterprise manager) to determine your capacity used and approx time to order a new unit.
Avamar Exorcist
462 Posts
0
August 17th, 2009 07:00
With regards to the second question, it's not possible to set a limit to control the amount of data which the replication target will accept. It will simply backup however much you send to it from the source system.
For this reason it's preferable to have a replication target which is at least as large as the sum of the replication source systems which replicate to it.
cwilson62946
12 Posts
0
August 17th, 2009 08:00
cwilson62946
12 Posts
0
August 17th, 2009 08:00
I want the amount of data INBOUND from AvamarB. Assume the amount of data from the server was constant ( ie 1TB) to get the total stored would I have to look at the first backup, then add all the of the Delta's from the inital backup?
Avamar Exorcist
462 Posts
0
August 17th, 2009 08:00
The replication log is only going to give you information about data which was added during a particular replication session. If you're looking for info on how much replicated data exists on a server I believe you would need to create a custom report.
Admin Console > Tools > Manage All Reports > New and use the v_repl_activities view
The report would need to be run taking into account the retention length of the replicated data, so when you come to run the report you would configure it to pull results from the last XX days.
cwilson62946
12 Posts
0
August 17th, 2009 08:00
I will try to create the report, but I am guessing that I would also need to run this on AvamarB?
Avamar Exorcist
462 Posts
0
August 18th, 2009 06:00
export it and sum of the bytes_new?
Yes, that's how I understand it works. However thinking about this a little more carefully I think it is difficult to produce accurate figures if both servers A and B are cross replicating.
There will be a certain amount of commonality between the replicated and the non replicated data.
Avamar Exorcist
462 Posts
0
August 18th, 2009 07:00
We have support solution esg103967 but I'm not sure if it is visible globally.
Just In case it isn't I will paste it here. You will need to run it on the replication target machine.
In order to identify the clients which are contributing the most amount of data change on the Avamar system we use the script 'capacity.sh'.
The script can help us analyze the amount of data added and removed from the system on a daily basis and to understand which clients cause the greatest amount of data change on the system in order to tune retention periods.
To run the script:-
===================
a) Login to the utility node as the admin user
b) run /usr/local/avamar/bin/capacity.sh
NOTE: In older versions of Avamar, this script is not present on the systme and needs to be manually copied to it. See below for details.
If the script is not present in /usr/local/avamar/bin then download it using the following link
ftp://avamar_ftp:anonymous@ftp.avamar.com/software/scripts/capacity.sh
To install and execute the script:
1) Upload capacity.sh to the Avamar utility node using SCP on a Linux command line or with WinSCP on Windows.
2) Place the script in the /home/admin directory.
3) Log in to the Avamar system as the 'admin' user.
4) Change to the directory where you uploaded the script.
5) Copy the script to the /home/admin directory: cp sched.sh /home/admin/
4) Change the permissions to allow the script to be executed:
chmod 744 /home/admin/capacity.sh
5) Run the script: ./capacity.sh
Understanding the output from the script:
The top part of the script output shows the date, the amount of new data added, the number of backups taken, the amount of data removed by garbage collection and the net change rate on the system (data added minus data removed).
This section gives you an idea of what is happening on a day by day basis. You can use this to understand, at a glance, on which days experienced large increases in backup data and how data has been removed in the garbage collection sessions.
It will be very clear if there were an unusual amount (or lack of) backup data or if garbage collection failed to run on a particular day.
Date New Data #BU Removed #GC Net Change
---------- ---------- ----- ---------- ----- ----------
2009-03-04 383236 mb 464 -33167 mb 1 350069 mb
2009-03-05 505260 mb 649 -56577 mb 1 448682 mb
2009-03-06 82157 mb 228 -197873 mb 2 -115715 mb
2009-03-07 499756 mb 434 0 mb 499756 mb
2009-03-08 243758 mb 328 -98435 mb 1 145322 mb
2009-03-09 126805 mb 437 -86354 mb 1 40451 mb
2009-03-10 233511 mb 435 -86748 mb 1 146762 mb
2009-03-11 152480 mb 140 -83876 mb 1 68603 mb
---------- ---------- ----- ---------- ----- ----------
Average 197349 mb -62578 mb 134770 mb
The bottom part of the script shows which clients added the most data in the last day.
Below we see that 7923mb was added to the system in the last day. We are given a breakdown of this amount by the three clients which most contributed to this new data.
In this case, if we needed to reduce retention periods to lower the amount of data stored on the system we would concentrate on these clients.
Top Three High Change Clients:
--------------------------
Total for all clients 7923 mb 100.0%
aaaaa.xxxx.emc.com 2381 mb 30.1%
bbbbb.xxxx.emc.com 1990 mb 25.1%
ccccc.xxxx.emc.com 1282 mb 16.2%
Further information:
1) View the output with courier font for best results.
2) Run ./capacity.sh --help for further options.
3) mb as noted in the script should actually be taken to be'Mb'
cwilson62946
12 Posts
0
August 18th, 2009 07:00
Is there a way to determine what is consuming the disk space? By answering this question, I can then make a decision if I need more nodes or if I need to call the AvamarB admin and request he replicate less data.
gbrown11
21 Posts
0
August 18th, 2009 12:00