Categories

Adverising

Blogroll

Sometimes it is difficult to uninstall software cleanly from add/remove programs. It doesn’t clean registry and leftover files/folders. This prevents from installing new software or work new program properly.

Shareware software, Revo is one good software to clean program and able to trace registry settings, files associated with program. Instead of manually cleaning registry settings, it is worth to try with 30 days free trial.

http://www.revouninstaller.com/

none

My case: I am planning to migrate old netbackup server (server1) to new server with the same host name (server1). My old server has 2 media servers,server1 and server2 which means it is connected to two media servers with two different tape loaders. When i am trying to backup catalog, i have no choice but to use server2 to backup just because server1 is using SDLT loader whereas server2 and new server are using LTO so that i will be able to recover catalog using LTO tape.

However, the problem is new server,server1 is trying to recover catalog from tape backup used by media server,server2. I did a hot catalog backup using tape. When I tried to restore using netbackup disaster recovery wizard, there is an error something like ‘unable to located /usr/……/../ from <server2>’ . Since server name is different, it is doubtful whether I am able to recover catalog using tape.

In order to restore catalog, here is what i have done.

1. Instead of hot catalog backup, i did offline(cold) catalog backup.

2. Instead of tapes, i used disk backup in offline catalog backup configuration. While doing that, there is an erorr 97, requested media id is in use which actually is catalog tape being assigned to use . So  i follow this link http://www.symantec.com/business/support/index?page=content&id=TECH35504 for solution. I expired catalog tape and configure offline backup to disk successfully.

3. I copied catalog files to new server, server1 , then use bprecovery command to recover catalog. Exact command i use is

bprecover -r -dpath g:\offlinecatalog.

Ensure not to have any space in folder name. I used g:\offline catalog which leads to invalid command.In fact, i forgot to stop following services as per symantec doc but it is still working.

NetBackup Service Monitor service

NetBackup Device Manager service

NetBackup Volume Manager service

To verify before recovery, the command bprecover -l -dpath g:\offlinecatalog can be used.

As for Unix, Linux, refer to symantec troubleshooting guide at

http://www.symantec.com/business/support/index?page=content&id=TECH52829  at page 566, the most important part of whole docs.

This method is very simple to recover catalog. No need to rely on the media to import catalog anymore.

 

 

none

when your drive is full with symantec database images, following steps will be helpful for you to move images from one drive to another to housekeep the drive.

Move only the individual client NetBackup catalog images to the new location.

1. Back up the NetBackup catalogs (see Backing Up the Catalogs Manually  on page 143 of the NetBackup DataCenter System Administrator’s Guide for UNIX).

This ensures that you can recover image information in case something is accidentally lost during the move.

 

2. Check the Jobs tab in the NetBackup Activity Monitor and ensure that no backups or restores are running for the client. If jobs are currently running, either wait for them to end or stop them by using the Jobs tab in the NetBackup Activity Monitor.

 

3. Use the Services tab in the NetBackup Activity Monitor to stop the NetBackup Request Manager and NetBackup Database Manager services. This prevents jobs from starting and the database from being modified while performing this procedure.

 

4. Create a file named ALTPATH (there should be no extension to this file)in the image catalog directory. For example, if NetBackup is installed in its default location and the client name is “mars,” the path to the image catalog is

C:\Program Files\VERITAS\NetBackup\db\images\mars\ALTPATH.

 

5. Create the directory to which you intend to move the image information. For example:

E:\NetBackup\alternate_db\images\mars

 

6. On the first line of the ALTPATH file, specify the path to the directory where you intend to move the client’s image information. For example:

E:\NetBackup\alternate_db\images\mars

This will be the only entry in the ALTPATH file.

 

7. Move all files and directories (except the ALTPATH file) that are in the current client directory to the new directory. For example:

If the images are currently in C:\Program Files\VERITAS\NetBackup\db\images\mars, and the ALTPATHfile specifies E:\NetBackup\alternate_db\images\mars, then move all files and directories (except theALTPATH file) to E:\NetBackup\alternate_db\images\mars.

 

8. Add the new image directory to the NetBackup catalog backup configuration (see “Files Tab”  on page 141 of the NetBackup DataCenter System Administrator’s Guide for UNIX). In the above example, you would addE:\NetBackup\alternate_db\images\mars.

CAUTION:  Failure to add the alternate image directory to the catalog-backup configuration can result in loss of backup data if there is a disk failure.

 

9. Start the NetBackup Request Manager and NetBackup Database Manager services by using the Servicestab in the NetBackup Activity Monitor. Backups and restores can now resume for the client.

 

 

none

The link will be as following

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

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

none

Behaviour: The backup failed with Unknown Error. In the backup log file, the error stated that AOFO: Unable to get minimum quiet time for physical volumes

Solution: Refer to the following link to resolve this issue

http://seer.support.veritas.com/docs/258341.htm

none

