-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 06, 2019 11:54 am
- Contact:
Manual backup copy
Good morning all,
having two separate vSphere\Veeam environments (not connected in any way), each one with its vCenter and its Veeam server, is there a way to manually execute some backup copies between them (let's say from Env1 to Env2, Env2 to Env1 it's not requested) without needing to re-seed the entire backup?
A really simple solution could be:
1) copy job on Env1 that copies to a USB drive (media support will be decided later)
2) manually copy USB driver content to Env2 repository, deleting previous files
3) in case some backups are needed, Import\rescan them in Env2 Veeam
This will be really easy, but requires to copy each time the full backups to Env2
What about something like this:
1) copy job on Env1 that copies to a USB drive (media support will be decided later)
2) import\rescan them in Env2 (keeping them on USB drive)
3) copy job on Env2 from USB drive to final repository
Could it work? Will it copy entire fulls to final repository or Veeam will do some synthetic fulls?
Is there any other way to achieve this?
Thanks!
having two separate vSphere\Veeam environments (not connected in any way), each one with its vCenter and its Veeam server, is there a way to manually execute some backup copies between them (let's say from Env1 to Env2, Env2 to Env1 it's not requested) without needing to re-seed the entire backup?
A really simple solution could be:
1) copy job on Env1 that copies to a USB drive (media support will be decided later)
2) manually copy USB driver content to Env2 repository, deleting previous files
3) in case some backups are needed, Import\rescan them in Env2 Veeam
This will be really easy, but requires to copy each time the full backups to Env2
What about something like this:
1) copy job on Env1 that copies to a USB drive (media support will be decided later)
2) import\rescan them in Env2 (keeping them on USB drive)
3) copy job on Env2 from USB drive to final repository
Could it work? Will it copy entire fulls to final repository or Veeam will do some synthetic fulls?
Is there any other way to achieve this?
Thanks!
-
- Product Manager
- Posts: 20413
- Liked: 2301 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Manual backup copy
No, the second option will not work. Thanks!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 07, 2019 12:58 pm
- Full Name: Jean-christophe Lutundula Apala
- Contact:
Re: Manual backup copy
Hello , I'am currently creating a correlation rule based on veeam servers logs, and i'am looking for some samples of veeam logs that show an export of a back up file , or if you have an idea where i can find it . Kind regards
-
- Product Manager
- Posts: 14726
- Liked: 1706 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Manual backup copy
Hi and welcome to the community jean243,
Instead of relying on logs I suggest to check the existing list of Veeam Backup & Replication Events. For example, you can use 490 event and it's state as a trigger for your internal procedure. Thanks!
Instead of relying on logs I suggest to check the existing list of Veeam Backup & Replication Events. For example, you can use 490 event and it's state as a trigger for your internal procedure. Thanks!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 07, 2019 12:58 pm
- Full Name: Jean-christophe Lutundula Apala
- Contact:
Re: Manual backup copy
Ok awesome , thank you for help have a great day
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jan 06, 2019 11:54 am
- Contact:
-
- Product Manager
- Posts: 20413
- Liked: 2301 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Manual backup copy
At first glance the first option seems to be the only way available. Thanks!
Who is online
Users browsing this forum: Bing [Bot] and 43 guests