This is a multipart message in MIME format.
--=_alternative 00556A9686257092_=
Content-Type: text/plain; charset="US-ASCII"
Thanks for the tip.
The filename and path i posted wasn't the actual file name and path on the
disk.
I gottsa keep some things secret ;)
The file is located outside of the database directory. We don't have hot
backups working with our progress db's. So we shutdown the db, copy the
db's to a copy directory, start up the db's and exclude the original db
directory.
I'll probably change that to filesystem snapshots on solaris 10 or SAN
based snapshot shortly. The shutdown, db copy and db startup takes a
while. That time can better be used netbackup'ing stuff up instead.
We may try to get hot backups working with progress too.
Karl
veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on 10/06/2005 10:24:06 AM:
> On Thu, Oct 06, 2005 at 10:13:21AM -0500, Karl.Rossing AT Federated DOT CA
wrote:
> > So i should backup the file again.
> >
> > Is there a way to backup the file via the command line on the client
so i
> > don't have to rerun the entire policy?
>
> The reason you got the error in the first place, we think, is that the
> database was not in hot backup mode. In this case, it's not just this
> file that will cause you problems - your entire database backup is
> suspect and should be rerun *AFTER* it's put into hot backup mode.
> If you back up just the single file, your database is very likely not
> restorable.
>
> .../Ed
>
> --
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts AT ewilts DOT org
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
--=_alternative 00556A9686257092_=
Content-Type: text/html; charset="US-ASCII"
<br><font size=2 face="sans-serif">Thanks for the tip.</font>
<br>
<br><font size=2 face="sans-serif">The filename and path i posted wasn't
the actual file name and path on the disk.</font>
<br>
<br><font size=2 face="sans-serif">I gottsa keep some things secret
;)</font>
<br>
<br><font size=2 face="sans-serif">The file is located outside of the database
directory. We don't have hot backups working with our progress db's. So
we shutdown the db, copy the db's to a copy directory, start up the db's
and exclude the original db directory.</font>
<br>
<br><font size=2 face="sans-serif">I'll probably change that to filesystem
snapshots on solaris 10 or SAN based snapshot shortly. The shutdown, db
copy and db startup takes a while. That time can better be used netbackup'ing
stuff up instead.</font>
<br>
<br><font size=2 face="sans-serif">We may try to get hot backups working
with progress too.</font>
<br>
<br><font size=2 face="sans-serif">Karl<br>
</font>
<br>
<br><font size=2><tt>veritas-bu-admin AT mailman.eng.auburn DOT edu wrote on
10/06/2005
10:24:06 AM:<br>
<br>
> On Thu, Oct 06, 2005 at 10:13:21AM -0500, Karl.Rossing AT Federated DOT CA
wrote:<br>
> > So i should backup the file again.<br>
> > <br>
> > Is there a way to backup the file via the command line on the
client so i <br>
> > don't have to rerun the entire policy?<br>
> <br>
> The reason you got the error in the first place, we think, is that
the<br>
> database was not in hot backup mode. In this case, it's not
just this<br>
> file that will cause you problems - your entire database backup is<br>
> suspect and should be rerun *AFTER* it's put into hot backup mode.<br>
> If you back up just the single file, your database is very likely
not<br>
> restorable.<br>
> <br>
> .../Ed<br>
> <br>
> -- <br>
> Ed Wilts, Mounds View, MN, USA<br>
> mailto:ewilts AT ewilts DOT org<br>
> _______________________________________________<br>
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT
edu<br>
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
> <br>
> <br>
> <br>
</tt></font>
--=_alternative 00556A9686257092_=--
|
