tsightler wrote: but the primary benefit is from simply having mulitple merges occurring in parallel. In v8 the merge is a 100% serial process, each file from each point is merged in sequence so if you have 160VMs in a job, you will find that there will be ~1 minute of overhead per VM, which is almost 3 hours just working on metadata.
jbarrow.viracoribt wrote:For instance, one of the jobs will gobble up all the proxy slots and the next 3 jobs will sit around waiting until the first job frees up slots.
jbarrow.viracoribt wrote:The second issue to running multiple jobs at a time is that I seem to only be able to have one storage snapshot in place at a time. If job 1 creates a storage snapshot, job 2 (if running at the same time) gets an error it can't create one.
jbarrow.viracoribt wrote:Sidebar: I'm hearing good things about the C3160 box as a repository. Does it number crunch pretty well even with 7.2k RPM drives (which it seems to come with)?
jbarrow.viracoribt wrote:9/22/2015 2:39:17 PM :: Creating storage snapshot
9/22/2015 2:39:18 PM :: Failed to create snapshot for LUN na_ls_lun_101 Details: Clone operation failed to start: Device busy..
jbarrow.viracoribt wrote:1. It makes my jobs more complex, I have to figure out what VM's fit in what jobs, then manage multiple jobs vs. 1 large job.
tsightler wrote:Do you perhaps not have a Flexclone license on that box? I'm thinking that could be the reason for this limitation. If that's the case, I can see how that could be a challenge for multiple jobs, especially if you have only a single datastore.
Users browsing this forum: Yahoo [Bot] and 1 guest