VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Good morning, everyone! Quick question. I have a copyjob that is throwing random “No Cloud Gateways available” errors. The odd thing is, it’s the only server that is having the issue and the our cloud connect server is fine. I am not quite sure what is happening between the cloud connect server and that backup server, but I want to get to the bottom of it! What would be the best Veeam log to check for info on that? I can run through the Windows Event Viewer, but I also want to see if any of the Veeam logs can shed some light. You all rock! Thank you so much for being great!
Hi, everyone I have some copyjobs that have been running for a significant amount of time due to a catchup-scenario we are in. I have noticed that on some of the jobs, it seems as if they start over. I check the jobs at some point the next day, and instead of the “Last Run” column showing days, I will see 8 hours ago, 3 hours ago, etc. The job will still be in running status. But it also looks like the job may not have started over. These jobs are immediate copy.
Hi, everyone! I have a quick question about coypjob intervals. If I have my copyjob set to 1 day starting at 4am, does that mean that the copy starts at 4am and runs until 4am the next day and then just starts over? I am seeing some warnings about things not being copied over in the copy interval. I’m a little confused on how this works. How can I make the copy interval longer?
Hi, everyoneI have configured Veeam Agent for Windows to backup to One Drive, for a user, and I am getting constant and consistent failures and I am not having much luck finding a solution. The errors mainly are: Veeam Agent 'job’ name finished with Error and will be retried. Job details: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: not an object Failed to download disk. Veeam Agent 'job name’ finished with Error and will be retried. Job details: Error: Shared memory connection was closed. Failed to backup file. File: [C:\WINDOWS\TEMP\digest_cd78e577-1055-4586-b7f1-5c21002d942d]. ItemSpec: [veeamfs:5:6745a759-2205-4cd2-b172-8ec8f7e60ef8 (ca7b02aa-1221-4b84-0868-8d2efa4aa31a)\digest_cd78e577-1055-4586-b7f1-5c21002d942d@cloud://<Path ConnId="f8d8bb00-8579-4324-910f-a29090f1a900" BackupId="197964ed-5767-4f66-9153-c709f0c1fdbb" StgId="838a66be-f1c4-4ce6-9f5f-b19467efea29" LocalPath="C:\
What does “Warning: some restore points failed to process” mean? I got this warning on a cloud copyjob and I can’t really find out what specifically it means or why it happened? Does this mean the copyjob failed or in a disaster recovery scenario that I’d have missing data that I couldn’t restore to from the cloud because it didn’t copy over? I ran a new sync and it was successful, but I am wondering what this warning means and how can I present it in the future?
I work pretty heavily with backups in my current role, and we use your product and another product with some of our clients. The other product has a feature that is incredibly helpful and I think would be an amazing feature to add to Veeam. How feasible would it be to add a “Force Retention” feature? I really believe we need this for situations when we run into low disk space. In Veeam’s current state, if I run into an issue where I need to reclaim disk space, I am forced to break my backup chain and delete data. If I could lower retention on my backup and then force retention, that would effectively eliminate the need for me to have to lose data and break a backup chain. For example: if I am in a situation where I am getting failures due to low disk space, and I have retention on said backup job set to 30 days, if I could cut retention down to, say, 20 days, and force retention, I could maintain my current backup chain and then address the disk space issue accordingly (adding more dis
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.