塔洛牌 - 二、女祭師 (The High Priestess)

正牌
愚人遇到了第二個人、女祭師。相對魔法師，她顯得非常安靜和内斂。手中緊握一卷露出一半的密冊(tora)，猜測這是有關人生和精神的秘密。但我覺得她並不會傳授給愚人，因爲時候未到。她的腳下有個月亮、一根寫B的黑柱、一根寫J的白柱、背後是被一塊屏風遮住了。月亮的力量是神秘的，而她卻可以踩在腳下，我想她比魔術師擁有更強的力量。胸前挂著的十字架，古希臘認爲世界由四种物質組成 -- 空氣、水、火、土，也表示東南西北。B是Boaz, J是Jachin。它們是耶路撒冷第一座寺廟 - 所儸門廟的兩根銅柱(From wikipedia)。B柱代表一切負面的力量而J柱代表一切正面的力量，屏風卻遮住了之間的一切，這些秘密的知識只有女祭師知道。我們人類能知道嗎？

反牌

黑白顛倒、女祭師沒有了支配月亮的力量、密卷也搖搖欲墜。

塔洛牌 - 一、魔術師 (The Magician)

正牌

聖杯(cups)代表愛情和情緒上的事
權杖(wands)代表事業，也有人說是創意、行動、熱情。
錢幣(pentacle)代表錢財和健康，是實在的物體。
寶劍(sword)代表人緣，也有人說是智慧、意志、挑戰。
愚人遇到魔術師，魔術師是非常正面和有力量的。他頭上有一個無限的符號，手握魔棒，一手指天、一手指地。表示他擁有各種支援，有通天地和改變的無限能力。魔術師腰纏蛇咬尾表示他有誘惑人的能力，所以需要分辨是真或假，而不是凴口說白話；這也表示永恒。花也表示他願意和人分享。我想愚人此時擁有了四种最基本的能力。

反牌

你會看見他失去各種支援，桌上的東西都掉下來了。通天地也好像變成顛倒是非了。

Veritas NetBackup - SAN switch migration activity

This post is to summarize the SAN switch migration activity I performed for Telekom Malaysia.

Some background information : TM has more than 150 media servers and running their master server in AIX environment. I involved in the netbackup portion when customr is actuallly perform the SAN switch migration for their ACS tape library which has 44 FC tape drives.

Tasks performed and the useful commands:
1) Gather the existing nbu information. De-activate policies and make sure no jobs are running.
2) freeze the Netbackup cluster group persistent.
    - haconf -makerw
    - hagrp -freeze -persistent
    - haconf -dump -makero
    - hastatus -sum
3) remove tape devices from master server.
    - nbemmcmd -deletealldevices -machinename -machinetype master
4) bring down netbackup services.
    - bp.kill_all
    - kill remaining nbu processes.
5) customer perform SAN switch migration
6) Perform AIX scan after SAN switch migration.
    - /usr/openv/volmgr/bin/scan (to check whether all drives serial number are detected)
    - found some drives are missing, after confirm the SAN zoning is done correctly. reboot the AIX server and re-run the cfgmgr again.
    - lsdev -Cc tape, /usr/openv/volmgr/bin/scan
    - other commands like: lscfg -vl , /usr/openv/volmgr/bin/scsi_command -d /dev/rmtxx -inquiry, odmget -q "/dev/rmtxx" CuAt, etc are also helpful to verify the drives.
7) verified the cluster is in partial status now. Unfreeze the cluster and bring up the netbackup service group.
   - you may hit "unable to initialize device mapping, status=1" error if running scan command. This is due to the virtual IP and netbackup services are not up.
8) Launch the NBU console and use the device configuration wizard to scan the robotic/drives for master server only.
9) Once master server have all drives configured in NBU. Then you proceed to use device configuration wizard to scan for other media servers too. But please run the nbemmcmd -deletealldevices in advanced.

Email archiving - how to deploy Symantec Enterprise Vault? Part 2

What's next after setup the SQL database and Vault service account?
Then you should start to check whether the Enterprise Vault is ready to be installed on the server. The easiest and faster way to check is to use the Enterprise Vault Deployment scanner.

Login the server using Vault service account. Browse into your EV software CD and access the folder called deployment scanner. Then just run the msi file inside to install. (Normally I install into D: drive) Once installed completed, Launch the deployment scanner and fill in the SQL server full name and the EV server name.
Rest assured, the deployment scanner will tell you what is lacking and you just try to fix them up until all necessary items are passed.

Common items that you need to fix
1) MSMQ location - use add or remove program to add this windows components (you will need i386 to install it). Check "application server" and then the IIS, ASP.net, and message queuing inside. (refer installation guide for detail how to do it). Once you install MSMQ, then right-click "My Computer" and select "Manage". Expand the tree and you see the icon called message queuing, right-click it and select properties. So you may change the location now to SAN disk and it will ask to reboot.
2) .NET - you require .NET 1.1 SP1 & .NET 2.0 SP1. Both are needed, Enable IIS first then install .NET. For E-Discovery deployment, you also need to install .NET 3.0.
3) Registry entries - you no need to fix it right now. you will able to fix it easily during installation.
4) IIS - Access the IIS manager and see the web extensions, you must see both .net 1.1 & .net 2.0 are allowed.
5) Exchange full admin rights - if you are doing Exchange archiving, most of time customer will forget to give you "receive as" & "send as" permissions. Grant the permissions in exchange server using system manager.

OK. to be continued...