Symantec netbackup appliance problemleri

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.

•Diske yazma ve ya diskten okuma hatası: Yoğunluktan ve ya bu nedeni ile kısa süreliğine diskin «down» konuma geçmesinden kaynaklanmakta.
•Diskin kullanılmaz hale gelmesi: Bazen diskin «down» konuma geçerek yeniden başlatılana kadar bu şekilde kalması.
•Diskten kasete kopyalama yapılamaması: Yukardaki sebeplerden ötürü ve ya bir şekilde katalogdaki sunucu adı ile netbackup politikası içeriğinde görünen sunucu adı arasında küçük-büyük harf farkı var ise ilk diske yazma yapılmasına rağmen diskten kasete yazamamakta.
•Disklerin ayda bir yavaşlaması: Disk yazma önbelleğine bağlı olan bataryanın ayda bir boşaltılıp doldurulması nedeni ile önbelleğin etkisiz hale gelmesi ve yazma işleminin birkaç günlüğüne aşırı yavaşlama problem.
•Replikasyonun belirtilen şekilde optimize çalışmaması, ve hiç tamamlanamaması.
•Cihazlar üzerindeki güncelleme, yama yükleme ve bakım işlemlerinde uzun süreli problemler yaşanması.

Symantec netbackup schedule is not working

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


Snapmanager for SQL: Timeout Expired

Error Code: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Example:

[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.

Read More


netbackup sucks http://netbackupsucks.blogspot.com/

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.

…..


How to find orphaned images on disk for netbackup? ( dedup disk or advanced disk full problem )

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.