Restore from LTO-6 tape
Greetings, everyone... I am puzzled if I will be able to restore from old LTO-6 tape after upgrading to the new environment. My old environment was:Windows Server 12 R2, using BE15, backup to IBM LTO-6 tape drive I am planning to upgrade to: Windows Server 2022 with the latest BE22, backup to new new LTO-8 tape drive In case I need to restore from old LTO-6 tape, is it supported restore from BE22 while it was backed up by BE15? And should the Inventory and Catalog operations done first before the restore? https://veritas.com/support/en_US/article.100042698
What is the best way to backup on to tape from flexscale?Does Flex Scale support tape backup over FC
Hi Team, I would like to know whether the backup on to tape via FC is supported over FC or not? The documentation is little confusing. If supported what is the best practice ? Thankyou in advance. Regards, Gopi G
Using Media Vault for Tape Management
We have several backup jobs that run just on the weekend that capture full vmWare guest servers. We run these to a Media Set that has two tapes. Recently we've ran into an issue where the first tape is almost full when another job kicks off and appends to it. Well, the data from that job is too much to fit onto that first tape, so it reaches the end of the job then just sits there prompting to import blank or scratch media. Well, we have a second tape available as part of the media set, but since it has other jobs on it, the job that is "hung" cannot append itself to another tape (read that this is by design). So I was thinking of using a Media Vault to export the first tape to after the 2nd to last job runs so that the final job doesn't get hung up after filling the rest of tape 1, instead, if tape 1 is exported to the media vault prior to the final job running, then tape 2 should be the only media available and it has plenty of space for the final job to write to. Can the Media Vault be used in this scenario? When tape media is exported to it at the end of the job, the media isn't available again until an inventory is ran against the slot, correct?
BACKUP EXEC 2014
Hello, We have backupexc 2014 installed on windows 2012 R2 server and we are backing up several physical servers which Includes Exchange Server and SQL servers. The backup server first takes the backup on the storage and then duplicates to the HP LTO 7 Tape drive. We have created a media group and added a tape to it. The problem is after 2 or 3 days the backupexec server adds a random tape from the tape drive and starts the backing up on that tape instead the tape which we have defined, I am also adding a screenshot to check
Backup Exec Not Recognizing Tape Media
I'm new to Backup Exec and am having trouble getting our backups working. We use NDMP to backup NetApp to a robotic tape library. Under the Media Properties of the tape drive it states "There is no media in the drive." When I try to run a job it gets stuck on "Active: Queued - Backup Scan" This is on Backup Exec 20.5. I've tried restarting the tape library and server, manually loading tapes to the drive, adjusting the overwrite protection, and inventories are completed succussfully. Any suggestions?Several drives going DOWN in short period with "MEDIA LOAD OR EJECT FAILED"
We have Netbackup 7.7.3 and attached to it tape library SL3000(attached over FC). 1. To the media/master server1(on Solaris 11 SPARC) attached robot and 13 tape drives from SL3000. 2. To the media server2(on SUSE ES 11) attached 5 tape drives from same SL3000 3.To the media server3 (on SUSE ES 11) attached same 4 tape drives from same SL3000 as media server2 It worked fine several years. But now, sometimes, when backups on server2 starts, several drives path may going down on server2 and different drives on server1. Support of tape library did not find any issues on library. We deleted all tape drives and added them again(this wag suggestion of tape lirary support team). Stange thing, that not shared drives was added with old names. This helps for two weeks. And now it comes again.. tpconfig -l output: Server1: Device Robot Drive Robot Drive Device Second Type Num Index Type DrNum Status Comment Name Path Device Path robot 0 - TLD - - - - /dev/sg/c0tw500104f000b22918l0 drive - 0 hcart3 4 UP - IBM.ULTRIUM-TD6.000 /dev/rmt/7cbn drive - 1 hcart2 3 DOWN - STK.T10000D.001 /dev/rmt/8cbn drive - 2 hcart2 2 DOWN - server1_579004003808 /dev/rmt/4cbn drive - 3 hcart2 1 UP - server1_579004005455 /dev/rmt/0cbn drive - 4 hcart2 8 UP - STK.T10000D.003 /dev/rmt/3cbn drive - 5 hcart2 7 UP - server1_579004002624 /dev/rmt/1cbn drive - 6 hcart2 6 UP - server1_579004008297 /dev/rmt/5cbn drive - 7 hcart2 5 UP - server1_579004005394 /dev/rmt/6cbn drive - 8 hcart2 12 DOWN - STK.T10000D.002 /dev/rmt/2cbn drive - 9 hcart2 11 UP - STK.T10000D.000 /dev/rmt/12cbn drive - 10 hcart2 10 DOWN - server1_579004006393 /dev/rmt/11cbn drive - 11 hcart2 9 UP - server1_579004006402 /dev/rmt/10cbn drive - 12 hcart2 13 UP - server1_579004006389 /dev/rmt/9cbn Server2: Device Robot Drive Robot Drive Device Second Type Num Index Type DrNum Status Comment Name Path Device Path robot 0 - TLD - - - - server1 drive - 0 hcart2 12 DOWN - STK.T10000D.002 /dev/nst1 drive - 1 hcart2 8 UP - STK.T10000D.003 /dev/nst0 drive - 2 hcart3 4 UP - IBM.ULTRIUM-TD6.000 /dev/nst3 drive - 3 hcart2 3 DOWN - STK.T10000D.001 /dev/nst2 drive - 4 hcart2 11 UP - STK.T10000D.000 /dev/nst4 Server3: Device Robot Drive Robot Drive Device Second Type Num Index Type DrNum Status Comment Name Path Device Path robot 0 - TLD - - - - server1 drive - 0 hcart2 11 UP - STK.T10000D.000 /dev/nst3 drive - 1 hcart2 3 UP - STK.T10000D.001 /dev/nst2 drive - 2 hcart2 12 UP - STK.T10000D.002 /dev/nst1 drive - 3 hcart2 8 UP - STK.T10000D.003 /dev/nst0 In messages on server1 we have errors: Jun 2 20:20:25 server1 tldcd[18489]: [ID 702911 daemon.error] TLD(0) key = 0x4, asc = 0x53, ascq = 0x0, MEDIA LOAD OR EJECT FAILED Jun 2 20:20:25 server1 tldcd[18489]: [ID 702911 daemon.error] TLD(0) Move_medium error Jun 2 20:20:54 server1 ltid[2215]: [ID 702911 daemon.error] Operator/EMM server has DOWN'ed drive STK.579004003808 (device 2) Jun 2 20:22:07 server1 avrd[2331]: [ID 702911 daemon.notice] Reservation Conflict status from STK.T10000D.000 (device 9) Tha same time on server2 we have messages: Jun 2 20:15:58 server2 kernel: st 11:0:0:0: [sg2] Warning! Received an indication that the mode parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Jun 2 20:20:12 server2 kernel: st 12:0:2:0: [sg6] Warning! Received an indication that the mode parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Jun 2 20:23:05 server2 kernel: st 12:0:0:0: [sg4] Warning! Received an indication that the mode parameters on this target have changed. The Linux SCSI layer does not automatically adjust these parameters. Jun 2 20:23:54 server2 ltid[15144]: Operator/EMM server has DOWN'ed drive STK.T10000D.001 (device 3)How to implement tape rotation with BE 21.0.1200
Hi, I am currently testing Backup Exec V21.0.1200. I would like to implement a data backup on tape and therefore have an LTO-4 tape drive, unfortunately without a tape changer. This means that I have to change the tape manually every day. No problem at first, if I knew which tape would be requested next, especially because I wanted to rotate the tapes according to the grandfather strategy. Unfortunately, I don't find an approach for this in this version. I'm grateful for every tip. Kind regards, Ulrich