Security Tips for Storage and Backup Admins

1. EMC Networker: Change “remote access” option *@*  on every client” –> http://sysarticles.com/emc-networker-security-exploit-that-remote-access/

2. Veritas Netbackup: Remove No.Restrictions file –> http://sysarticles.com/security-expolit-on-netbackup-no-restrictions/

3. EMC VMAX: Change default password of SMC user in unisphere (take snapshot or backup before changing. If you would get “Failed to authenticate user.” error, there is no way to fix except restore or reinstall. And, If you reinstall unisphere you will loose performance database. There is a trick to not get this error.)

4. EMC VPLEX: Change default passwords of VPLEX. Default passwords of VPLEX is already complex, but anyone can find default passwords of service, admin and root users in the documents.

5. Commvault: Activate Ransomware Protection –> http://documentation.commvault.com/commvault/v11/article?p=features/disk_library/t_enable_ransomware_mediaagent.htm


How to Expand a Striped Meta on EMC VMAX (Disk büyütme işlemi)

1. Create new meta devices that you will add to disk:

symconfigure -cmd “create dev count=X, size=cyl, emulation=FBA, config=TDEV, mvs_ssid=0, device_attr=SCSI3_persist_reserv;” prepare / commit

·        Change the X and Y to the correct values for your environment

·         Make a note of the device IDs, I’ll call them AAAA and BBBB, assuming you created two

Example: symconfigure -sid 096 -cmd “create dev count=8, size=27776 cyl, emulation=FBA, config=TDEV, mvs_ssid=0, device_attr=SCSI3_persist_reserv;” commit

New symdevs: 01D1C:01D23 [TDEVs]

 

2.      Create new BCV meta devices that exactly same as Striped Meta that you want expand :

symconfigure -cmd “create dev count=1, size=Y cyl, config=BCV+TDEV, emulation=FBA, mvs_ssid=0;” prepare / commit

·        Change the Y to the current size of the meta you are expanding

·         Note the device IDs, I’ll call them XXXX and YYYY, assuming auto meta settings created two devices

Example: symconfigure -sid 096 -cmd “create dev count=8, size=27776 cyl, config=BCV+TDEV, emulation=FBA, mvs_ssid=0;” commit

New symdevs:  01AAC-01AB3

 

3.       Create volume from BCV meta devices:

symconfigure -cmd “form meta from dev XXXX, config=striped, stripe_size=1 cyl; add dev YYYY to meta XXXX;” prepare / commit

you can make 2nd and 3th steps with unisphere:

a.        Select Storage -> volumes -> “Create meta volume” under BCV+TDEVS 

image001

b.        Select “Create volumes” and “Using New Virtual Volumes”.

image002

c.       Enter Member Count and Member Capacity that exacly same as stiraped meta that you want to expand , then select BCV+TDEV.

Number of Meta Volumes 1 * Meta Volume Capacity Meta Volume Member Count including Head Meta Volume Member Capacity 2776JJ Calculated Meta Volume Capacity 2034 GB ¡ 222 S Cyl * Volume Configuration B+TDEV

d.        Select “Run Now”, then copy device IDs.

 

4.      Bind this meta to a pool – symconfigure -cmd “bind tdev XXXX to Pool <POOL> preallocate size =ALL allocate_type = persistent;” prepare / commit

·         Replace <POOL> with one of your pool names

with unisphere:

a.        Select Bind under Storage -> Thin Pools -> Pool:

Rebalance Variance (1-50) 1 Maximum Volumes per Rebalance Scan .. 256 Pool Reserved Capacity Enabled ü Expand Bind

b.        Enter Volume ID, then select “Find Volumes” :

Thin Volunıes Wizard 1 Find Volumes Find volumes that match the following criteria Capacity equal to GB %. Volume ID 3335 (e.g. 001 or 001-OFF or 001 ,003-OTF) Volume Identifier Name Additional Criteria Select Category Add Another Clear All Find Volumes> Cancel Help

 

c.    Select related volume, “Allocate Full Volume Capacity” and “Persist preallocated capacity …” , then click Bind :

Selected 0 items Allocate Full Volume Capac) Persist preallocated capacity through reclaim or <Modify Criteria Bind Cancel Help

 

