When C drive is full with antivirus cache,you may be wondering if it is possible to move to D drive or other available drives . The solution is No. It is not possible to move cache file even if you uninstall/ reinstall antivirus. It will still be in C drive. If system resources are insufficient, there is nothing much you can do except from upgrading system.

As interim solution, you may be able to housekeep some folders from following locations.

1. You can clear the folders from

C:\Program Files\Common Files\Symantec Shared\VirusDefs but leave the latest definition folders.

2. Delete all files/folders from

C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads

As windows used 32bit block numbers lowest storage stack, this actually limit to support single storage drives (LUNs) using hardware raid not having more than 2TB.  In order to have logical disk more than 2TB, disk format must convert from MBR (Master boot record) to GPT (GUID partition tables) to be usable.

How to convert from MBR to GPT

1. download diskpart

2. use diskpart command. Open command prompt-> type diskpart

3. at diskpart prompt, type list disk.

4. at the diskpart prompt, type select disk <disk number>

5. at the diskpart prompt, type clean. Clean command will delete partitions and volumns on the disk

6. then type convert gpt

references:

If you encounter end marker unreadable in symantec backup exec, follow symantec link as below.

http://www.symantec.com/business/support/index?page=content&id=TECH50884

This helps to resolve my issue

System states access rights issued can be resolved by following below steps. This is to bypass the authentication on master and media servers.

1. Locate HKEY_LOCAL_MACHINE\Software\Symantec\Backup Exec for Windows\backup Exec\Engine\NTFS

2. Risht click -> New DWORD Value -> Type useAdSSCheck as value name.

3. Ensure value must be 0.

4. Restart netbackup services on both master and media servers.

Symantec tech note should be followed as below

http://www.symantec.com/business/support/index?page=content&id=TECH36571

Adding unix clients to netbackup seems very simple but you will be frustrated when you are unable to add clients and no error is prompted.

Solution to resolve this is to create a job first. When you create a job using a wizard and asked for the client server name, you can either browse or key in client server name (if client name is not in the network, keyin as per host file on your system – drivers/etc/hosts. It should be the same as hosts).

Then go to host properties-> clients on veritas. Client name should be appeared there. Try to connect and see if there is any error. If there is any erorr such as error code 46 relating to access authenticated problem, you have to check host name in your client system. In solaris, default installation path of veritas is

/usr/openv/netbackup/bp.conf

view bp.conf and check the server name. It should be the same name as you placed under etc/hosts.

This is very simple but i have wasted few hours trying to figure out why veritas can’t add clients.

a waste of your time to figure out what actually happened.

When you download netbackup 7.1 from symantec, you probably encounter same issue as i were. I received an error as mentioned in title after i download NetBackup_7.1_Win_zip.1of2 and NetBackup_7.1_Win_zip.2of2 from symantec. It is beacause those 2 files need to me merged before you can extract. Do not try to change the file extention to .zip.  Instead run the following command.

- On UNIX systems:
cat “NetBackup_7.1_Win_zip.1of2″ “NetBackup_7.1_Win_zip.2of2″ > “NetBackup_7.1_Win.zip”

- On Windows systems:
copy /b “NetBackup_7.1_Win_zip.1of2″+”NetBackup_7.1_Win_zip.2of2″ “NetBackup_7.1_Win.zip”

That will merge into valid zip file.

The above sql patch is failed to update while doing monthly maintenance. When I open the log from C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB070895_sqlrun_sql.msp.log there is error as below.

“SQL Server Setup cannot upgrade the specified instance because the
previous upgrade did not complete. Start the Remote Registry service and go to Add/Remove
Programs, select the Change button for Microsoft SQL Server 2005, and then select SQL
instance [2] and complete the setup.”

As per instruction, I tried to follow from add/remove program and lead to another problem when I tried half way through. There is an error box prompted to look for sqlrun_sql.msi which is unable to find from system drive and prompted to insert CD.

Solution to  solve this problem,follow below instruction posted from the forum, http://social.msdn.microsoft.com/forums/en-US/sqlsetupandupgrade/thread/73bbe749-2cfc-4d2e-a48c-a084a52b8801/

I have tried more than twice in order to work. So if you run into any problem while trying, just reboot the server and tried again the same step.

1. Go to Add/Remove Programs, select the Change button for Microsoft SQL Server 2005, and then select SQL instance and complete the setup. Keep the dialog for SqlRun_SQL.msi open.

2. Download SQLEXPR.EXE from http://www.microsoft.com/downloads/details.aspx?familyid=31711D5D-725C-4AFA-9D65-E4465CDFF1E7&displaylang=en

3. Run SQLEXPR.EXE and leave the dialog about another instance open.

4. Point the first dialog for SqlRun_SQL.msi to the new folder that SQLEXPR.EXE created.

5. Let the installer finish and restart the computer.

Error is detected when installing window 2003 Sp2.

The resolution for this problem is as stated in below link.

Read the rest of this entry…

If you changed hostname of  vcenter update manager, you are required to change hostname in configuration file to make it work. Otherwise, connection to the hostname will be having a problem. In order to change the config file, refer to the following link.

http://aaronwalrath.wordpress.com/2009/07/02/fixing-vmware-update-manager-after-changing-vcenter-server-ip-address/