-
- Expert
- Posts: 160
- Liked: 16 times
- Joined: Nov 19, 2014 4:20 am
- Contact:
Migrating SOBR extents
Hi,
We are replacing our storage systems which we used for our Scale-Out Backup Repository. We are going to use the "Evacuate Backups" feature to migrate the SOBR extents to the new storage systems.
My questions are:
1. Should I disable the backup jobs for the duration of the migration?
2. Does the backup jobs really need to be disabled?
Our SOBR is about 64TB. It will take very long time for the migration to be completed. If the jobs will be disabled, then we will not have a backup for few days or maybe a week?
Thanks,
We are replacing our storage systems which we used for our Scale-Out Backup Repository. We are going to use the "Evacuate Backups" feature to migrate the SOBR extents to the new storage systems.
My questions are:
1. Should I disable the backup jobs for the duration of the migration?
2. Does the backup jobs really need to be disabled?
Our SOBR is about 64TB. It will take very long time for the migration to be completed. If the jobs will be disabled, then we will not have a backup for few days or maybe a week?
Thanks,
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Migrating SOBR extents
Take a look at the Seal Mode - allows to gradually migrate to a new extent.
-
- Veeam Software
- Posts: 688
- Liked: 150 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: Migrating SOBR extents
Hi,
as written in the documentation (https://helpcenter.veeam.com/docs/backu ... ml?ver=110) it is highly recommended to stop and disable the jobs during the migration.
Also the extend needs to be in placed into maintenance mode. This is mandatory to evacuate backups.
Also keep in mind that evacuating backup files from an extent formatted with ReFS will hydrate synthetic full backups created by Fast Clone.
Thanks
as written in the documentation (https://helpcenter.veeam.com/docs/backu ... ml?ver=110) it is highly recommended to stop and disable the jobs during the migration.
Also the extend needs to be in placed into maintenance mode. This is mandatory to evacuate backups.
Also keep in mind that evacuating backup files from an extent formatted with ReFS will hydrate synthetic full backups created by Fast Clone.
Thanks
Stefan Renner
Veeam PMA
Veeam PMA
-
- Expert
- Posts: 160
- Liked: 16 times
- Joined: Nov 19, 2014 4:20 am
- Contact:
Re: Migrating SOBR extents
Wow, that is my worry really. Disabling a jobs will put us in a situation where we don't have a backup maybe for a week. It will take 64TB maybe one week to be completed.
Thanks,
Thanks,
-
- Veeam Software
- Posts: 688
- Liked: 150 times
- Joined: Jan 22, 2015 2:39 pm
- Full Name: Stefan Renner
- Location: Germany
- Contact:
Re: Migrating SOBR extents
the question in my eyes is always, how much of a retention is on that 64TB?
Maybe it is easier to start a new chain on the new extend while keeping the old extend for restores.
With that you would not need to migrate and also no need to disable anything.
As foggy wrote you may want to check the seal mode here.
Maybe it is easier to start a new chain on the new extend while keeping the old extend for restores.
With that you would not need to migrate and also no need to disable anything.
As foggy wrote you may want to check the seal mode here.
Stefan Renner
Veeam PMA
Veeam PMA
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Jun 15, 2022 3:22 pm
- Full Name: Mario Orefice
- Contact:
Re: Migrating SOBR extents
Hi all,
I am in the same situation in which I would like to use the SOBR evacuate feature in order migrate from one repository to another.
The point is that I want to do it without disabling daily backup jobs and without running new active fulls, so seal mode is not an option.
Would this procedure works as per your experience:
1 - Add old and new repositories into a new scale-out repository
2 - During the day while backups are not running, start the evacuate backups job
3 - Stop the evacuate job in the evening, before the daily incremental schedule starts (will the incremental job run smoothly even if some restore points of the chain are moved to the new extent?)
4 - Repeat steps 2 and 3 everyday until the old extent is empty
Thank you
I am in the same situation in which I would like to use the SOBR evacuate feature in order migrate from one repository to another.
The point is that I want to do it without disabling daily backup jobs and without running new active fulls, so seal mode is not an option.
Would this procedure works as per your experience:
1 - Add old and new repositories into a new scale-out repository
2 - During the day while backups are not running, start the evacuate backups job
3 - Stop the evacuate job in the evening, before the daily incremental schedule starts (will the incremental job run smoothly even if some restore points of the chain are moved to the new extent?)
4 - Repeat steps 2 and 3 everyday until the old extent is empty
Thank you
Who is online
Users browsing this forum: No registered users and 73 guests