VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Thanks @MicoolPaul for your answer.Yes in my comprehension, Veeam needs to have an account with global admin role to create the app with all the appropriate rights.In the case where the application is created manually it's seem that is not a requirement but I m not sure.But in any case an account needs admin rights, to restore with the explorers.(Exchange,Sharepoint,Teams administrator roles)Unfortunatelly I dont have an M365 account to test this on my lab :(
Do both proxies have the same transport mode configured and the same number of task slots? Yes the both proxy are in hotadd but not the same number of task slots. Also remember that Direct SAN won’t work remotely. So if your proxies are Direct SAN, and 1 stops working, it will fail over to Hot-Add locally as a second choice. I find many people have their Veeam BR Server as a standby proxy which gets used in this situation. It’s often not a terrible idea to create a few VM’s in your virtual infrastructure as Veeam Proxies I find on the rare occurrence they are needed. Personally though, I’m in the Direct SAN for life crew because it works so well. Direct San is a good option but sometime the infrastructure is not compatible or if you have vm in thin provisioning, the proxy will not be used so it’s necessary to create a vm to have a hotadd proxy.
Nice point here, physical security is the first thing to enforce, before cybersecurity and so on! Looking forward for the post series, just for you to know, I have seen many places with awesome hardware, tools for security, etc… in a unlocked server room, open racks, accessible ports, etc. I was thinking the same and saw your comment. So many company invest in security tools but forget the basics in terms of physical security like close the door of the it room….
Enjoy your trip !
Hello,I'll probably wait a bit before migrate my existing clients to Postgres, except for the ones who arrive to SQL Express limits.For new installation I will probably install Veeam with Postgre except if my client have some needs for specific dev.On the VSPC side, I ll stay in SQL Standard cause Postgre is not supported as Veeam One.In the security view I don’t know if Postgre is more secure than MS SQL or if we need to apply some hardening too.
HelloIs it possible that your host HOST02 is managed by another Veeam Server?
Hello,Yes concurrents task are limited by CPU/RAM.You have to take in consideration the limitations on the proxy side and repository sideTask Limitation for Backup Proxies:1CPU= 1 task = 1 vDiskYou could find here example how to size your proxy:https://bp.veeam.com/vbr/2_Design_Structures/D_Veeam_Components/D_backup_proxies/vmware_proxies.htmlTask Limitation for Backup Repositories:That depends how you set the configuration of your repo, in "Per-VM mode" 1 task = 1 VDiskYou could find here example how to size your repo:https://bp.veeam.com/vbr/2_Design_Structures/D_Veeam_Components/D_backup_repositories/For Data Domain you need to deploy a Gateway Server, I never installed this kind of appliance, but you have to follow the best practices guides to set the good configuration. Especially to have the good block size, the number of parallels task etc...
GA Jan 12th
Congrats!In my company, we deploy VXRail infrastructures and backup them with Veeam.Vxrail is based on vSan so I supposed you recommanded to used:Virtual Proxies One Proxie per host if necessary DRS rules to stick each proxy to its hostsIn this way, data is read locally from the node without useless network traffic consumption.
Yes I have already hit the SQL Express limit, cause the infrastructure grew up in the times and the Veeam is used for backup, replication, backup copy, tape...In v12 this limitation could be change with Postgre.I never installed a Veeam on a SQL cluster, for me this case apply for the MSPs.
I’ll check in my lab tomorrow 😊 Hello @MicoolPaul hope you are fine :)did you have time to test in your lab?
I already dit it during a break… not the best timing my score: 39574
Yes I have already hit the SQL Express limit, cause the infrastructure grew up in the times and the Veeam is used for backup, replication, backup copy, tape... In v12 this limitation could be change with Postgre. I never installed a Veeam on a SQL cluster, for me this case apply for the MSPs. Impressive. You win! I have Backup, Replication, Backup copy, PB’s of Tape, index's, object storage, multiple repository's, multiple proxies. How many VM’s were you backing up as a ballpark. Hmm not so much around 200-300 VMs
@Stabz This is a great feature but sending on-premesis backups to object storage have me a little concerned. One issue I am afraid that will crop up is bandwidth issues. Users will need to make sure they have enough bandwidth and object inject speed to handle their backup traffic in their stated backup window. The second issue I worry about is that hope will think since they have a backup in the cloud they won’t need a second copy somewhere else. I think that will be a big mistake. Personally I am going to discuss this as a great on-premesis solution to provide immutability with the hassle of learning Linux - and may well be easier to maintain for some shops. Then do a backup copy job to an off-site location. Hello @vmJoe ! I agree, I don't recommend to backup directly to cloud object storage for sure, we need a backup near the production to have the best performances in case of restore. But in case you have an object storage appliance onpremise this will simplify a
Backup copy to another bucket in other region ? :D
I’m currently using an Exagrid appliance as my backup repository. Can the “Direct Backup to Object Storage” be configured to auto-start as soon as the corresponding backup job completes? I’m going to use AWS Glacier Deep Archive.
Soon the mini serie Veeam Community Recap around the world ! Nice one again :D
Woow amazing recap thanks @MicoolPaul
Hello,Seems to have some problem to apply the retention policy. Do you have the right permissions for the service account? https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_deploy.html?ver=110#step1
Hello, Seems to have some problem to apply the retention policy. Do you have the right permissions for the service account? https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_deploy.html?ver=110#step1 Hi Stabz, I’ve read something about the retention policy on the log error, I also thought of something due to retention of hardened repository that cannot delete file because locked, but it worked fine still last friday and why the repository become Unavailable? Hi @fspadaro , the issue could came from a lot of things. I would recommend to check the server first if you have any hardware issue, after that you could check the Veeam Services. In any case if the problem persist you should open a ticket to the Veeam Support https://www.veeam.com/fr/support.html.
Hello, I never try this. I know it’s possible to backup a replica create with Veeam with some recommendations.CBT cannot be utilized when backing up replica VMs Make sure replication jobs do not overlay with your backup ones. Otherwise, multiple issues will be expected
Hello @mcz ,Normally you should have the option in standalone mode. Maybe it’s not set in the beta. I ll try to take a look
Have you installed the provided BETA license in the agent? Only Workstation and Server editions will be able to use direct to object storage. the Free agent edition cannot use direct backups to object storage. Thanks Fabian @Mildur beat me to it!
I enabled it only if I have multiple Performance tiers with enough space to receive full backup of another one.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
