Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog
Showing posts tagged with Tip/How to
Showing posts in English
ebodykid | 30 Jul 2009 | 2 comments

Just wanted to give everyone a heads up, so that they don't run into the same nightmare as i did when upgrading from 6.5.3 to 6.5.4.. I had a fun 30 hour day getting bounced around the world with support only to go back to my initial suggestion of reverting to a catalog backup. With the addition of the db_marker.txt file and the behavior of the sun patchadd it can cause a nightmare if you are symlinking your db/images to another location..

the following applies if you are installing the upgrade using the patches provided by Sun..

If the following conditions are true, people need to take extra care when performing the upgrade using the Sun patches
• You are symlink’ing <install location>/openv/netbackup/db/images to another location
• And/or you are symlink’ing <install location>/openv/db/staging to another location
• you are upgrading by using the Sun Netbackup 6.5.4 patches (ie 127655-04)

If these are...

Stuart Green | 29 Jul 2009 | 6 comments

Now and again Symantec release a technote with a flash tutorial including narration/steps taken, rather than screen grabs. Here's links to all of them to help managing NetBackup.

• Device Management / Configuration
How to upgrade tape drive firmware
How to run the Veritas NetBackup (tm) 6.0 Automated Robot Diagnostics Utility
How to create and configure a Disk Storage Unit with Veritas NetBackup (tm) 6.0

• Logging
How to view unified logs for a specific JobID in Veritas NetBackup (tm) 6.x
How to enable and configure robust logging in Veritas NetBackup (tm) 6.0
...

Mouse | 22 Jul 2009 | 10 comments

I was really shocked when I learned that EMC Documentum (Content Management solution) does not allow you to put itself into "online backup mode".

As we used Documentum with an Oracle database, and your content storage and DB should be backed up at the same time to ensure the consistency.

But the problem of implementaion of "hot backup" is obvious: we have to freeze the DB with metadata prior to backup of the filesystem. So what is the solution?

The key is here: perform regular Oracle hot backup and start fs backup from a notification script. This can lead to discrepancies between your content storage and metadata, but your Documentum admin will be able to delete all unnecessary files which were appeared after the DB backup.

Shrikumar | 20 Jul 2009 | 0 comments

Hi,

I am getting CC41 error from one of my client machine whenever using a particular interface at the same time I am able to ping that interface telnt that interface and tried so many network troubleshooting.

But when using other interface the backups are getting completed sucessfully

Please help me to solve this issue.

Regards,
Shrikumar

RahulG | 20 Jul 2009 | 1 comment

The Backup Exec Command Line Applet is a convenient way to access some of the most useful features of Backup Exec from a command prompt.

The Command Line Applet allows management of only one media server at a time, but allows for remote management of media servers within an enterprise. However, if the Central Admin Server Option (CASO) is installed, you can administer all servers managed by the central administration server.

Backup Exec must be installed and running on a media server in order for the Command Line Applet to target it, but the Command Line Applet does not have to be run from a media server. The Command Line Applet uses functional command switches typed in a command prompt window to perform most Backup Exec functions and utilities.

Note: Backup Exec Command Line Applet is only backwards compatible for a previous release and dot releases of the same version of Backup Exec.

The Command Line Applet displays job statuses as numeric values....

Zahid.Haseeb | 15 Jul 2009 | 0 comments

How can we replace the backup image position from secondary to primary

Note:- Why we need to do this?
One main reason can be, the primary image keeping place damage/corrupted/crashed

How can we achieve this? Because by default the backup restores from the first/primary copy

Few days before i got stuck in a issue. Basically i have Netbackup Server 6.5 with win2003 server. i was taking SQL 2005 backup successfully. At the Netbackup Agent-->Netbackup SQL Agent we browse the backups and also make the SQL restore script for restore without any problem.
i am taking multiple copies of backups. My primary copy of backup is going on Tape and secondary backup is going on SAN drive.

Procedure
By default when we browse the backups from Netbackup Agent-->Netbackup SQL Agent it shows the 1st copy/primary copy of backup from the storage which we select as the first storage in the policy. as shown in the figure...

| 09 Jul 2009 | 4 comments

When using the Backup Exec MSVS agent  to backup the Hyper-V virtual images it will backup the complete hard drive and not the actual data on the drive. I mean if you have created a VHD of 100 GB and have only 30 GB used, when we backup it the VHD it will backup complete 100GB and not 30 GB this is because Unlike VMware, MS doesnot provide any utilty like VCB which inturn compress the data and lets the Backup Exec backup the only data and not the free space.

hence when backing up Hyper-V images it will backup the complete VHD though you donnot have that much data on the drive.....

Let me know if some has any other answer to this question.

| 09 Jul 2009 | 1 comment

Hello,

VCB is Vmware consolidated backup a utility from which allows backup applications to take online snapshots of running Linux and Windows Guest virtual machines hosted on VMware ESX or ESXi servers. VCB then allows those snapshots to be moved to a separate system known as a “VCB Proxy Server” to be backed up “off-host” from the ESX host server by a backup application, such as Backup Exec 12.5, without impacting the ESX host server and all of its Guest virtual machines during a backup

AVVI agent doesnot include the VCB, you cannot use the AVVI agent without VCB as that is utility which will all the backup software to take the snapshot of the VM's

If u have a VM ware server that should not cost u . u can download it using the link http://www.vmware.com/download/vi/drivers_tools.html

...

RahulG | 09 Jul 2009 | 7 comments

Would like to share the SQL command that helped in deleting the computer name from DLO console stuck in "Delete pending" state.

The Cause of this is most likely to be the change in HostName of a Workstation.

NOTE: Use BEUTILITY to DUMP "backup" the DLO database. Copy saved database X:\program files\Symantec\backup exec\data\BE_DLO.BAK to a safe location.

The delete machine script deletes by MachineID so the first thing we have to do is find out the Machine ID.

NOTE: Clean installs of Backup Exec 11 and 12 will use the BKUPEXEC instance for both the BE database and the DLO database. Upgrades from previous versions will have separate instances and the DLO instance maybe BKUPEXECDLO. Verify the instance name is correct before running the commands below.

From a CMD prompt type the following:

osql -E -S %COMPUTERNAME%\ bkupexec -d BE_DLO

1> select MSID from MachineSettings where MSName = 'ComputerName'

2...

RahulG | 07 Jul 2009 | 0 comments

SunOS is the core operating system comprising the kernel, utilities and basic libraries. Solaris is the broader environment comprising SunOS, OpenWindows and networking support. In other words, SunOS is a component of Solaris.
SunOS and Solaris relate to each other as follows:
For example, when one does a 'uname -a' or ‘uname –r’ this reports that the server has SunOS 5.6 installed which means that it actually got Solaris 2.6 installed which is a bit confusing and not as complete. If you're not into Solaris, it's easy to get confused by the fact that (for example) there's more than one version of Solaris 8, and it's also called Solaris 5.8 and even SunOS 5.8.
The following example shows the output for ‘uname’ command output:
#uname -r
5.6
We can also use more /etc/release to find out the Solaris version.
#cat /proc/version
In addition, we can also run the command ‘showrev’. There's a man page...