While I am sure this is quite advanced as is always the case with Comm's there is some information here on SLES which is what Avamar is based upon, however I am not sure what you need to tell Avamar to get it to work correctly with the VLAN's.
I had an open SR, but since then nothing then SR managing...
So, my issue is not SUSE/Linux. That part is managed.
The problem is to know the impact over the AVAMAR itselft...
So I need to know what to do so get the minor impact over the grid, since the grid that would get such change is a full 3,9TB node grid and has a considerable VLANs vs clients.
Making a checkpoint, stopping gsan, apply changes, starting gsan, making checkpoint can take more then the Maintenance window...
So, at this point I need to be directioned to the details or have a procedure...
Why do you have to take a checkpoint after the changes have been created ? It seem's like this would be overkill because you can always re-perform the changes if you need to roll back to the 1st check-point and than just wait until next maintenance period for new checkpoint to complete... ?
The sheduller only goes to backup window after a checkpoint is done, if we stop Avamar Server, make changes... then if we do not get a checkpoint soon only in the next begining blackout and maintenance window sequence we will have a checkpoint...
So if you make some changes during the current maintenance window the imideatly expected backup window will not run, will post poned to after next "cron" checkpoint...
I did noticed this on the procedure for Disk Transplantation that in the last step says that you can go home after start Avamar Software... is not true... you have to get a fresh checkpoint or you will get customer mad with you that the midnight backups didn't run...
Sandeep_Sinha
307 Posts
627
0
Posted January 14th, 2013 23:00
I would suggest you to contact your local EMC sales team to get help with this task.