Video Screencast Help
Backup and Recovery Community Blog
Showing posts in English
Ajju | 04 Sep 2009 | 3 comments
Document                     Description
No
 
320378            BUG REPORT: Vault internal error 286
 
 
330305           ...
Zahid.Haseeb | 04 Sep 2009 | 1 comment

Today we discuss in this BLOG "Network Connection Timed Out(41)" in the Activity Monitor of Veritas Netbackup Server with the restore failed to recover the requested files(5)
In our case we have a environment of :

  • Windows2003 server
  • Veritas Netbackup 6.5.
  • MS SQL Server 2005

In this BLOG we will discuss:

  • Error which i have found
  • Resolution

Error which i have found

9/3/2009 2:09:05 PM - media 0010L4 required
9/3/2009 2:09:08 PM - restoring image dbserver-sec_1251836312
9/3/2009 2:09:16 PM - started process bptm (4200)
9/3/2009 2:09:16 PM - mounting 0010L4
9/3/2009 2:09:14 PM - requesting resource 0010L4
9/3/2009 2:09:14 PM - granted resource 0010L4
9/3/2009 2:09:14 PM - granted resource IBM.HHLTOGEN4.000
9/3/2009 2:09:20 PM - mounted; mount time: 00:00:04
9/3/2009 2:09:22 PM -...

J.H Is gone | 03 Sep 2009 | 0 comments

A recent discussion showed that some NetBackup users think that "ALL_LOCAL_DRIVES" can only be used for windows clients.
It can be use for unix as well.

All local drives will work on UNIX just like it does on windows.

On windows clients it seems obvious that all local drives will be drives like C: and E: and F:
But for people who do not know UNIX very well this seems to have no relation.

My example is going to be for an AIX server.

 

Filesystem    512-blocks     Free      %Used     Iused     %Iused     Mounted on

/dev/hd4      2097152     1489784      29%      4585        1%         /

/dev/hd2   ...

J.H Is gone | 03 Sep 2009 | 18 comments

Understanding how NetBackup writes to tapes and what happens when images expire will help you better manage your tapes.

Tapes are linear - meaning that they write from the front to the back.

if we look at a tape.
BOT|day1image|day2image|blankspace|EOT

now the day1image expires on the tape - the assigned date does not change and you have this.

BOT|expiredimage|day2image|blankspace|EOT

if you try to write to this tape again it will ONLY write in the blankspace as tapes are Linear - meaning they can only append (tapes cannot write here and there like a disk can)

Now day2image expires - the assigned date of the tape goes blank - no assigned date

-------

Now look at it with multiplexing.

you use the tape - it gets an assigned date.

BOT|server1part1|server2part1|server1part2|server2part2|blankspace

if the backup for server1 fails or if the backup image expires then you have this

BOT|expiredimage|...

Mark Garringer | 03 Sep 2009 | 1 comment

Our second meeting went very well. It was great to see returning faces as well as new faces at Adesa in Carmel!

19 people attended from 14 different orginizations around the Indianapolis area!

Phil Weingart gave a quick overview of the backup environment at Adesa, touching on design challenges and future projects. We also had two very successful breakout sessions discussing Disaster Recovery and VCB Implementation.

Our next meeting is scheduled for December 8th. Stay tuned for details on time and location!

Attached are the meeting minutes, a copy of Phil's presentation, a write up on Sallie Mae's VCB Implementation, and a VCB Proxy Installation slide show.

GFK | 28 Aug 2009 | 0 comments

I don't know if any of you have noticed but the first fiscal quarter of this year has been pretty bad for server sales. It doesn’t matter what the pundits say, however, it is important for all of us to save money, cut costs – but absolutely not at the expense of our backup.

 

Whatever else you gamble with, backup shouldn’t be one of them. IDC recently reported that server sales from January to March was the worst quarter in the dozen years that they have been releasing quarterly server figures. The current economic crisis has injected a disconcerting amount of uncertainty into the business climate. Organisations are loath to spend any more money than is absolutely necessary.

The silver lining here is that IT departments can use this opportunity to consolidate existing projects and focus on optimising existing backup systems . Backup Exec 12.5 and Backup Exec System Recovery 8.5 are built on complete protection and recovery providing...

GFK | 28 Aug 2009 | 3 comments

Backup Exec 12.5 released an Agent for Enterprise Vault, which is designed to offer complete protection for Enterprise Vault 7.5 implementations.  When Enterprise Vault 8.0 was released, architectural changes in EV 8.0 made the Backup Exec 12.5 Agent for Enterprise Vault unable to automatically protect all aspects of Enterprise Vault. An integrated solution will be in the next version of BE. In the meantime …

For customers who have not purchased the Agent for Enterprise Vault, and wish to protect Enterprise Vault manually with a combination of Backup Exec Agent for SQL Server and Agent for Windows Systems, refer to the following Tech Note:  http://seer.entsupport.symantec.com/docs/312327.htm

The Backup Exec 12.5 Agent for Enterprise Vault contains all of the building blocks necessary to protect Enterprise Vault 8.0.  Customers who have purchased the Agent for Enterprise Vault do...

HardikPatel | 27 Aug 2009 | 2 comments

hi
i am facing some problem in veritas netbackup 6.5.2
i have 3 servers which are configured as media server.
now one server with windows platform is not getting backed up from past 2 days
and giving error code 42 network read failed

i checked network settings and host files
ping test from host to server and vice versa.

and i checked some log and in bpdbm log file i found msg that is
db_valid_master_server: tcsc-ads.tcsckandla.com is not a valid server

plase provide help with this issue
i am new to veritas netbackup.

Thanx

bhupeshsingh | 26 Aug 2009 | 0 comments

Circular logging must be disabled if you want to do the following:

Run incremental and differential backups.

Recover data up to the point of failure.

Run continuous backups of Information Store transaction logs.

Put transaction log files on a separate physical disk from the database. If the disk that contains the database is damaged, the transaction logs are available as a recovery resource.

Set the retention period for deleted items and mailboxes to a length of time that is appropriate for the available disk space. The longer the retention period, the more disk space is required. However, some retention period can prevent you from having to restore a mailbox or database. If possible, configure the Exchange server so that items are not deleted until a full backup is performed.

Make Write Cache unavailable on the SCSI controller. Data corruption can occur if the computer fails before the operation is written to disk.

Monitor the...

OneManITShop | 19 Aug 2009 | 0 comments

I had to restore a file this morning using my B2D job. While I had no problems and everyone is happy I found it to be the perfect opportunity to go over my backup plan. It can’t hurt.

I backup 3 data types:
Email (Domino Server)
User data (aka files)
Active Directory

I’m using Backup Exec for all my backup jobs and most of the time I’m happy with the performance.

Domino backup is done using the Domino agent. Using this article as a reference I backup the Lotus\Domino\Data folder. Weekly cycle to tape with daily full backup to disk provide a strong backup. One important note that helps me keeping the backup in reasonable size is old users nsf files. When a user leave the company we still need to keep the mailbox (compliance, compliance, compliance) but it is not changing and there is no point in backing the same file every day. I have...