by foggy » Tue May 24, 2016 3:27 pm people like this post
I mean that copying the job folder from simple repository to the SOBR extent directly is not the right approach. Instead, you need to "introduce" the job to a SOBR by adding the simple repository where the job is stored to SOBR as an extent (so that SOBR could perform some naming modifications).
by electricd7 » Tue Sep 06, 2016 2:49 pm people like this post
We have a large backup job which has been writing to a normal repository. I would like to move this job our scale-out repository. Is it just as simple as find a member of the scale-out with enough space to hold it all and move it and repoint the job? We have our scale-outs set to put incrementals on any member, but in this case I would think I would have to have them all on the same member to be recognized? Any advice?
by electricd7 » Tue Sep 06, 2016 5:01 pm people like this post
OK, have added the repo to my scale-out, put it in maintenance mode, and then evacuated the data. I closed the window, so how do I now check the progress of the evacuation to know when it is safe to remove the extent from the scale-out?
by rogerdu » Fri Sep 23, 2016 3:02 pm people like this post
I've copied the latest .vbk file from my main repository (single file, not on a scale out repository) to a Scale Out repository on my remote site... When I rescan the remote site Scale Out repository, it skips 3 files... Then, when I try to map the remote copy to the full, it does not present it as a choice... I can only assume that I have not done something correctly...
by stevil » Wed Sep 28, 2016 8:27 pm people like this post
I have a similar conundrum with a new scale-out repo I created. I added three repositories into a SOBR, two of them were new, one of them already has 25TB of backup files in it. All goes well, the jobs are all reconfigured to point to the new SOBR. When I run the job it works, but all the traffic is pointed towards the original BR, the other two new ones are untouched. This is with an incremental and an active full. How do I get the active full to start populating the other repositories in the SOBR?
by dellock6 » Thu Sep 29, 2016 7:31 am people like this post
This is expected for an incremental to keep using the same extent as long as it has enough space, but an active full should recalculate the best placement. Maybe the existing storage still has the biggest amount of free space even if it's already used? Because free space is the main criteria for the selection as of now.
by stevil » Thu Sep 29, 2016 7:33 am people like this post
Thanks for the reply. It seems to be working by design now, I'm wondering if it was a permissions issue on the two new repositories. All three have the same amount of space free. I'm using 3 Different IP's on the same NAS device (DR4300) to increase throughput since the RapidCIFS driver is not compatible with veeam sadly