Video Screencast Help
Backup and Recovery Community Blog
Showing posts in English
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...

Zahid.Haseeb | 14 Jul 2009 | 3 comments

Today we will discuss in this blog how can we copy backup images from one media to different. Suppose we have had backup image of some data on a SAN drive and we want it to have at different SAN drive DSU/volume pool.

In this blog we imagine that we have backup image on DSU1 and we will make a copy of this backup image in to DSU2.
First confirm from the catalog that you have had backup image which you want to have on another DSU(DSU2) as well.

Suppose that the backup image is present as the below example snap is showing
imagebrowser image

Now select the duplicate from the Action menu and click on search as the below snap showing
imagebrowser image

Now right click on the backup image and click on duplicate
...

| 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...

| 08 Jul 2009 | 1 comment

Solution

you can switch to install mode while lusers are on the server. However I would recommend that you disable log on for new users till you installed the stuff:

Please use the following command before you start with the remote agent installation.

change logon /disable
change user /install

Install software

change user /execute
change logon /enable

Please let me know if you have any other resolutions for the same.

RahulG | 07 Jul 2009 | 0 comments

This is by design and not a problem. Hardware compression and Hardware Encryption can be used for NDMP backups of Filers if the tape device supports the same.

If you perform an NDMP backup of Filer with Software Compression the job would complete successfully however the job lob won’t report any software compression ratio. This is due to the fact that the compression was not performed.

If you perform an NDMP backup of Filer with Software Encryption the job would fail with following error:

Final error: 0xe0000f1f - Software encryption is not supported for one or more of the selected resources. Check the job log for more information.

V-79-57344-3871 - Software encryption is not supported for one or more of the selected resources. Check the job log for more information. Check the job log for more information.

Again this is normal since it is not supported.

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...

RahulG | 07 Jul 2009 | 1 comment

Mailboxes for the user's deleted from the active directory do not show up in the restore selections when the data is backed up to a tape.

Details: This behavior is by design.

Explanation : When Running the GRT backup to tape , the exchange data is backed up in the native format ,along with the ese.dll and other supporting files,Later the MAPI is initialize on the exchange server by RAWS (Remote agent for Windows Server) to gather granular restore information .MAPI gathers the exchange data using Active directory and then writes to the catalog. As MAPI cannot retrieve the information about the deleted user from the Active directory the catalog information for the user is not written to the catalog. this is not a problem with restore selection from backup to disk folder due to the Dynamic way we can read the exchange DB using the VFF technology

Workaround : Duplicate the backup set from tape...

GFK | 03 Jul 2009 | 0 comments

I know I keep banging on about this but it really does bother me that we are not adequately protecting Active Directory (AD) as the primary directory service in Windows. Microsoft Exchange, SQL, and SharePoint all depend on efficient backup and quick recovery of AD. So if you have any of these business applications you should be thinking about how you backup, and more to the point, restore AD. We all know that AD data has a bad habit of corruption which can have a disastrous affect across the Windows environment.

AD objects can get modified or deleted by mistake, faulty scripts accidentally overwrite key AD attributes. Since it is a replicated database an accidentally deleted user account can result in a lengthy process while someone struggles to recover the AD environment. Ultimately, we can end up at the mercy of AD. Anyone who has ever had to recover AD understands the frustration and time involved with what should be a basic recovery process – but isn’t....