Is it possible to create a Copy job with the first and third Saturday of the month?
Trying to have a staggered, two-device air-gapped solution.
device 1 = First/Third
Device 2 = Second/Last
Thanks in advance!
-
- Service Provider
- Posts: 41
- Liked: 4 times
- Joined: Oct 17, 2016 1:03 am
- Contact:
-
- Product Manager
- Posts: 9452
- Liked: 2513 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Scheduling with powershell
Hello Limey
A single copy job cannot use such schedule.
I recommend to use a single backup copy job (type: periodic) and set it schedule to run each Saturday.
Configure the repository as "Backup Repositories with Rotated Drives":
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
After the Saturday backup copy session, remove the drive. Connect the other drive each Friday evening for the Saturday backup copy.
Best,
Fabian
A single copy job cannot use such schedule.
I recommend to use a single backup copy job (type: periodic) and set it schedule to run each Saturday.
Configure the repository as "Backup Repositories with Rotated Drives":
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
After the Saturday backup copy session, remove the drive. Connect the other drive each Friday evening for the Saturday backup copy.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 41
- Liked: 4 times
- Joined: Oct 17, 2016 1:03 am
- Contact:
Re: Scheduling with powershell
Unfortunately, these are hardend linux Repos.
Can I do it via a periodic Copy job to run on a Saturday, then use a scheduled task w/Powershell to enable/disable it based on the schedule I'm after?
Can I do it via a periodic Copy job to run on a Saturday, then use a scheduled task w/Powershell to enable/disable it based on the schedule I'm after?
-
- Product Manager
- Posts: 9452
- Liked: 2513 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Scheduling with powershell
Hello Limey
So you plan to rotate "hardened repositories"?
Air-gapping a hardened repository is not necessary if you follow the hardening guide lines. It may also lead to errors/warnings with the background retention process, if a hardened repository is not connected. This process runs every day at 00:30.
In case you still want to disconnect hardened repositories, you can try the following:
- Add two hardened repository in the veeam console
- Add two backup copy jobs
- Use a PowerShell script to modify the schedule of the backup copy job to switch between First/Third and Second/Last Saturday.
A single hardened repository in Veeam wouldn't work. If backup files are not available, the job would bring an error.
Please also be aware, there are months with 5 Saturdays. This may be important for your script. In those months, you won't have a backup copy on the forth Saturday. September 2023 would be such month.
My recommendation is to leave the hardened repository connected. The effort seems to much, while the hardened repository already has a good solution if hardened correctly.
Just for your information, we also provide a hardening script for hardened repositories: https://www.veeam.com/sys507
Best,
Fabian
So you plan to rotate "hardened repositories"?
Air-gapping a hardened repository is not necessary if you follow the hardening guide lines. It may also lead to errors/warnings with the background retention process, if a hardened repository is not connected. This process runs every day at 00:30.
In case you still want to disconnect hardened repositories, you can try the following:
- Add two hardened repository in the veeam console
- Add two backup copy jobs
- Use a PowerShell script to modify the schedule of the backup copy job to switch between First/Third and Second/Last Saturday.
A single hardened repository in Veeam wouldn't work. If backup files are not available, the job would bring an error.
Please also be aware, there are months with 5 Saturdays. This may be important for your script. In those months, you won't have a backup copy on the forth Saturday. September 2023 would be such month.
My recommendation is to leave the hardened repository connected. The effort seems to much, while the hardened repository already has a good solution if hardened correctly.
Just for your information, we also provide a hardening script for hardened repositories: https://www.veeam.com/sys507
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 41
- Liked: 4 times
- Joined: Oct 17, 2016 1:03 am
- Contact:
Re: Scheduling with powershell
Sorry about the confusion. I plan to have two hardened repos. Each with its own Backup Copy job running periodically. I would like BCJ1 to run 1st Sat/3rd Sat, and BCJ2 to run 2nd Sat/4th Sat. These are two independent jobs with their own Hardened Repo - no rotating.
I am trying to kick off the BCJ manually, but I get an immediate fail from Powershell; yet it runs from the GUI
Here's what the event log says
Backup Copy job 'BCJ1' finished with Failed.
Job details: Job has been stopped with failures. Error: Root element is missing.
Backup completed with errors Error: Root element is missing.
This is the Powershell
Get-VBRbackupcopyJob | where {$_.Name -eq "BCJ1"} | start-vbrjob
PS D:\Toolbox> Get-VBRbackupcopyJob | where {$_.Name -eq "BCJ1"} | start-vbrjob
Job Name State Start Time End Time Result
-------- ----- ---------- -------- ------
BCJ1 Stopped 8/4/2023 5:00:59 PM 8/4/2023 5:01:15 PM Failed
I am trying to kick off the BCJ manually, but I get an immediate fail from Powershell; yet it runs from the GUI
Here's what the event log says
Backup Copy job 'BCJ1' finished with Failed.
Job details: Job has been stopped with failures. Error: Root element is missing.
Backup completed with errors Error: Root element is missing.
This is the Powershell
Get-VBRbackupcopyJob | where {$_.Name -eq "BCJ1"} | start-vbrjob
PS D:\Toolbox> Get-VBRbackupcopyJob | where {$_.Name -eq "BCJ1"} | start-vbrjob
Job Name State Start Time End Time Result
-------- ----- ---------- -------- ------
BCJ1 Stopped 8/4/2023 5:00:59 PM 8/4/2023 5:01:15 PM Failed
Who is online
Users browsing this forum: Bing [Bot] and 178 guests