Basic description of feature request: ability to open a standalone VBK (one that is NOT part of an existing backup job), and extract one or more VM's and insert them directly into a new VBK.
I know that v7 can do an operation similar to this with a Backup Copy Job run against an existing backup job, but it would be nice to have a standalone tool that can do this with old VBK's that are not part of an existing backup job.
-
- Veeam ProPartner
- Posts: 7
- Liked: never
- Joined: Jun 19, 2013 7:59 pm
- Full Name: Greg Gillette
- Location: Anchorage, AK
- Contact:
-
- VP, Product Management
- Posts: 27055
- Liked: 2710 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: feature request:extract VM from VBK, insert into another
Hi Greg,
Can you give us a bit more information on how often do you want to use the feature and what is the general use case for that, so we could have a better understanding of what is required?
Thanks!
Can you give us a bit more information on how often do you want to use the feature and what is the general use case for that, so we could have a better understanding of what is required?
Thanks!
-
- Product Manager
- Posts: 20270
- Liked: 2252 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: feature request:extract VM from VBK, insert into another
Hi, Greg.
I assume the problem with backup copy job is that it doesn’t allow to use “imported” data as a source for it, right? If so, you can, probably, create a “dummy” backup job, map it to the previous backup data (old .vbk) and use it later as a source for a backup copy job.
Thanks.
I assume the problem with backup copy job is that it doesn’t allow to use “imported” data as a source for it, right? If so, you can, probably, create a “dummy” backup job, map it to the previous backup data (old .vbk) and use it later as a source for a backup copy job.
Thanks.
Who is online
Users browsing this forum: Semrush [Bot] and 207 guests