Maintain control of your Microsoft 365 data
Post Reply
mdglazerman
Novice
Posts: 6
Liked: 1 time
Joined: Sep 30, 2019 12:50 pm
Full Name: Mark Glazerman
Contact:

Help using Veeam Gitlab code

Post by mdglazerman »

Good morning,

We are trying to make use of the following gitlab code to create sharepoint and teams jobs in our azure hosted VBM365 environment …

https://github.com/VeeamHub/powershell/ ... JobManager

We are using the following syntax to run the script…

./vb365-JobManager.ps1 -Organization "my-org.onmicrosoft.com" -Repository Proxy1-Repo1,Proxy1-Repo2,Proxy2-Repo1,Proxy2-Repo2 -objectsPerJob 200

I have the syntax worked out to run correctly and it starts creating new jobs which are visible in our console. Our issue is keeping the session alive on our VBO server long enough for the script to finish. If the rdp session is interrupted it kills the script.

Does anyone have a step by step process to execute this script in the background ? I’m not very powershell savvy but have a real time crunch to get this all setup. For context between teams objects and sharepoint sites we have about 44k objects that need to be parsed by the script. I suspect the script will need to run for ~24 hours to fully complete.

Thanks in advance.

Mark
mdglazerman
Novice
Posts: 6
Liked: 1 time
Joined: Sep 30, 2019 12:50 pm
Full Name: Mark Glazerman
Contact:

Re: Help using Veeam Gitlab code

Post by mdglazerman » 1 person likes this post

So I was able to work this out with some assistance from Tim Smith (One of the Solutions Architects who works on the VB365 platform. below is what I had to do...

$trigger = new-JobTrigger -once -at 11:00am

Register-ScheduledJob SPsites {c:\scripts\job-manager.ps1 -organization M365x08207376.onmicrosoft.com -Repository Repo -objectsPerJob 10} -trigger $trigger

(SPsites is just a name for the job) Then you can run Get-ScheduledJob to verify (as well as see it on Task-Scheduler under Microsoft > Windows > PowerShell > SheduledJobs)

And then you can run Get-Job to view it’s status.

This does work even if the RDP session or user who initiated the command gets logged off the machine.
Post Reply

Who is online

Users browsing this forum: No registered users and 9 guests