Unsolved

1085

June 18th, 2022 12:00

Veeam v11 backup of Isilon Shares

Hello,

I am attempting to backup an Isilon Access Zone via native integration with Veeam 11.

The Isilon cluster has been added to the Veeam infrastructure successfully and I can create a backup job and select the Access Zone.

The job starts successfully and begins to backup the shares in the Access Zone.

The issue is that all of the processing is only being done by one node in the Isilon cluster (four node cluster).  This is causing the node to max out on CPU.

Is there a way to load balance the Veeam backup across the nodes?

I have created four Gateways on the Veeam infrastructure and selected these when adding the Isilon cluster to the Veeam infrastructure.  When the job runs all four Veeam Gateways are processing the job as I can see VeeamAgent processes on each Gateway server but all of the backup data is coming from one Isilon node.

Thanks,  Andrew

June 19th, 2022 13:00

Veeam has confirmed that load balancing with Isilon is not supported.

After a lot of testing, I did discover that the CPU % rises when the share files and folders are being calculated by the Veeam backup job, Once that is complete the CPU % does drop down again. Not sure if there is any way to skip this calculating process.

A job with just one share added stabilised at CPU % of 5% once the calculation was complete. I have started another job with three shares added and the CPU % is 15% once the calculation was complete.

I would like to run a job that backs up an Isilon Access Zone with approx 50 shares. My concern is that the CPU % on the Isilon node climbs in line with the number of shares in the job.

2 Intern

 • 

58 Posts

June 20th, 2022 09:00

I am interested in how you are using Veeam is this to effectively replicate to another isilon cluster? Are you able to add shares into the backup job over time? as perhaps attempting all the shares on the first try is very intensive, perhaps backup 3 shares, wait to complete, add another 2 shares to the policy > run job > repeat until all 50 are in the policy? 

1 Message

June 25th, 2022 19:00

I have exactly the same problem. You cannot use different ip addresses to setup different filers under Veeam, it recognises, that they are part of cluster, and say, that it is already setup.

June 29th, 2022 03:00

Veeam Support has said they realise this is an issue and load balancing is planned for v12.

June 29th, 2022 03:00

Hi storageSysAdmin

The benefit of Veeam v11 is the native Isilon integration so Veeam knows about the config of the isilon and all of the Access Zones.   This makes it so much easier to create a job as you just have to select an Access Zone to backup and Veeam picks up all of the shares and also any new shares added over time.

This is my preferred way of backing up the Isilon.   I did think about your solution but I am working with Dell and Veeam to find a remedy to this issue.

The Access Zone with 50 shares is now at 99% and has been running for 142 hours and now seems to have hung.   

Top