Netapp Altavault Challenges Evacuating Files

[chadsink]

Has anyone tried moving backup chains from an Altavault to another share, then importing them back into Veeam B&R? Because Altavault has been discontinued, there are several yearly backups that need to be moved. After playing around with folder permissions, the files can technically move to a standard Netapp FAS CIFS share(part of a SOBR). But when trying to import the backups, it gives me inconsistent information in B&R. For example, one backup folder imports correctly with the repository displayed in disk view. Another folder(verified permissions), shows the backup in disk view but does not display the associated repository. Also, if anyone knows of a better way in general to move these backups without having to manually butcher the permissions, that would be greatly appreciated!

[Andreas Neufert]

Hello Chad,

can you please check if you followed one of the options here? https://www.veeam.com/kb1729

[chadsink]

Yes I tried doing a "new job/new repository". When I attempt to map a backup, only 1 chain shows up in the SOBR. Strange thing is, I see additional folders(complete with associated backups and metadata files) when simply windows exploring into the SOBR location. But these do not show up in the list of possible "map backup" chains.

[Andreas Neufert]

Can you please open a support ticket and let our team have a look ?