+1I’m moving an artesca S3 bucket to another veeam host. The repo is part of a SOBR with a storeonce primary target. Rescan option cant be done directly on the repo but can on the SOBR…..however it seems to fail.
I’m concerned when moving to the new server, we wont see old backups. Thoughts??
Best answer by MavMikeVBR
the import has worked which is great and we can see the backups under “object storage (imported)”
on to the next challenge…...I just wished veeam could do, right click job, export job to excel….oh well, traditional copy and paste will do haha
+11Hi
please explain better what is your task list for migration.
If you’re trying to add the bucket on a new server without Veeam database migration surely you can see your backup files.
+1I have a customer with 2 veeam servers, we are migrating to single veeam server. Artesca bucket config which is capacity tier in a SOBR with storeonce. This config and backups need to move to the other veeam server.
Config is fine to migrate, its the history I’m concerned about
+11OK… you’re not moving all configurations from server 1 to server 2 as this part of documentation https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120 …. right?
+1OK… you’re not moving all configurations from server 1 to server 2 as this part of documentation https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120 …. right?
yes we are moving config from veeam server 2, to veeam server 1 however we also need to retain config on server1 so its a merge of server2 into server1….. I dont think a configuration migration is workable
+1I’ve actually added the artesca bucket to the other Veeam server and the last step is to tick “import backups” I tick that, it all works but I dont see any backups imported. The repo shows 0TB used when it should be approx 15TB.
I should also see “object storage (imported)” under backup but I dont.
I’m concerned this import isnt working so may delay the migration and speak to veeam support.
thoughts??
+20Hi
Agree with your assessment in that you should be seeing the ‘Object storage (imported)’ section under Backups. Unless Michael has other suggestions, yes...I think your best bet is to open a Support case.
Please keep us posted on the resolution.
Best.
+21I’ve actually added the artesca bucket to the other Veeam server and the last step is to tick “import backups” I tick that, it all works but I dont see any backups imported. The repo shows 0TB used when it should be approx 15TB.
I should also see “object storage (imported)” under backup but I dont.
I’m concerned this import isnt working so may delay the migration and speak to veeam support.
thoughts??
If the other server is active it will "own" the bucket. This is why the configuration backup and migration is the option to move servers. Then it will allow the new server to take ownership of the bucket. You can also try to rescan the repo now that you have added it to see if that fixes it.
+1I’ve actually added the artesca bucket to the other Veeam server and the last step is to tick “import backups” I tick that, it all works but I dont see any backups imported. The repo shows 0TB used when it should be approx 15TB.
I should also see “object storage (imported)” under backup but I dont.
I’m concerned this import isnt working so may delay the migration and speak to veeam support.
thoughts??
If the other server is active it will "own" the bucket. This is why the configuration backup and migration is the option to move servers. Then it will allow the new server to take ownership of the bucket. You can also try to rescan the repo now that you have added it to see if that fixes it.
thanks Chris, so based on the ownership, you would expect this?
With this customer, both veeam servers are in use so we cant do a config backup and migration as we need to merge both servers into the one single server.
If we delete the veeam repo on the server we want to decom, will the new one take ownership once we do a rescan?
tbh if its a concern we could keep veeam server 2 running until that bucket’s data has expired.
+1we are doing an “import backups” now and seems to be importing. We now have a “capacity tier (imported)” record appear and it says import 1 of 12 backups…..so lets see how that progresses
+20we are doing an “import backups” now and seems to be importing. We now have a “capacity tier (imported)” record appear and it says import 1 of 12 backups…..so lets see how that progresses
Looks promising!… 😊
+21we are doing an “import backups” now and seems to be importing. We now have a “capacity tier (imported)” record appear and it says import 1 of 12 backups…..so lets see how that progresses
That is a good sign. Yeah after adding doing another import/rescan should bring things over. Hopefully this is the solution to the issue and it resolves the problem. Keep us posted.
+1we are doing an “import backups” now and seems to be importing. We now have a “capacity tier (imported)” record appear and it says import 1 of 12 backups…..so lets see how that progresses
That is a good sign. Yeah after adding doing another import/rescan should bring things over. Hopefully this is the solution to the issue and it resolves the problem. Keep us posted.
thanks Chris, will do….It would seem at the moment that when creating the S3 repo, the options to import backups etc doesnt actually work…..however, doing a separate “import backups” seems to be working…..The import is 6 thru 12 so its progressing.
will keep you guys posted.
+1the import has worked which is great and we can see the backups under “object storage (imported)”
on to the next challenge…...I just wished veeam could do, right click job, export job to excel….oh well, traditional copy and paste will do haha
+21the import has worked which is great and we can see the backups under “object storage (imported)”
on to the next challenge…...I just wished veeam could do, right click job, export job to excel….oh well, traditional copy and paste will do haha
Great to hear the import worked. 👍🏼
+20Awesome! Glad you’re up and going
+1we seem to have hit an issue.
Whilst the v12.1 veeam server can see the S3 repo and backups have imported, the other v11 Veeam server has shown up backup failures.
The v11 backups to the S3 repo fail with “data in object storage is encrypted but wrong password was provided”,
not sure if there is an incompatibility issue across the veeam instances. Could well be. Also found this thread….
any thoughts?? I may get the 2nd Veeam server upgraded to v12.1 so at least we are on the same version.
+21Did you check the Encryption password to ensure it was correct for the backups? Only thing I can think of right now but definitely upgrade v11 to v12 and then see. It does get a bit dicey when having 2 VBR servers accessing the same S3.
+1Did you check the Encryption password to ensure it was correct for the backups? Only thing I can think of right now but definitely upgrade v11 to v12 and then see. It does get a bit dicey when having 2 VBR servers accessing the same S3.
we did replicate the config which included all passwords as well. I think the best way forward is to make sure both VBR instances are on the same version…..
Unfortunately I cant move the cover over yet as one of the proxys has a network issue which the customer needs to resolve.
+21Did you check the Encryption password to ensure it was correct for the backups? Only thing I can think of right now but definitely upgrade v11 to v12 and then see. It does get a bit dicey when having 2 VBR servers accessing the same S3.
we did replicate the config which included all passwords as well. I think the best way forward is to make sure both VBR instances are on the same version…..
Unfortunately I cant move the cover over yet as one of the proxys has a network issue which the customer needs to resolve.
Yeah, see what happens when you upgrade the v11 to v12 and take it from there. If the config moved over, it should have the correct password.
+11Did you check the Encryption password to ensure it was correct for the backups? Only thing I can think of right now but definitely upgrade v11 to v12 and then see. It does get a bit dicey when having 2 VBR servers accessing the same S3.
we did replicate the config which included all passwords as well. I think the best way forward is to make sure both VBR instances are on the same version…..
Unfortunately I cant move the cover over yet as one of the proxys has a network issue which the customer needs to resolve.
I had same issue last year. When Veeam V12 scan S3 repo it have the ownership on it. Metadata on different servers version not corresponding so... Yes you must update other VBR server
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