Not: if Dynamic RDF is enabled you will get  “ Error occurred while Defining change number 1:

   The devices being acted on are a mixture of dynamic and Non dynamic DRDF devices

   Device 1D1C generated the failure”

errors at 5th step. So you must enable Dynamic RDF on AAAA:BBBB devices

To enable Dynamic RDF :

symconfigure -sid aaa -cmd “set device AAAA:BBBB attribute=dyn_rdf;” commit

Example: symconfigure -sid 096 -cmd “set device 01D1C:01D23 attribute=dyn_rdf;”  commit

5.     Now you can add new meta devices:

symconfigure -cmd “add dev AAAA:BBBB to meta ZZZZ, protect_data=TRUE, bcv_meta_head=XXXX;” prepare / commit

·         AAAA and BBBB are the device IDs created in step 1

·         ZZZZ is the device IDs of the meta head you want to expand

·         XXXX is the device IDs of the BCV meta head created in step 3

·         Example: symconfigure -sid 096 -cmd “add dev 1D1C:1D23 to meta 08BC, protect_data=TRUE, bcv_meta_head=1AAC;” commit

 

6.    After expand operation you can unbind BCV volume, then dissolve and delete BCV meta devices. Look at: “EMC VMAX – Removal Of A TDEV”

 


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


Symantec Netbackup ve Netapp Snapmanager SQL ile yedekleme ve geri dönme

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.

UT – Veri yedekleme talimatı

UT – Geri Yükleme talimatı

Ayrıca geri yükleme dökümanında netappdaki snapshottan dönmek için yapılan lun clone yöntemi de anlatılmakta.


Netapplarda tüm volume ler için autogrow ve snap autodelete ayarlayan script

Netapp üzerinde snapshotlardan dolayı lun offline sorunu ile karşılaşmak istemiyorsanız, mutlaka vol autogrow ve ve snap autodelete ayarlamanız gerekmekte. Her ne kadar yönetim için kullandığınız grafik arayüzü ile oluşturduğunuz lunlarda bu özellikler otomatik gelse de eskiden kalma ve ya komutla oluşturulan lunları kontrol için faydalı olabilir.

Powershell script indir

Örnek: .\set_autogrow_and_snapautodelete.ps1 -filer filername -user root -pass password -change yes

Not: Scriptin çalışması için plink.exe C:\WINDOWS\system32 içerisinde olması ve ya -ssh parametresi ile yerini göstermeniz gerekmekte.


Netapp Volume Checklist

VOLUME CHECKLIST

Netapp üzerinde bir volume yaratıldıktan sonra ayarlanması gereken parametreler aşağıda belirtilmiştir. Opsiyonel olduğu belirtilmemiş ise mutlaka girilmesi gereklidir. Netapp System Manager üzerinde ayarlanabilen komutlar için komutun hemen altında ilgili resim bulunmakta ve ayarlanması gereken kısım kırmızı kutu içerisinde gösterilmektedir. Komut içerisinde volume adlari vol_adi ve lun adları lun_adi olarak belirtilmiştir.

Read More


NetApp üzerinden ESX e iSCSI ile nasıl disk verilir?

ESX e Netapp üzerinden iSCSI ile disk verme

  1. Kurulum yapılacak Windows sunucunun NetApp tarafından hangi yazılım versiyonları ile desteklendiğini öğrenmek için http://now.netapp.com/matrix adresinden gerekli kontrolleri yapınız.
  1. NetApp matrixinde bulduğunuz konfigurasyon içerisinde deskteklendiği belirtilen NetApp ESX iSCSI Host Utilities yazılımının matrixte belirtilen versiyonunu http://now.netapp.com/NOW/cgi-bin/software adresinden indirip yükleyiniz.

Read More


NetApp üzerinden Windows 2003 e iSCSI ile nasıl disk verilir?

Windows 2003 için iSCSI Software Initiator Kurulumu, Netapp üzerinden LUN oluşturulması ve Ayarlamaları

  1. Kurulum yapılacak Windows sunucunun NetApp tarafından hangi yazılım versiyonları ile desteklendiğini öğrenmek için http://now.netapp.com/matrix adresinden gerekli kontrolleri yapınız.

Read More