Oracle Tape Backup failed with unimplemented feature
Hello everyone. I've recently learned to config FT and decided to test my oracle backups with FT. Normal filesystem backup from client is fine and it shows the transport protocol is FC. But when I start an Oracle policy, all of child processes fail with error "unimplemented feature", nothing more. Any idea what I'm doing wrong? Master server Netbackup version is 10.2 on Redhat 7.9. Client version is 10.0.1 on Solaris 11. Oracle version is 19c. Any help would be great
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)
Data to Tapes Not Compressed
I am using LTO6 tapes with the HPE MSL2024 tape library. I am sure the Hardware Compression has been enabled at the tape library level, but the data writing to the tapes does not seem to be compressed at all. Each tape shows Full when the usage reachs to 2.8TB which is just raw capacity. BTW, my NetBackup system is a NetBackup Appliance 5230. It looks like the hardware compression is disabled from the Appliance somewhere. Any idea would appreciated. Ross
Restore SQL Server from Tape Backup
Hi guys, I have to admit that I am very new for all the Netbackup things. Briefly.... I have 2 NBU server which are not in the same cluster. NBU1 is DC site , NBU is DR site. I have to get the tape backup from NBU1 to restore at NBU2. I have done the Phase 1, Phase 2 import and restore perfectly on VMware. But the problem I am facing right now is how to restore SQL server from data imported NBU2 to the new virtual machine.(Windows Server 2012) Netbackup is 7.6.1 I create a new virtual machine and already installed SQL Server, MS SQL Client, grant permission for user. Thanks in advance. I am very desparate.......Tape Elimination with Veritas Access
A significant number of my NetBackup customers are currently looking to eliminate tape within their environments. For a long time people have been saying that tape is dead but until recently I never believed it because of the amount of data you could store on an LTO tape and the performance of the drives, made it cheaper than an average disk array. With the introduction of deduplication technology, tape elimination started to become a reality but the cost to keep the data beyond a few months on deduplication pools was not cost effective and meant that tape still had a place within the environment for long-term retention. With Veritas Access this is about to change as customers are now able to send their long term backups via S3 to a cost effective scale-out NAS solution. This effectively creates a two-tiered storage platform for the backup environment, with primary backups sent to high performance storage while leveraging advanced features such as client-side deduplication and Accelerator synthetic backups to reduce backup windows. Any backups that need to be kept for long-term retention would be automatically duplicated to Veritas Access via S3. This approach reduces the amount of primary storage required, eliminates tape, including all the operational costs associated with it and if using NetBackup Appliances or custom built Media Server Deduplication Pools (MSDP), provides a single vendor backup solution. With this new approach to backups, tape elimination may become a reality after all.