Behaviour: While running the backup, tape drive went offline. Though tape drive is brought back to online and run again, end up with backup error ‘Communication Stalled’

Solution: Go to devices -> Right click server name -> Paused and Un-paused the server to resolve the issue.

The following link can be used as reference but  as mentioned in the link,  I have never tried to install the hotfix to resolve this issue though.

http://seer.entsupport.symantec.com/docs/308627.htm

none

If there is a need to run symantec endpoint protection live update within SEP manager, just follow the below steps.

1. Go to Admin -> Servers -> click on Local Site

 2. In the tasks list, Download LiveUpdate Content

If there is any errors or live update doesn’t completed, uninstall liveupdate, reinstall live update and re-register with liveupdate will be able to resolve.

The following link will be able to guide on how to uninstall/reinstall liveupdate.

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007100907303548

none

Here is the quick solution to those who encountered this problem in vista and xp.  go to command prompt and type powercfg /hibernate on

so simple, right..

however, if there is an error about permission issue, just go to start->type command prompt in search box->right click on command prompt icon-> run as administrator and type the command again. It should work.

none

It can be seen that many people love to use mac book as some people love the design and some love the reliability of the Mac. Some people are interested to use Mac book but they just love windows OS as it seems to be more familiar to them. For those people, there are two options. Option 1 is to use dual boot, one for Mac and the other one for Window. This can be done by using BootCamp software (I will talk about this in another post). In this post, I will mention about the Option 2 which is clean installation windows on Mac. This can be used on Mac Mini, MacBook white, MacBook pro which were published in 2009 onwards.
First of all , you will need to have original Mac OSX DVD which comes along when you bought Mac book, Windows XP/Window Vista/Windows 7 installation CDs.
1. Place the Mac OS CD in your DVD drive. Then boot up from CD. To do this, you got to press key “C” while booting to boot directly from CD or “Option button” ( if using window keyboard, press “Alt” key), then graphical boot menu will be appeared for you to select CD.
2. Don’t install when Mac OS installation program open. Go to “Disk Utilities” from “Utilities Menu”. Select the Mac harddisk from the list on the left and select the Partition tab on the right. Click the Options button, then select “Master Boot Record”

3. Next, under the disk utilities partition tab, you can find the “Volume Scheme”. Since you are going to install only window, just select 1 partition. As for format, you can select MS-DOS Fat at this moment. When you install window, you can choose NTFS to format. Then click “Apply”

4. Restart computer. Press option key while rebooting. When boot menu appear, just press Disk eject. Take out Mac DVD , insert window DVD and install windows. Make sure not to forget to format with NTFS. After installing OS, continue install drivers using Mac OS X DVD as windows drivers can be found in Mac OS X installation CD.
Now you are ready to use your window in Mac. Ensure to backup your data before you try the above steps. It is working for my case.

none
Sometimes, we might encounter difficulty in starting Windows Vista after we have applied some crack/hack program that modifies the Windows Vista system to do something in operating system.

If we don’t know how to repair the boot loader, all we can do is to reinstall the whole Windows operating from the installation media. Sometimes, we can repair the boot error problem by booting from the Windows Vista installation DVD and then choose repair option in boot screen. We can try to repair Windows file system by selecting recovery from the Windows Vista boot screen then go to command prompt. In command prompt (console window), we can scan our hard disk that has Windows Vista by starting the command chkdsk. That check disk function can repair the Windows system error most of the times.

However, there might be cases even that disk check utility can’t fix the Windows boot error. I think that condition can happen if the Windows boot sector was altered by a certain program and forced to do some special startup commands. In the case in which Windows Vista boot loader was altered or modified, the problem might not be corrected even if we reinstall Windows Vista from installation media.

In such case or if we don’t want to reinstall the whole Windows system, we can try to restore the Windows Vista boot sector to default state. That function helped me many times to repair Windows Vista boot problems.

There is a small command line program called “bootsect.exe” in Windows Vista installation DVD. That small program is inside the BOOT folder of Windows Vista installation DVD. We can luckily use that small program to restore the Windows Vista boot sector to default state.

To invoke that program and to restore the Windows Vista boot sector, all we have to do is boot from the Windows Vista installation DVD. Then, select and open recovery console form the boot screen. (You can go to recovery console by clicking the links near the bottom of the Windows Vista first boot screen after you have booted from installation DVD).

You have to open the command prompt window to type the necessary command. Then, navigate to your Windows Vista installation DVD drive and then change the path of working folder to BOOT folder.

For example, if your DVD drive‘s letter is E:, navigate to E:\BOOT and then type the following command.

E:\boot\bootsect.exe /NT60 All

The boot sector restore program will work and you have to restart your PC after removing the installation DVD from the drive. The boot sector should be restored to normal (default) state and Windows should be able to boot normally.

This small program helped me for many times when I encountered boot problem with Windows Vista. I am not very sure this program can help you for every circumstances but I hope this information will help you anyway.

none

Most commented

  • None found