corrupt Outlook.ost file??

[Brad Pears]

I am using a Veritas Backup Exec (9.1) remote agent to backup my XP
workstation nightly. The backup fails each night due to the fact that it
cannot verify the Outlook.ost file. It says that the file is corrupt...

What exactly is this file used for and should I be concerned? My Outlook
client seems to be running fine.

Thanks,

Brad

 

[Lanwench [MVP - Exchange]]

I am using a Veritas Backup Exec (9.1) remote agent to backup my XP
workstation nightly. The backup fails each night due to the fact that
it cannot verify the Outlook.ost file. It says that the file is
corrupt...

What exactly is this file used for and should I be concerned? My
Outlook client seems to be running fine.

Thanks,

Brad

This is the offline copy of your Exchange mailbox, stored locally on your
computer. This tells me you have Exchange server...generally, OST files
aren't used on desktops on LANs; they're used on laptops or home/remote
computers to give access to the mailbox, GAL, public folders, while not
connected to the server.

If you connect to Exchange, you need to be doing online backups of the
Exchange databases using the BE Exchange agent.

I really have to ask, why are you doing workstation backups, anyway? On a
domain, you should be storing everything on the server(s), and using roaming
profiles in Windows. That way, workstation backups are not necessary - and
workstations can be treated as interchangeable objects.

I don't run workstation backups and so I don't know why you're getting this
error, but since you probably don't need an OST file anyway, it may not be a
big deal - and you wouldn't want to back it up, since it means you'd be
backing up your Exchange mailbox twice to tape (presuming your server
backups are set up properly).

 

[Roady [MVP]]

The ost-file is an offline copy of your Exchange mailbox so you can view
your mail even when disconnected from the Exchange server. It probably fails
because you've got your Outlook still running during the backup. Since it's
only an offline copy of your Exchange mailbox (which most likely gets backed
up on the Exchange server) you can choose not to backup this file.

--
Robert Sparnaaij [MVP-Outlook]
www.howto-outlook.com

Tips of the month:
-What do the Outlook Icons Mean?
-Create an Office 2003 CD slipstreamed with Service Pack 1

 

[Brian Tillman]

I am using a Veritas Backup Exec (9.1) remote agent to backup my XP
workstation nightly. The backup fails each night due to the fact that
it cannot verify the Outlook.ost file. It says that the file is
corrupt...

If you leave your Outlook running, then it's not a surprise your backup
software is complaining. Outlook opens it PSTs and OSTs for its own
exclusive use and backup programs will not be able to make proper backups of
them as long as they are open. If you want backups of Outlook data that you
know you'll be able to restore in the event of a problem, then Outlook must
be closed when the backup runs.

 

[Brad Pears]

I am only backing up my workstation because I have a bunch of data on there
I just don;t want to lose. I do copy stuff over to the server but I also
have a lot of configuration settings on my PC that if I were to have a
problem would be a pain to reconfigure etc... Since we now have an extra
tape drive sitting in my Exchange box doing nothing after purchasing a Dell
autoloader for the backups, I figured I may as well put it to use!

Thanks for the info...


"Lanwench [MVP - Exchange]"

 

[Brad Pears]

Thanks for the responses guys!

 

[Lanwench [MVP - Exchange]]

I am only backing up my workstation because I have a bunch of data on
there I just don;t want to lose.

You really should consider storing *all* your data on the server - by
default, all users should. This presumes your server is in good running
condition & is maintained well, and backed up nightly. You can use folder
redirection via group policy to point My Documents at a subfolder of the
users' home directories to make this easier.

I do copy stuff over to the server
but I also have a lot of configuration settings on my PC that if I
were to have a problem would be a pain to reconfigure etc.

Roaming profiles....they follow you around wherever you log in, presuming
your workstations have the same OS version & your app load is fairly
consistent.

Since
we now have an extra tape drive sitting in my Exchange box doing
nothing after purchasing a Dell autoloader for the backups, I figured
I may as well put it to use!

Why not install it locally, then? & use NTBackup to do a local backup of
your workstation to tape, if you really want to do workstation backups at
all.

Thanks for the info...


"Lanwench [MVP - Exchange]"

This is the offline copy of your Exchange mailbox, stored locally on
your computer. This tells me you have Exchange server...generally,
OST files aren't used on desktops on LANs; they're used on laptops
or home/remote computers to give access to the mailbox, GAL, public
folders, while not connected to the server.

If you connect to Exchange, you need to be doing online backups of
the Exchange databases using the BE Exchange agent.

I really have to ask, why are you doing workstation backups, anyway?
On a domain, you should be storing everything on the server(s), and
using roaming profiles in Windows. That way, workstation backups are
not necessary - and workstations can be treated as interchangeable
objects.

I don't run workstation backups and so I don't know why you're
getting this error, but since you probably don't need an OST file
anyway, it may not be a big deal - and you wouldn't want to back it
up, since it means you'd be backing up your Exchange mailbox twice
to tape (presuming your server backups are set up properly).

 

[Brad Pears]

Yes, installing local is something I thought about before and will likely do
eventually. Just haven't got around to it yet...

We currently are only using roaming profiles for our terminal server users.
We have a mix of XP and Win98 machines.

I am already redirecting the My Documents folder for term server users - but
the GPO is a little screwy and only some users are having this happen... AN
issue I have to sort out that has been casuing me grief...

Once we have replaced the Win98 machines - which is a plan down the road,
then I will be able to apply a policy to all workstations and use folder
redirection, roaming profiles etc...

Brad

"Lanwench [MVP - Exchange]"

I am only backing up my workstation because I have a bunch of data on
there I just don;t want to lose.

You really should consider storing *all* your data on the server - by
default, all users should. This presumes your server is in good running
condition & is maintained well, and backed up nightly. You can use folder
redirection via group policy to point My Documents at a subfolder of the
users' home directories to make this easier.

I do copy stuff over to the server
but I also have a lot of configuration settings on my PC that if I
were to have a problem would be a pain to reconfigure etc.

Roaming profiles....they follow you around wherever you log in, presuming
your workstations have the same OS version & your app load is fairly
consistent.

Since
we now have an extra tape drive sitting in my Exchange box doing
nothing after purchasing a Dell autoloader for the backups, I figured
I may as well put it to use!

Why not install it locally, then? & use NTBackup to do a local backup of
your workstation to tape, if you really want to do workstation backups at
all.

Thanks for the info...


"Lanwench [MVP - Exchange]"

Brad Pears wrote:
I am using a Veritas Backup Exec (9.1) remote agent to backup my XP
workstation nightly. The backup fails each night due to the fact
that it cannot verify the Outlook.ost file. It says that the file is
corrupt...

What exactly is this file used for and should I be concerned? My
Outlook client seems to be running fine.

Thanks,

Brad

This is the offline copy of your Exchange mailbox, stored locally on
your computer. This tells me you have Exchange server...generally,
OST files aren't used on desktops on LANs; they're used on laptops
or home/remote computers to give access to the mailbox, GAL, public
folders, while not connected to the server.

If you connect to Exchange, you need to be doing online backups of
the Exchange databases using the BE Exchange agent.

I really have to ask, why are you doing workstation backups, anyway?
On a domain, you should be storing everything on the server(s), and
using roaming profiles in Windows. That way, workstation backups are
not necessary - and workstations can be treated as interchangeable
objects.

I don't run workstation backups and so I don't know why you're
getting this error, but since you probably don't need an OST file
anyway, it may not be a big deal - and you wouldn't want to back it
up, since it means you'd be backing up your Exchange mailbox twice
to tape (presuming your server backups are set up properly).