-
- Certified Trainer
- Posts: 1025
- Liked: 448 times
- Joined: Jul 23, 2012 8:16 am
- Full Name: Preben Berg
- Contact:
Best Practices for Version 9
All,
The long awaited Best Pratices Guide has been updated for version 9.
URL: bp.veeam.expert
Any feedback is welcome - in this thread, by commenting directly in GitBook (preferred), via Twitter, through your local Veeam representative - anything goes.
Huge thanks to all the teams involved -- Solutions Architects, QA and Support.
Regards,
Preben
The long awaited Best Pratices Guide has been updated for version 9.
URL: bp.veeam.expert
Any feedback is welcome - in this thread, by commenting directly in GitBook (preferred), via Twitter, through your local Veeam representative - anything goes.
Huge thanks to all the teams involved -- Solutions Architects, QA and Support.
Regards,
Preben
-
- Enthusiast
- Posts: 96
- Liked: 24 times
- Joined: Oct 08, 2014 9:07 am
- Full Name: Jazz Oberoi
- Contact:
Re: Best Practices for Version 9
Do we have one available for Hyper-V as well ?
-
- Certified Trainer
- Posts: 1025
- Liked: 448 times
- Joined: Jul 23, 2012 8:16 am
- Full Name: Preben Berg
- Contact:
Re: Best Practices for Version 9
We are working on a chapter about Hyper-V proxies and transport modes. Everything else should more or less apply to Hyper-V as well.
Thanks for the feedback!
Thanks for the feedback!
-
- Chief Product Officer
- Posts: 31816
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Best Practices for Version 9
Please keep the feedback coming, folks!
-
- Veeam ProPartner
- Posts: 55
- Liked: 12 times
- Joined: Apr 10, 2013 12:11 pm
- Full Name: Gregor Smerke
- Location: Ljubljana, SI - Slovenia
- Contact:
Re: Best Practices for Version 9
Dear All
Regards
Gregor
As I remember from training it should not be possible or at least it is not supported to backup the Veeam backup server by itself. From this piece of information I deduced that it should also not be possible to replicate the Veeam backup server by itself since all the same gear is being used as with backup. Please, can someone explain to me where did my reasoning fail?Planning for Disaster Recovery of Veeam Backup Server
If you have the backup server in the primary site it is recommended to replicate the Veeam backup server VM to the secondary site (verify network and IP mapping settings before you begin; refer to http://helpcenter.veeam.com/backup/vsph ... a_job.html for details). If the configuration database is external, ensure this server is also replicated to the secondary site.
Regards
Gregor
-
- Certified Trainer
- Posts: 1025
- Liked: 448 times
- Joined: Jul 23, 2012 8:16 am
- Full Name: Preben Berg
- Contact:
Re: Best Practices for Version 9
Not sure what training you had, but this is definitely wrongGregorS wrote:As I remember from training it should not be possible or at least it is not supported to backup the Veeam backup server by itself.
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Best Practices for Version 9
Gregor, probably you're meaning the fact that it cannot hotadd itself in case the default proxy is used, and CBT cannot be used, but generally, backup server can be used to backup itself.
-
- Veeam ProPartner
- Posts: 55
- Liked: 12 times
- Joined: Apr 10, 2013 12:11 pm
- Full Name: Gregor Smerke
- Location: Ljubljana, SI - Slovenia
- Contact:
Re: Best Practices for Version 9
Yes, this is what I must have memorized and falsely generalized.... it cannot hotadd itself...
Do you mean only in combination with [hotadd]? Is there also a reason CBT cannot be used with [san]? Can you elaborate? Thanks!... and CBT cannot be used...
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Best Practices for Version 9
If the proxy is used to hotadd disks of other VMs, CBT cannot be used during backup of this proxy. No issues with other transport methods.
Who is online
Users browsing this forum: Majestic-12 [Bot] and 98 guests