Netbackup Version: 7.6.0.1
Hata Tanımı: Politika içerisinden “policy storage” kısmındaki yedekleme yapılacak yeri değiştirmemize rağmen yedeği eski yere almaya devam etmesi.
Geçici Çözüm: Politikaya sağ tıklayarak “Copy to New Policy” seçeneğini seçmek, yeni politika üzerinden yedeklemeye devam etmek.
Kalıcı çözüm: Her zaman olduğu gibi, muhtemelen versiyon güncelleme gerekmektedir 🙂 Bulanlar bana e-posta atar ise burda yayımlarım.
Yaptığımız tüm testlere rağmen 3 ay boyunca problem networkten dediler, en son sunucu ile netbackup appliance’i arka arkaya bağlayınca yukardaki sonuç göründü. Bundan sonraki aşamada bulunanları bir sonraki makalede yazacağım.
Link: http://www.symantec.com/connect/forums/interrupt-when-backup-large-sql-databases
Son 2.5 senedir benzer problemler ile aylarca aşağıdaki döngüde uğraşırken şimdi aynı döngüye hafta mertebesinde girdiğim için yazma ihtiyacı hissettim.
Evet arkadaşlar adımlar bu şekilde aylarca hatta yıllarca uğraşmak istiyorsanız case açın, yoksa kendinizce bir çözüm bulun. Mesela MSSQL yedeği kendi üzerinden SQL script ile bir yere native dosya yedeği almak ve sonrasında bu dosya yedeğini netbackup ile yedeklemek gibi. Şimdiden kolay gelsin.
Not: Bilmiyenleri için söyleyeyim, Netpbackup appliance üzerinde iki tip disk var biri tekilleştirme yapılan Puredisk diğeride direk yazılan Advancedisk. Tekilleştirme yapıldığında hata alınıyor ve yapılmadığında hata alınmıyor ise problem tekilleştirme yapılan taraf ile ilgil olduğunu anlamak için mühendis bile olmaya gerek yok. Fakat bunu görmelerine rağmen inatla problem networkte diyenler çok kötü destek verdiğini gösterir.
___________________________________________________________
1 Open the Client, media and master server logs , try again and send the logs .
2 Increase timeout values.
3 If problem doesn’t resolve go step 2 again , if timeout value come over 7200 second, go 4 step now .
4 Symantec engineers say “you have network problems” , check the network .
5 Change the some media server ( appliance ) parameters
6 Change the client TcpWhatever parameters and reboot the client .
7 Take backup to Advanced disk. And probably you can take successfully backup to advanced disk and Symantec engineers can say “you have network problems” 🙂 again
8 If the problem still not resolved the problem, assign case to another engineer or backline and go step 1
In this way, If you want to deal with these steps for months or even years, open a case , or found a solution by yourself . For example, you can take MSSQL native backup, then backup this file with NetBackup . Good Luck.
Eğer Symantec Apliance almayı düşünüyorsanız, karşılacağınız problemler aşağıdaki gibi olacaktır. Bunlardan bir kısmı gündelik, bir kısmı haftalık ve aylık olanlar mevcuttur. Detaylı bilgi için benimle iletişime geçebilirsiniz.
If a schedule or schedules are not working, do following steps on the master server:
1. shutdown NBU services
C:\program files\veritas\netbackup\bin\bpdown.exe -v -f
2. use bpps or Services to check all the NBU service including PBX service are not running.
3. delete the below files if they exist:
C:\program files\veritas\netbackup\bin\bpsched.d\pempersist
C:\program files\veritas\netbackup\bin\bpsched.d\retirepersist
C:\program files\veritas\netbackup\bin\dbdbm.lock
C:\program files\veritas\netbackup\db\jobs\restart\*
C:\program files\veritas\netbackup\db\jobs\pempersist
C:\program files\veritas\netbackup\db\jobs\pempersist2
C:\program files\veritas\netbackup\var\nbproxy_jm.ior
C:\program files\veritas\netbackup\var\nbproxy_pem.ior
C:\program files\veritas\netbackup\var\nbproxy_pem_email.ior
C:\program files\veritas\netbackup\var\TaoNotifSvc*.*
C:\program files\veritas\netbackup\db\failure_history\*
4. startup NBU (reboot recommended)
C:\program files\veritas\netbackup\bin\bpup.exe -v -f
5. Run the following command:
C:\program files\veritas\netbackup\bin\admincmd\nbpemreq -updatepolicies
Error Code: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Example:
Follow
[08:01:47.379] [HostName] Connecting to SQL server HostName...
[08:01:47.383] [HostName] Transaction log backup for database [BSM] will truncate logs... [08:01:47.383] [HostName] Starting to backup transaction log for database [BSM]... [08:04:15.879] [HostName] Database [HostName:BSM] Percent: 5% completed [08:06:48.387] [HostName] Database [HostName:BSM] Percent: 10% completed [08:08:43.885] [HostName] Database [HostName:BSM] Percent: 15% completed [08:10:43.644] [HostName] Database [HostName:BSM] Percent: 20% completed [08:11:47.474] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. An exception occurred while executing a Transact-SQL statement or batch. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. [08:11:47.483] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. An exception occurred while executing a Transact-SQL statement or batch. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. [08:11:47.483] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. An exception occurred while executing a Transact-SQL statement or batch. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
http://netbackupsucks.blogspot.com/
…
That’s why NetBackup sucks and it’s not “Symantec Sucks”. I’ve used several Symantec products for years and never found any problem with them. Until NetBackup! I’ve used at least four major backup products since working with Network/System Administration from 1996 on. Sure some have had quirks, but nothing that lead me to completely loose faith in them.
…..
If you believe that the disk is too full that should be more than normally.(I had this problem on 3 netbackup 5220 appliance that version 2.5.2 and 2 windows media server that version 7.5.0.5, I found and deleted them,then 50TB space was freed from dedup disks of three apliances.) We need a bpimmedia list from the master server, and catalog lists from the deduplication media servers to compare and find out if there are orphaned images. Follow the steps below:
1) Identify the disk pool name and then collect NetBackup Image list from the Master Server:
For Windows master server:-
<install path>\veritas\Netbackup\bin\admincmd\bpimmedia -stype PureDisk -dp <POOLNAME> >c:\NBU_Images.txt
or for UNIX master server:-
/usr/openv/netbackup/bin/admincdmd/bpimmedia -stype PureDisk -dp <POOLNAME> >/tmp/NBU_Images.txt
2) Gather deduplication image list (replace “mediaservername” in the commands below with the actual media server name)
a) For Windows MSDP storage server:
Change to “<STORAGE_LOCATION>\databases\catalog” folder and run:
dir /b /s /a-d |findstr /vi “__” >c:\DEDUPE_IMAGES-mediaservername.txt
b) For Unix MSDP storage server change to “<STORAGE_LOCATION>/databases/catalog” and run:
find -not -name “__*__*” -type f >/tmp/DEDUPE_IMAGES-mediaservername.txt
3) Compare output files NBU_Images.txt and DEDUPE_IMAGES.txt files.
If you find extra image names in NBU_Images.txt, so, you have orphaned images.
Create a technical case in my.symantec.com or contact me to delete these images.
Regards.
Merhabalar,
Symantec Netbackup ve Netapp Snapmanager SQL ile yedekleme ve geri dönme ile ilgili hazırladığım dökümanlara aşağıdaki linklerde ulaşabilirsiniz.
Ayrıca geri yükleme dökümanında netappdaki snapshottan dönmek için yapılan lun clone yöntemi de anlatılmakta.