At least one of my clients does this, and successful file restores as well

O seu cliente usa o veeam e consegue copiar o volume NSS ( Dados ) - não estou conseguindo configurar,  entrei em contato com o suporte da veeam, me foi passado que não dão suporte para este tido de volume,  que é muito antigo.

saberia me explicar melhor como vcs conseguem fazer a copia ?

Obrigado

A) NSS is a current and supported file type on OES by Veeam.  Clearly a support tech who thinks you were talking about NetWare, as if talking about Microsoft means DOS.

B) are you trying to copy the whole volume, or the files?   And what versions are we dealing with on both Veeam and OES levels?

Falei para o técnico que é NSS no OEs e na ultima versão 
Tentei copiar o volume inteiro e apenas os arquivos 
VC conseguiu de qual forma 
Obg

I haven't done such a whole volume copy.  Where are you trying to copy it too?  There are different ways depending on what exactly you are aiming to do.

eu estou tentando copiar para uma NAS 

That sounds like you'd want to do a restore of all the files of the volume to another destination, as a NAS by definition is files only, not necessarily able to host a vm datastore. 

VEEAM, SEP and other backup tools have support for NSS file systems, so backup and restore is basically possible. To be able to back up an NSS with VEEAM, a helper VM is required as far as I know. I do not want to give any information about the configuration of VEEAM here, this is the wrong forum for that.

The first step is to be aware of what it means to perform an NSS-compliant backup. If an NSS-compliant backup is made, the data itself and the metadata are backed up accordingly so that a restore to an NSS volume can take place. There are some basic things to know here. An NSS Novell Netware backup cannot be restored to an OES LINUX NSS volume without further ado. It is also impossible to restore a native NSS backup to an XFS or NTFS volume, for example. One possibility is to use the Extended Attributes (xAttr) command if the client or SNAP Shot API of the backup vendor supports this xattrib. A corresponding configuration must be made in the NSS for this. Arcserve, for example, no longer has NSS support, but supports the xattrib command via the SAN Agent and File System Agent and can therefore actually back up and restore NSS data. A restore with xattrib support can be performed on non-NSS volumes.

This was just a small excursion into data backup and NSS restore. Nbackp and Rsync can also back up in compliance with NSS, it is possible to move data back and forth from Novell Netware to OES LINUX if you know which switches are required. I would be happy to go into more detail here. Based on my long experience, I can only advise you to back up data to long-term archives independently of the manufacturer. After 10 years or more, it may be that the manufacturer of the backup software as well as OT, Microsoft or whoever has changed the file system in such a way that a restore fails. There are so many regulations that have to be adhered to today, a backup or an emergency recovery has to take this into account. File NAS systems offer a Rsync function. Rsync knows switches that allow the meta data and rights of an NSS volume to be synced. I often use this option in the field to have a data backup in a remote network behind a perimeter that can be accessed in an emergency if no OES or eDir is available. 

A brief suggestion at the end. One interface for NSS classic Backup is the TSA interface. Even under OES 24.x there is still the tsatest tool which can help to exclude basic errors for the NSS backup. I still use the tool today to find logical errors in the backup, for example, if errors occur in the backup application when backing up data

                 SMS - TSA Statistical Analyzer

Read Count:                             Min. Read Time:
Last Read Size:                         Last Read Time:
Total Bytes Read:                       Max. Read Time:
Raw Data MB/min:                        Avg. Read Time:
Backup Sets:                            Avg. Scan Time:
Avg. Open Time:                         Total Read Time:
Avg. Close Time:                        Elapsed Time:
Effective MB/min:                       Total TSA Time:
                                        Max. Error:
                                        Avg. File Read Time:


LOG:
server
Error code NWSMTSConnectToTargetServiceEx fffdffd7
Error:Failed to connect Target Service:Username or Password invalid
Disconnected from TSA
Press any key to exit

  Server .Linux File System
Connected to TSA: Server.Linux File System
TARGET SERVICES: 940d1f10

Screenshot of a Lab server, an example of an error, the user who should perform the backup is not authorized, from the error it can be seen that the nam.conf or lum has a defect.