Search results for query: *

Does anyone use NB 5.1 MP2 on Win2003 yet? I'm currently using 5.0 MP1 and have to upgrade due to problems with Exchange mailbox backups on a Win2003 cluster. I'm just wondering if MP2 is any good. Tnx, Louis

Yep, the bpbkar log.

Hi, I wonder if it is possible to start a duplicating job which uses multiple storage units. This is the situation: - 1 Win2003 NB 5.0 Master/mediaserver with 1 storageunit containing 2 SDLT drives. - 1 Win2003 NB 5.0 Mediaserver with 1 storageunit containing 2 SDLT drives. Every day at 7:00...

With help of Veritas support I finnaly found the cause of this problem: NetBackup 5.0 has problems backingup some mailboxes which have been migrated from Exchange 5.5 to an Exchange 2003 cluster. This problem should be fixed in MP3. I identified the mailboxes that caused the problem by running...

The 41s only occur with mailbox backups of this specific mailcluster. I've found out it actually starts to backup a few mailboxes before failing on the same mailbox every time again. After excluding this specific mailbox it fails at another mailbox. The bpbkar32.exe process at the client stays...

Have you contacted Veritas Support yet? We also have problems with the mailboxbackup of our clustered Exchange 2003 server (exit status 41). Veritas support admitted a problem with the backup of Exchange clusters. They adviced us to install MP3 (currently NB 5.0 with MP1). This should fix the...

It appears that this problem was caused by 2 problems: 1) SCSI-ID (all Compaq SDLT drives default have SCSI-ID 6 and if a second SCSI-controller is added it also has ID 6) 2) According to Compaq an Array Controller has difficulties with SDLT drives. You should use a simple SCSI-controller instead.

Hi, We have a Win2003/Exchange2003 on a MS cluster (active passive) and a NetBackup 5.0 Master and Media server on Win2003. When we do an Exchange database backup it works fine, but when we try to do a mailbox backup the job fails with status 41 (connection timeout). I suspect the problem to be...

Hi, We currently have a Proliant DL380 G2 running Windows Server 2003 with the internal drives connected to the onboard Smart Array 5i SCSI Controller. To the external port of this controller we have a Compaq 100 GB SDLT drive in an external enclosure connected. This works fine. Now we want to...

Thanks for that suggestion. I'm curious why Veritas created the "Administrator's e-mail address" field when you can't use it in your scripts. At least it seems like you can't use it because I haven't been able to find how to use it in the documentation.

Hi, We recently started using NetBackup 5.0 for windows on Windows 2003 (previously used arcserve). I've installed Blat and edited the nbmail.cmd script and the dbbackup_notify.cmd to let me know which tape holds the most recent backup of the catalogdatabase. I also want to start using other...

We are currently implementing Netbackup 5.0 MP1 for Windows on a Windows 2003 and Exchange 2003 enviroment. A backup of Exchange (either mailboxes or informationstore)from a policy works fine, but when we try to do a user initiated backup from the "Backup, Archive and Restore" interface at the...

This solution you mentioned is for Exchange 5.5 with SP2. We are Running Exchange 5.5 with SP4. I looked in the registry anyway, but the "InBackupMode" key already had the value "0". So this didn't help. Thanks anyway. Yesterday I put the Exchange agent in debugmode level 1...

No, we did a while ago, but we turned it off. Even if it was on it shouldn't be a problem because we only make full backups of Exchange. Any other suggestions? Thnx, Louis

Hi, We have te same error when backing up Exchange 5.5 SP4 on a Win NT 4.0 SP6 server: E8604 Failed to start backup. (DBNAME=Information Store, EC=Backup Agent Error -- (305) "Exchange Server Error. HrBackupOpenFile failed. Check Backup Agent Activity Log".) We use ArcServe 2000...

Dit you reboot your server after installing BAOF? I had similar problems on an NT 4 server with DHCP and Wins. Both databases stil failed to backup because they were open. After a reboot those files are no longer a problem.

Did you reboot your server after installing the open file agent? If not, do so first! Else try to lower the "write inactivity period" on your open file agent's configuration.