VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
The simplest way to accomplish this is to backup directories distributed over several jobs… But I think this is not what you want…. No, this does not work. If you select just one small folder and put it in a job by itself this backup still won’t run. When the job starts Veeam will engage the VSS function on the Windows OS. Because the disk is bigger than 64TB the VSS function won’t start. At this point the Veeam job will fail. Veeam uses VSS whether it is a folder or a volume backup.
It has one drive letter but underneath it is really x2 100TB volumes. Individually still breaches the 64TB VSS limit. As @Jmeixner stated, you can take bakup via multiple backup jobs. You can use dikpart from windows and split the drives into smaller chunks ( e.g. 4 * 50TB or more) and then add each drive letter to different backup job with different backup timings. If I split up the volumes it’ll effect the user experience. Instead of all their files being in one drive they’ll have to open different drives to get to different files. I’d be interested to hear if it is possible to split the volumes without losing the data. I'm extremely doubtful that could be done but I wouldn’t have thought it is possible.
yep. It is a bit weird but the explorers look like separate components. I guess there is a technical reason why the explorers are separate from the main o365 console. If the explorers are not installed and up to date there will be problems… particularly with restorations… perhaps also with backup itself… I can’t remember.
As mentioned i am slowly learning Veaam infrastructure,. and ensuring everythhing in our current system is working, In the process a client upgraded from 9.5 to 12,. but hit issues and uninstalled everything and reinstalled,. however we provide 365 back up with storage,. this client isn’t a normall managed client and they only pay for licenses, but i need to get this back up and running for them,. i have the 365 server (running 365 v7 and B&R v 12but i am unsure how he connects to store? feel i am over thinking this one slightly and their is a simple answer that isn’t involve b&R If you are installing the o365 software onto a fresh build of Windows you have to bear in mind that sometimes ports are blocked and sometimes the WinRM must be enabled. I am sure all of this is covered in the Veeam documentation but I understand they are not paying you to sit down and read books so if you did not pay proper attention to the installation guidance you might have missed something
“Unfortunately, the fixes reported by Microsoft in these don’t appear to work” Means it isn’t the same cause? I’ve not had this issue with HPE kit. I use direct attached disk shelves for backup rather than any of the dedicated storage platforms.
We’ve setup a test environment (which can’t be permanent due to licensing) to test the concept of NAS backup in this scenario and we got the following line in the Actions list to show this will likely work. “14/03/2023 11:26:01 :: Failed to create a VSS snapshot, failing over to direct backup from the file share Details: Unknown status of async operationThe shadow copy provider had an error. Check the System and Application event logs for more information.--tr:Failed to create VSS snapshot.--tr:Failed to perform pre-backup tasks”. In other words it attempts VSS as the first method but that fails and it moves to direct mode. This is NOT treated as an error so if the backup completes successfully in other respects this line in the backup will not produce a failed or warning status which is good news.
Have you got any more information on the ‘LVG’ snapshot as I can’t find any reference to it. Have you got a link to the page in the Veeam documentation which describes how to configure this?
That would be similar to solution 3 from Nikita earlier. i.e. use the hardware VSS instead of the Microsoft VSS.
Naa. It’s a physical Windows 2019 server. I do have places I can create a VM specifically to assist with this backup but you’re not being clear on the details. Unless you’re saying this only works if the whole server is a VM and the storage is on a SAN or something like that? What is the significant difference which means the backup would work if it was a VM type backup?
If the server is a VM you could back it up with VBR but don't enable Application Aware Processing. That to me is the only other way around it. I have seen this work. This is an interesting idea. It has the potential to work if what you’ve said about seeing it working is correct. What do you think the process is for making this happen? I would have to create a VM first of all. Could I site the VM on the physical server which has the physical disk attached to it?
As for now I see three options: Split the volumes into smaller sizes and then back up each volume separately. This would require additional planning and management, but it is a viable option. Sooner or later it becomes an enormous volume with really hard management capabilities. Another option is to use Veeam Agent in “file – level backup mode”, where you can choose the exact directories to be backed up and split the jobs (can take a looong time to complete). And the last one is not to use the Windows Software VSS Provider (that has the actual limitation of 64TB volume for VSS snapshot), but the Hardware one and use the storage snapshots to perform the backup. More details here. Please check if the volume presented to this physical machine resides on the supported storage array. I would definitely check out these suggestions for the backup. Not sure you will find many other options. It’s bad news though, isn’t it… if we can’t backup more than 64TB with Veeam… unless you
It has one drive letter but underneath it is really x2 100TB volumes. Individually still breaches the 64TB VSS limit.
So there aren’t any other options?
Hello, I guess this machine could be a File Server? While Veeam Agent for Windows (and any other application leveraging Microsoft VSS) cannot back up volumes larger than 64 TBs, you could protect this server using NAS Backup (a feature of Veeam Backup & Replication). Of course this would be a file-level protection, as opposed to volume-level or machine-level, but it does not have limitations in terms of source volume size. As a potential additional option, if this is a VM, you could try a crash-consistent backup, disabling both Application-Aware Image Processing and Indexing. I have thought about NAS backup but the stupid license calculation means that single backup would cost us about £60,000 in licensing. 400 licenses.
What is on the server that you need VSS for? And is this a VMware level backup or Agent level backup you’re trying to achieve? When you set up a backup by default it’ll use VSS. The server is a stand alone physical Windows 2019 with a large direct attached storage array. I’m of the view (without bothering to really research it) that VSS is the process by which changes are tracked. Without it I think the system would try to backup all the data on each run of the job.
did it work?
If you select ‘Run As’ from the right-click context menu when starting Backup & Replication console it’ll make a difference to the access you have when performing a restoration. i.e. run as administratorIf that doesn’t work then you should wipe your permissions from the data drive when you’ve stored your backup files. I think the former suggestion should work for you though. On Windows 2019 you can set the shortcut to always run as administrator so that helps avoid this if you’re running into the problem regularly.
That functionality is different between backup and backup copy jobs. The ‘left arrow’ thing doesn’t work if it’s a copy job… only for a standard backup. So having discovered this I think there could be a possibility that the same would be true for the ‘report’ function when it comes to a backup copy job.
I think statistics only covers the job as it is currently running. It wouldn’t show previous sessions. I get why you’re asking though.
It’s not a support ticket as it’s a program ‘feature’. I don’t care if they don’t resolve it, I get an email with the report on. But it is nevertheless an inconsistency.
...and actually, I’ve just checked. The history section does not keep the information in the scenario where the job has not completed an initial backup.
But it’s still inconsistent that it is in the report only if the job has completed once successfully. If there was ever a time when seeing information about job failures was important it would be at the initial backup when you’re still working out compatible settings for the job.
I saw that article but looking at my setup I found I was already on the latest version so it was no use to me. My case was the same as the one described above. I had a proxy server which was out of date. I had another similar instance a few days ago. This time I found the application had lost the shared secret details. I had to put them in again and it was fine after that. I think I’ve seen that happen once before 6 months ago. It just forgets the authentication information.
Same happened to my setup on 5th/6th May 2021. Working fine, then stopped working. Solution was to upgrade the proxy.
Release of version 11 is coming imminently. It’ll probably be generally available before you’ve had time to procure and configure hardware and software for this project so it would make sense to plan to use version 11 from the get-go. Veeam releases are unlike Microsoft releases in the sense that they are tested prior to release… haha. I can’t think of a time any of the features I regularly use being compromised by a version release. Anyway, the new version gives you the ability to create an immutable disk based repository on a specially configured Linux server. Disk is actually very similar to tape in terms of cost these days, so why make life hard for yourself with tape. The main concern when it comes to the 400tb size you have will be restore time in a DR scenario. Day to day backups will be manageable on basic hardware as only incremental backups are taken after the first full backup. So you must find out from a discussion with the organisation owners what their cost v.s. res
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.
