Thanks for the info.  We had many calls in to support at the time, and did
move the PI to a filespace on the ADSM server.  However we still experienced
startup delays, and it still seemed to want to mount the old PI tape.  We
tried a variety of things, with help from support, but when we lost all the
backups it was pretty much the last straw.  We do have Exchange servers
elsewhere on campus that are using Backup Exec for their databases and are
happy with it.  But they are not using ADSM as the output device.

> -----Original Message-----
> From: Freddy Sjauw-En-Wa [SMTP:FreddyS AT NSMG.SEAGATESOFTWARE DOT COM]
> Sent: Wednesday, July 07, 1999 8:33 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: ADSM ,Backupexec and Exchange
> Importance:   High
>
> Debbie et al,
>
> I am sorry to hear that you had negative experiences with our ADSM
> implementation. There are a number of variables that need to be in place
> for
> it all to work. Did you call upon our support people to help you resolve
> the
> issue?
>
> The way our implementation works is to use the API client to port data
> from
> BE (Backup Exec) to ADSM. BE sees the entire ADSM system as one virtual
> Autoloader. The data stream is forked into user data and control data
> before
> sending it to ADSM.  We always advise customers to keep the control data
> (PI data) on a disk based pool. This way access, positioning etc of the
> 'virtual tape' is fast and there are no timing issues with BE. The user
> data
> (VT data) can be written either directly to tape or overspill to tape from
> a
> disk pool. (Personally I prefer the overspill config. since ADSM does not
> need to mount a tape -locate, get, mount, position- and thus will eat all
> data at that time like candy).
>
> We did encounter unpredictable events/behaviour when PI data was written
> to
> tape. This is the position data that would normally live at the beginning
> of
> a tape (cat, header, mounts etc). Similarly one would also get
> unpredictable
> behaviour if the header data was in any way shape or form incorrect on a
> normal tape.
>
>
> I hope this explains our implementation a bit.
>
>
> Regards,
>
> Freddy Sjauw-En-Wa, B.Sc., B.Eng.
> -Homo Bonae Voluntatis-
> VERITAS  support
>
>
>
> -----Original Message-----
> From: Weeks, Debbie [mailto:debbie AT ADMIN.USF DOT EDU]
> Sent: 07 July 1999 12:20
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ADSM ,Backupexec and Exchange
>
>
> We had tried this configuration initially, and had a lot of problems with
> it.  ADSM was defined as an output device to Backup Exec.  We had a lot of
> unexplained delays in startups of scheduled backups, and then problems
> with
> the Backup Exec catalog caused us to lose about 6 months worth of backups.
> They may have improved in subsequent versions, but we are not willing to
> invest the time to find out.
>
> I wouldn't want to go this route again, but of course we have no interest
> in
> doing individual mailbox backup/restore.  It is too slow, our backup
> window
> would not allow for anything but a selective backup of individual
> mailboxes,
> and we would probably never have selected the one we would need to
> restore.
> We can restore a 6-7 gig Exchange database, and recover a mailbox, within
> about an hour (when it goes well), and that is good enough for us.
>
> > -----Original Message-----
> > From: malkit [SMTP:malkit AT UDI.CO DOT IL]
> > Sent: Wednesday, July 07, 1999 7:55 AM
> > To:   ADSM-L AT VM.MARIST DOT EDU
> > Subject:      ADSM ,Backupexec and Exchange
> >
> > Hello
> >
> > I read somewhere , and I can't find it anymore, about ADSM and
> > backupexec integration through ADSM API.
> > Since backupexec can restore exchange single mailbox I was wondering if
> > any of you implement ADSM and Backupexec to work together.
> > If so, do you have any recommendation for the implementation ? Do you
> > recommend to work with this method ?
> > --
> > Regards
> >
> > Malkit Hayun , UDI
> > Storage Products Manager
> > IBM Certified Specialist-ADSM
> > Office: 972-3-9233440
> > Fax:    972-3-9233441
> > Mobile: 972-52-834575
> > Email: malkit AT udi.co DOT il