Thank you very much for your tips and help. But nothing helped.Ĭan i automated this? When a script is used, do i have to setup the windows scheduler for this script or can i do that in Veeam B&R (something like "start this script before that job")?
![veeam backup to tape veeam backup to tape](https://bp.veeam.com/vbr/2_Design_Structures/D_Veeam_Components/D_tape_server/media/image25_updated21.png)
![veeam backup to tape veeam backup to tape](https://helpcenter.veeam.com/docs/backup/vsphere/images/linking_backup_to_tape.png)
I just inventoried, marked it as free and moved it to the customer media pool manually. It doesn't matter which tape i take, Veeam recognizes it as "Unrecognized" and do nothing until i mark it manually as free. With v11 we got the new feature called instant file share recovery which lets us publish file shares directly from the backups previously created with NAS backup jobs. With this i think the tapes should be now known by Veeam B&R. But as we all know, Veeam’s NAS backup doesn’t support tape (yet), neither as a primary nor as secondary (backup copy or archive) target. give a name to this tape (for example "Monday 1" etc.) What i already tried at the customer site is that:
#Veeam backup to tape how to
But with the information given there i'm not sure how to fix the problem, since i'm not so aware of Powershell. I already search the forum here and found the thread. I have to right click the loaded tape and mark it as "free", then the backup to tape job starts immediatly. A tape is loaded, but Veeam B&R puts it in the "Unrecognized" media pool and so the backup to tape job wont start. The tapes where used by Backup Exec before and should now be used by Veeam B&R tape job.Įverytime the backup to tape job starts, it is waiting. The customer has a LTO-6 tape drive connected to the backup server and LTO-6 tapes.
![veeam backup to tape veeam backup to tape](https://helpcenter.veeam.com/docs/backup/vsphere/images/files_to_tape_launch.png)
By default, Veeam Backup & Replication uses the account under which the Veeam Backup Service is running. To execute the script, Veeam Backup & Replication connects to Microsoft SQL Server. Things work well except backup to tape job. The path by default: C:Program FilesVeeamBackup and. First there is a backup to disk job (reverse incremental) followed by a backup to tape job (always the last backup state, which means the "calculated" full backup of reverse incremental backup to disk job). Since they had Veeam B&R for Backup to Disk and Symantec Backup Exec for Backup to Tape, i combined both with Veeam B&R. A few days ago i changed the backup solution at a customer site completely to Veeam Backup & Replication.