Join discussions around Veeam community projects, Veeam events, industry and technology news
- 1,275 Topics
- 12,451 Comments
Dear All, we have following data protection requirement, so looking forward for your guidance for creating a Backup & retention policy. File Server - at present we have 5TB files & folders currently backing up using Veeam. The requirement is that we need a 36 months of retention period of data and the backup job should run every 1 hour. The objective is to restore any file or folder with in the period of 3 years. VM Backup with at least 2 restore points with daily incremental and weekly full. Thank you in advance
I started my first backup on the 9th. I have retention set to 12 days and Synthetic on Saturdays (default) . No files have yet been removed from my NAS. I have attached details 9kinow there are extra backups on some days) but its over 12 days now. When will deletion start ? Tony
Beeing a Veeam Architect as well as DataCore DCIE at the same time I was always pushing for this plugin.After it finally happened, I took the time to write a deep dive blogpost covering all aspects:Technical background, prerequisites BfSS jobs, howto and caveats Snapshot only jobs “Instant-Sandboxing” from storage snapshots Off-label-usage with unique functionality of DataCore: Using DataCore CDP rollbacks together with the plugin to recover without having had a snapshot in the first place… (cool stuff!)Find the article in English here:https://www.elasticsky.de/en/2020/06/veeam-storage-plugin-for-datacore-deepdive/Might come in handy if you want to combine those great products. Comments or complements welcome! Regards,Michael
Hi,we do backups from our on premise VMs and some physical servers (agentbased). Backups are going to be offloaded to S3 and Glacier useing capacity and archive tier. Anything is working fine.In case of desaster, we plan to recover the backups on aws as ec2 in a vpc. We could also use vmc on aws. But because of our host limit of 2 nodes, this will not be practicable. Is there a way of automatic recovery tests, veeam orchestrator for example, to aws? Or is there even a better option? Ideal would be a daylie updated ec2 environment. Fallback would be, do backup from ec2 and recover as vm. If this would be possible.
Hello everybody,I have to chain some jobs of backup to tape. They save backup jobs on disk to a LTO.I’d like to erase the tape on the first job. I don’t see how to do it.So I have actually a job wich save all the job to disk in a single path.Thnaks a lot for your helpOlivir GAUJAC
Hi,I’m a bit confused about the difference of old Veeam forum and new community discussion board. I just posted in old forum, but as it’s not allowed to post log file content there, I’ll give it a try here too. I'm setting up our first Linux based backup repository based on Apollo 4510 server (Veeam 10). Now the jobs have different kind of errors. Before I open a case I wanted to know if those problems are known issues with an easy workaround. This all seems to be related to load, as it happens only when multiple backups are running. But there is not much CPU load and no errors in the usual linux logs.#1 at this time backup jobs were writing active fulls with 1,5GB/s over LAN to the server, CPU was 90% idle (52 cores). Nothing interesting in /var/log messages.[15.05.2021 15:19:27] <326> Error Failed to upload file D:\Veeam\Backup\VeeamAgent64 to /tmp/VeeamAgent0bc9a8bd-ebd8-44b8-a373-44510aefd89f[15.05.2021 15:19:27] <326> Error Failed to find terminal prompt: timeout occ
I'm getting several warning is the windows logs. It seems to all be to do with the logging Cannot write into storage C:\ProgramData\Veeam\Backup\Utils\Util.VolumesHostDiscover.log Text: System.ObjectDisposedException: Cannot access a closed file I have deleted the logs and they recreate and the events are recorded but throw this warning. This is a Community edition of VBS 11
I’m currently running the 30-day trial version of Office 365 backup (18.104.22.168) and everything has been running well for the last 10 days or so. I have the software set up to run every 8 hours for a whole organization backup. Out of the blue, last night, the backups started failing with “Access denied. The remote server returned an error: (403) Forbidden”The admin password is the same and Azure AD shows the login for the Veeam account as successful. I’ve checked our Office 365 Health panel and see nothing new that might impact the backups. I’m running a backup to a local repository and have rebooted the backup server and the proxy server. I have plenty (4.8+ TB’s) of storage available on the repository. I went into the Organization setup and reentered the credential info and all of the checkboxes came back as successful. Has anybody else encountered this issue or does anybody have any hints for how to alleviate it?
Hey all,I’m just working with a 30-day trial and really focused on backing up my MS 365 environment. I set up a test using my on-prem backup server as the proxy and offloading the data to an Azure Blob (also a trial). And it worked! :DBut it’s slow. Like 1.2 MB/s processing rate.My question is, has anyone setup something similar with an Azure VM as the proxy? And if so, does it improve performance? Thank you very much for your time!
Am I the only one who does not like the fact that the Linux Backup/Mount Proxy needs a user that can do a su or sudo on anything?I would love to see the list of commands the Linux Proxy service user is actually using and then I would configure the sudoers list to allow those commands and nothing else.If the service user has the permission to execute any command with sudo, it de facto becomes a second root user, which we would very much like to avoid on any of our Linux boxes!Let me know what you think!
Hi, Does Any One Know A Way Of Reproducing The Daily E-Mail That Is Sent Which Contains In A Report:-Veeam Backup for Microsoft Office 365 Type Name Status Start time End time Items Data size Details Also, What does The Items Column Stand For? is it total sent and received mali, I Have Looked In VEEAM Manuals But I Can’t Find The Answer? The Ability To Run This Report Would Be Handy To Run For A Date Selection As Well? Thanks In Advance!, NicO!
Hi Folks, Just wanted to share my opinion on this. I was around when Cloud Connect was introduced and remember the struggle with customers when explaining backup copy job copy intervals. Often I would hear.. “can we not just have our legacy, backup job done then offsite?”. Veeam brought in the immediate copy not to long ago and I have already noticed some issues. When you leveraged periodic BC jobs you could set the copy interval differently for tenants with different quality bandwidth. I could be wrong but with Immediate copy if it gets behind it will copy one day, then right away try the next in order to catch up. If you have many backup copy jobs and only so many concurrent connections available this then becomes an issue. I prefer periodic copy, I can say to the tenant, yes we will get your backup copy jobs over the wire but with your current bandwidth we need 3 days… then it is up to them to increase bandwidth.
@Gostev mentioned some data loss issues in conjunction with VMware Tools quiescence in his current “the word from Gostev”. This method is used, when Veeam application-aware processing is not enabled ...… but “VMware Tools quiescence” is.Also because of such issues, Veeam recommends using their application-aware backup.So I want to ask the community, which backup method for application awareness do you use for Windows vSphere-VMs:Veeam application-aware processing VMware Tools quiescence.I personally try to implement Veeam processing whenever possible (security, network,...). At least for AD, SQL-based applications, Exchange, ...
I want to share a blog post by John Nicholson (VMware - not the guy from Shining !) which is about VMware Backup Myths. If you are in a backup related job, it could be funny to read. I did not know some of them!https://thenicholson.com/backup-myths/My favorites are:Virtual machine backups are not useful for file, or app level recovery. Agent-based backups are “lighter-weight” than hypervisor-assisted backups. Network based backups will bottleneck on the vCenter. Snapshots Suck. Here you have to read details in post! Enjoy reading!
Hi,we are running VMs on vSAN (VxRail). Backup with hot add mode works fine. Anything is ok.We are planning now, to offload big disks (>3 TB) to an iSCSI Storage device. z.B. PowerStore. So the VMs are running a mixed disk placement. System Disk stays on vSAN. Data Disk will be on iSCSI Storage. iSCSI Storage is attached to the same TOR Switch as the Veeam Rep Server. VMs are not stretched in the vSAN Cluster. Whats the best way to backup? What is your recommandation?
Hi, I have installed Veeam B&R v11 on a windows machine running a 5 Hyper-V vm. I have registered my Hyper-V using backup infrastructure > Add server. It now shows up in backup infrastructure > managed servers > microsoft Hyper-V > Standalone servers. I have created a backup repository on a NAS on the local network. But when I want to create a backup job (home > backup job > Virtual Machine), I have no VM listed. Any advices on what I’m missing to be able to backup my VM?
Hi, I have configured a backup job on all Teams and on first run, i am alerted the mailbox is already being protected by another job. 11-12-2020 11:04:59 :: Processing mailbox XXX completed with warning: Mailbox is already processed by another job This is correct, as i have a backup job doing backup of all mailboxes every 4 hours. What is best pracgtice? To do complete Teams backup including the mailbox in one job, and on another job do all my mailboxes and exclude the Teams mailboxes? As of now where i have the Teams mailbox backup done by another job, how would a Team site restore be done? RegardsRobert
Login to the community
Log in with your Veeam account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.