Backup OES Server / Novell Storage Services

Hi ​@ncl_ - Welcome to the Community.

Can you share a bit more about this setup, specifically your OES server? Normally I’d say that should be enough..assuming your OES server is a VM, and the Volumes for the OES server (VM?) are part of the VM as well. I would say backing up the VM should be good enough, but am not really familiar with Novell/OES. At the very least, you can reach out to Veeam Support and have them verify your backup goal.

Hello ​@coolsport00. Thank you for the quick response!

Sorry, I should haved made it clear in my post that the OES Server is a VM the volumes are part of that VM aswell of course.

I’ve already reached out to the support, but since I’m currently only using VBR Community Edition I’m not expecting a response any time soon and thought maybe I could get some help in this forum.

Yeah...with CE edition Support is a ‘best effort’ kinda deal. But again...if you’re backing up the Volumes as well, you should be good. You can do a test FLR as well. Go through the process, open up the FLR Exporer window and see if your metadata files are there. You can even do a restore if you want, but do so to a different location. That should validate your concerns.

hi ​@ncl_ 
 

Its my understand that Veeam can only do file‑level restore [FLR] on:

• Ext2/3/4
• XFS
• Btrfs (limited)
• ReFS
• NTFS
• FAT/exFAT

NSS/OSE is not supported for file‑level restore browsing if understand your question correctly. 

So, you would not be able to mount your VM backup and browse inside the NSS volume to restore individual files.

The only option would be:

• Restore the entire VM disk,
• Then manually mount it on an OES server,
• And extract the file system contents using native OES tools.

Well this is unfortunate since this was the biggest reason I wanted to use Veeam.

I’ve tried your solution by restoring the entire disk to the OES server. The problem now is, that I can’t mount the disk on that server, because the pool I’m trying to restore already exists.

Only solution I can think of right now to circumvent this, is to restore the entire VM, mount a new disk to that VM, copy the files onto that new disk, unmount it and mount it onto the production VM to copy the files over.

Well since we are using Proxmox as a virtualization platform, there is no option to create a helper appliance and since the requirements for Guest File Restore in Proxmox doesn’t mention NSS I guess it’s not supported. 

In that case you’d use a linux helper host

Thanks for sharing about the OES support ​@ddomask 👍🏻 Good to know for any others who have need to back it up with Veeam.

Thank your for your help. Do I understand correctly that I need a license for that use case and can’t use Community Edition?

https://www.veeam.com/veeam_data_platform_feature_comparison_ds.pdf

AFAIK you can always do restores of any type, you just need to add a Linux Managed server in the Backup Infrastructure section.