To allow duplicate client names, log into the utility node as the admin user, open up /usr/local/avamar/var/server_data/prefs/mcserver.xml in an editor (e.g. vi) and change the line shown above from value="false" to value="true". Once you've saved the changes and closed the editor, you will have to restart the MCS using:
dpnctl stop mcs
dpnctl start mcs
Note that restarting the MCS will clear the activity monitor.
There's no limitation on the Avamar side but you'll have to make sure your VM host has the resources to run both backups at the same time. It's almost certainly better to run the backups serially instead of in parallel to avoid putting the storage into contention.
ionthegeek
2 Intern
•
2K Posts
0
April 3rd, 2014 06:00
There is an mcserver.xml flag that controls whether duplicate client names are permitted:
To allow duplicate client names, log into the utility node as the admin user, open up /usr/local/avamar/var/server_data/prefs/mcserver.xml in an editor (e.g. vi) and change the line shown above from value="false" to value="true". Once you've saved the changes and closed the editor, you will have to restart the MCS using:
Note that restarting the MCS will clear the activity monitor.
ionthegeek
2 Intern
•
2K Posts
0
April 3rd, 2014 06:00
There's no limitation on the Avamar side but you'll have to make sure your VM host has the resources to run both backups at the same time. It's almost certainly better to run the backups serially instead of in parallel to avoid putting the storage into contention.
bmurrey-network
48 Posts
0
April 3rd, 2014 06:00
Thank you Ian. Do we need to be mindful that both backups don't happen during the same time or are simultaneous backups supported?