OST and storage server creation
Hi, Im trying to create an OST disk pool and although the storage server is created successfully with the following command: nbdevconfig -creatests -storage_server<datadomain_name>-stype DataDomain -media_server <media_server_name> but it fails when tried to add the media server as a data mover with the following command: tpconfig -add -storage_server<same data domain name as before> -stype DataDomain -sts_user_id <user> -password <password> I have logged straight into the data domain with the supplied credentials and it gets in fine. I've checked its not using a mix of FQDN and shortnames by making everything local, even on the data domain, ive restarted nbrmms on the media server a few times so I'm bit at a loss to what to try next. The error I get is: Failed to open server connection to type DataDomain server scodd1: Error = 2060046 Authorization failed for OpenStorage server scodd1 Im using netbackup 7.0.1, DataDomain OS version is 4.9 and the OST plugin is version 2.5.1.0-326737. My media server is RHEL5. Could it be that I'm using too new a version of the OST plugin? I find it odd its happy to create the storage server but wont pass credentials. There was nothing I could see in the release notes to say the version of the OST plugin (which is the newest stable release) wouldnt work with 4.9 but maybe im wrong. Does any have experience of these versions? Thanks in advance for any help given. RobertSolved4.1KViews0likes4Comments
NBU with DD boost over FC
Hi, I'm currently doing some test fora project that the client is going touseNBU with data domain boost. We tried and sucess to backup data to DD boost through NBU, however, I can't establish the connection between NBU server and DD. Even the NBU server is visable to DD, NBU server wouldn't be able to mount the DD and see it on the device manager. Have search the NBU compatibilty matrix onhttp://www.symantec.com/business/support/index?page=content&id=TECH59978but I couldn't found the compatility of NBU and DDOS. 1) Can someone share the experience of using DDBoost over FC with NBU? 2) We are suspecting this is the compatability issue betweenNBU and DDOS, would that be a case? We are currently testing on Win server 2008 R2 with NBU 7.6.1 and DDOS 5.5.0.1. Best, BrianSolved3.9KViews1like3Comments
Netbackup 7 - Incorrect disk pool available space
Hi, I'm currently testing Netbackup 7 in our lab. I created a media server dedup disk pool (on a Win2k8 R2 Std 64 bits server). Backups were working fine until recently. I'm now getting error 129 (insuffisent disk space). After looking at the drive, I only had 18gb left (the drive is 1TB). I went in the catalog and expired a bunch of older backups. My disk space is now back to 120gb but for some reason, Netbackup's disk pool properties still report only 18gb as available space. I've tried restarting services (and even rebooting the server) but nothing changed. I figured maybe it would get updated by one of the admin tasks that runs every night so I left it like that for the week-end but this morning, the console still shows 18gb available space. Is there a way to force Netbackup to recalculate the available space? Also, on a related note... looking at the disk pool properties, there is a "Disk volumes" section where it reports my 18gb free space. I've search a lot but couldn't find a way to add a 2nd volume to the disk pool (didn't find anything in the admin guide or the console). Since the section has a "s" to volumes, I'm guessing it is doable. Can anyone point me in a direction in case I'd eventually need to add a 2nd lun to the server for additional space? Thanks a lot for your help! PhilippeSolved3.2KViews1like12CommentsDuplication jobs are stuck at "Waiting for positioning of media id"
We have an NetBackup 7.5.0.6 environment running on an RHEL5 Master Server and two RHEL5 Media Servers. Each server has access to all 16 LTO4 tape drives connected via two different libraries. On a regular basis I can encounter duplication jobs which seem to be stuck. All resources have been granted and a proper tape has been mounted. The file list contains the first image which should be duplicated in this batch and NetBackup claims that it's waiting for positioning the media. This can take take hours until finally the duplication process starts and then proceeds at expected speed (350 GiB/h) with multiple images in the batch. I know that positioning is not an issue as the same media and drives are used for B2T jobs which never show such behavior. Did anybody encounter something like this? Any hint where to look and what to check? Thanks Markus2.5KViews1like12Comments
AIR Replication via specific media server
Hi At a client we have a large AIR environment and some DB's that are deployed as media servers. When our AIR SLP's do replications between the various DataDomains, it seems to pick a random Media server. in the past we use to use the Media Server override to lock down Media servers. So that the Media server that did the backup would do the restore. Is there anything like that, that we can do with air to ensure the SLP uses a specific media server, or preferably the media server that backed up the date.Solved2.3KViews0likes5CommentsNetbackup : MSDP replication between remote sites within the same domain
Hello, I'm looking for feedback about replicating data from MSDP media server on remote sites back to main site. As they are on the same domain, I guess I won't be able to use AIR. Is there something similar for intra domain replication ? Is there a way to boost finger print seeding ? (without using tapes or moving servers) Or will it be better to create a local master server and use AIR ? BTW, what is occuring if a regular duplication or AIR is failling ? Is there a resuming feature, or do we just rely on the learned deduplication info to partly recover the already duplicated info ? Last be not least, I'm using resilient connection (works really nice with file backups). Is it possible to strip the stream to multiple streams ? I've got huge latency, and tcp is shapped. Thanks for your feedback,Solved2.1KViews1like5Commentsbackup Performence
how to improve backup performance(For example I am running a backup operation it is taking 10 hours (consider ) then I need it to finish it within 5 hours or below mean as early as possible is it possible or not if possible means how Give me an example )Solved1.9KViews2likes8Comments
sgscan doesn't see disk drives, sees tape drives
I'm on Solaris 10 master, NetBackup 7.0.1. My media server on which I'm having an issue is Solaris 10, NetBackup 7.0.1 Advanced Disk (PureDisk). I replaced a tape drive yesterday and then ran the sg.install. When I run the sgscan command it finds all the tape drives but not the disk drives - local or SAN attached. I've never seen this happen to disk before. Any ideas? cfgadm sees both tape and disk c1 fc-private connected configured unknown c1::500000e01066d351,0 disk connected configured unknown c1::500000e010670831,0 disk connected configured unknown c2 fc-fabric connected configured unknown c2::500507630061457b,0 tape connected configured unknown c2::5005076300616ff2,0 tape connected configured unknown c2::5005076300617c17,0 tape connected configured unknown c2::5005076300617d51,0 tape connected configured unknown c2::500507630061eedd,0 tape connected configured unknown c2::5005076313600e16,0 tape connected configured unknown c2::5005076313600e64,0 tape connected configured unknown c2::5005076313601021,0 tape connected configured unknown c2::50050763136010c8,0 tape connected configured unknown c2::50050763136011f5,0 tape connected configured unknown c2::5005076313601214,0 tape connected configured unknown c2::5005076313601287,0 tape connected configured unknown c2::50050763136012a4,0 tape connected configured unknown c2::5005076313601ead,0 tape connected configured unknown c2::5005076313606f7b,0 tape connected configured unknown c2::5005076313607556,0 tape connected configured unknown c2::500507631360780a,0 tape connected configured unknown c2::5005076313607cd3,0 tape connected configured unknown c2::500507631360a57e,0 tape connected configured unknown c2::500507631360a9b2,0 tape connected configured unknown c3 fc connected unconfigured unknown c4 fc-fabric connected configured unknown c4::50060e8003a80100,0 disk connected configured unknown c4::50060e8003a80100,1 disk connected configured unknown c4::50060e8003a80100,2 disk connected configured unknown c4::50060e8003a80100,3 disk connected configured unknown c4::50060e8003a80100,4 disk connected configured unknown c4::50060e8003a80100,5 disk connected configured unknown c4::50060e8003a80100,6 disk connected configured unknown c4::50060e8003a80100,7 disk connected configured unknown c4::50060e8003a80100,8 disk connected configured unknown c4::50060e8003a80100,9 disk connected configured unknown c5 fc-fabric connected configured unknown c5::50060e8003a80110,0 disk connected configured unknown c5::50060e8003a80110,1 disk connected configured unknown c5::50060e8003a80110,2 disk connected configured unknown c5::50060e8003a80110,3 disk connected configured unknown c5::50060e8003a80110,4 disk connected configured unknown c5::50060e8003a80110,5 disk connected configured unknown c5::50060e8003a80110,6 disk connected configured unknown c5::50060e8003a80110,7 disk connected configured unknown c5::50060e8003a80110,8 disk connected configured unknown c5::50060e8003a80110,9 disk connected configured unknown format sees the disk AVAILABLE DISK SELECTIONS: 0. c6t50060E80000000000000A801000000A8d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a801000000a8 1. c6t50060E80000000000000A801000000C0d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a801000000c0 2. c6t50060E80000000000000A801000000D8d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a801000000d8 3. c6t50060E80000000000000A80100000030d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000030 4. c6t50060E80000000000000A80100000018d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000018 5. c6t50060E80000000000000A80100000000d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000000 6. c6t50060E80000000000000A80100000090d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000090 7. c6t50060E80000000000000A80100000078d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000078 8. c6t50060E80000000000000A80100000060d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000060 9. c6t50060E80000000000000A80100000048d0 <HITACHI-OPEN-V*24 -SUN-2114-1.39TB> /scsi_vhci/ssd@g50060e80000000000000a80100000048 10. c6t500000E01066D350d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /scsi_vhci/ssd@g500000e01066d350 11. c6t500000E010670830d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /scsi_vhci/ssd@g500000e010670830 sg.conf has proper entries for disk and tape: name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500000e01066d351"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500000e010670831"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50060e8003a80100"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50060e8003a80110"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313600e16"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601ead"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300617d51"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360a9b2"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630061457b"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601287"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300616ff2"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601021"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136012a4"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136010c8"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="50050763136011f5"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076300617c17"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313600e64"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360a57e"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313607cd3"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313606f7b"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313601214"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507630061eedd"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="5005076313607556"; name="sg" parent="fp" target=0 lun=0 fc-port-wwn="500507631360780a"; but sgscan does not see disk: /dev/sg/c0tw500507630061457bl0: Tape (/dev/rmt/21): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300616ff2l0: Tape (/dev/rmt/6): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300617c17l0: Tape (/dev/rmt/11): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300617d51l0: Tape (/dev/rmt/2): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507630061eeddl0: Tape (/dev/rmt/17): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313600e16l0: Tape (/dev/rmt/0): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313600e64l0: Tape (/dev/rmt/12): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601021l0: Tape (/dev/rmt/7): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136010c8l0: Tape (/dev/rmt/9): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136011f5l0: Tape (/dev/rmt/10): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601214l0: Tape (/dev/rmt/16): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601287l0: Tape (/dev/rmt/5): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136012a4l0: Tape (/dev/rmt/8): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601eadl0: Tape (/dev/rmt/4): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313606f7bl0: Tape (/dev/rmt/15): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313607556l0: Tape (/dev/rmt/18): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360780al0: Tape (/dev/rmt/19): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313607cd3l0: Tape (/dev/rmt/14): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360a57el0: Tape (/dev/rmt/20): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360a9b2l0: Tape (/dev/rmt/1): "IBM ULTRIUM-TD2" here's the steps I took to update: 1. devfsadm –C 2. cfgadm -al -o show_FCP_dev 3. cfgadm -c configure c2 4. mv /usr/openv/volmgr/bin/sg.conf /usr/openv/volmgr/bin/sg.conf.old 5. /usr/openv/volmgr/bin/sg.build all -mt 20 -ml 0 The file ./st.conf should be appended to /kernel/drv/st.conf. A reboot may be necessary to create any new device files. Created file ./sg.conf. Created file ./sg.links 6. mv /etc/devlink.tab /etc/devlink.tab.old 7. cp /usr/openv/volmgr/bin/sg.links /etc/devlink.tab 8. mv /kernel/drv/sg.conf /kernel/drv/sg.conf.05122005 9. cp /usr/openv/volmgr/bin/sg.conf /kernel/drv/ 10. devlinks 11. rem_drv sg 12. cd /dev/sg 13. rm * 14. /usr/openv/volmgr/bin/driver/sg.install Copied files to /kernel/drv and to /kernel/drv/sparcv9. Doing add_drv of the sg driver Leaving existing sg configuration. If you wish to update the configuration you need to rm -f /kernel/drv/sg.conf and rerun /usr/openv/volmgr/bin/driver/sg.install. 15. /usr/openv/volmgr/bin/sgscan /dev/sg/c0tw500507630061457bl0: Tape (/dev/rmt/21): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300616ff2l0: Tape (/dev/rmt/6): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300617c17l0: Tape (/dev/rmt/11): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076300617d51l0: Tape (/dev/rmt/2): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507630061eeddl0: Tape (/dev/rmt/17): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313600e16l0: Tape (/dev/rmt/0): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313600e64l0: Tape (/dev/rmt/12): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601021l0: Tape (/dev/rmt/7): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136010c8l0: Tape (/dev/rmt/9): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136011f5l0: Tape (/dev/rmt/10): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601214l0: Tape (/dev/rmt/16): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601287l0: Tape (/dev/rmt/5): "IBM ULTRIUM-TD2" /dev/sg/c0tw50050763136012a4l0: Tape (/dev/rmt/8): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313601eadl0: Tape (/dev/rmt/4): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313606f7bl0: Tape (/dev/rmt/15): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313607556l0: Tape (/dev/rmt/18): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360780al0: Tape (/dev/rmt/19): "IBM ULTRIUM-TD2" /dev/sg/c0tw5005076313607cd3l0: Tape (/dev/rmt/14): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360a57el0: Tape (/dev/rmt/20): "IBM ULTRIUM-TD2" /dev/sg/c0tw500507631360a9b2l0: Tape (/dev/rmt/1): "IBM ULTRIUM-TD2" 16. Run the Configure Storage Devices wizard in NetBackup.Solved1.9KViews1like2Comments
Duplication jobs are stuck at "Waiting for positioning of media id"
We have an NetBackup 7.5.0.6 environment running on an RHEL5 Master Server and two RHEL5 Media Servers. Each server has access to all 16 LTO4 tape drives connected via two different libraries. On a regular basis I can encounter duplication jobs which seem to be stuck. All resources have been granted and a proper tape has been mounted. The file list contains the first image which should be duplicated in this batch and NetBackup claims that it's waiting for positioning the media. This can take take hours until finally the duplication process starts and then proceeds at expected speed (350 GiB/h) with multiple images in the batch. I know that positioning is not an issue as the same media and drives are used for B2T jobs which never show such behavior. Did anybody encounter something like this? Any hint where to look and what to check? Thanks Markus
