This is a multipart message in MIME format.
--=_alternative 0075C5C186256D7F_=
Content-Type: text/plain; charset="us-ascii"
I had to come up with some way to do this also. I am still working on a
final solution, but in the interim I have set up scripts that do an export
of the databases in off hours shortly before the backup runs. When the
backup runs, it backs up the export files and the content storage. Of
course with this scenario, there is a risk of some new content not being
in the metadata export. In the current environment here, it is not likely
that any new content would be added in the 20 minutes before the backups
run. I also do a full cold backup of the database and content storage
areas on the weekend.
I still need to look at using Oracle RMAN and Solaris fssnap or Veritas
snapshot (in Veritas Volume Manager software).
I was also told that Documentum has a built in utility for
copying/exporting the data (metadata and content) to a flat file. This is
apairantly what CYA has built onto the create their I have not researched
this yet.
Message: 8
Subject: RE: [Veritas-bu] Backing up Documentum DocBases
Date: Fri, 8 Aug 2003 16:01:10 -0700
From: "Kennedy, Jeffrey" <jkennedy AT qualcomm DOT com>
To: <markjessup AT northwesternmutual DOT com>,
<veritas-bu AT mailman.eng.auburn DOT edu>
I would be extremely interested to hear as well. The app admins here
are going to spend money on CYA, a Documentum specific backup software.
Not exactly an enterprise solution IMO.
~JK
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu [mailto:veritas-bu-
> admin AT mailman.eng.auburn DOT edu] On Behalf Of
> markjessup AT northwesternmutual DOT com
> Sent: Friday, August 08, 2003 11:44 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Backing up Documentum DocBases
>
> Just curious if others have experience backing up Documentum Docbases
> and if so, how do you do it and with what tools (Netbackup only).
> Documentum is a document management base which uses a docbase which
> consists of a standard database such as Oracle, SQL, or UDB which
holds
> metadata but then also has an associated storage area that holds all
of
> the documents. The content storage area could be a huge amount of
small
> files totally GBs or TBs of storage. The key is that when you backup
> this app, you need to backup both the database and the content at the
> same time to keep them in sync. So I am curious how people are doing
> this today. Are you using just Netbackup, Documentum specific tools
> such as CYA Hot Backup for Documentum, or hardware/software snapshots,
> etc. Any information you could provide would be greatly appreciated.
> Thanks!
>
>
>
> Mark Jessup
> IS Manager, Enterprise Storage and Output Management
> Northwestern Mutual
> (414) 665-3968
> markjessup AT northwesternmutual DOT com
>
Richard Mickle
UNIX Systems and Storage Administrator
Response Marketing Services
A Division of Moore Wallace North America, Inc.
E-Mail: Richard.Mickle AT rms.moorewallace DOT com
Phone: 920-339-1695
Cell Phone: 920-366-1987
Fax: 920-339-1807
--=_alternative 0075C5C186256D7F_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="Courier New">I had to come up with some way to do this
also. I am still working on a final solution, but in the interim I have
set up scripts that do an export of the databases in off hours shortly before
the backup runs. When the backup runs, it backs up the export files and
the content storage. Of course with this scenario, there is a risk of
some new content not being in the metadata export. In the current
environment here, it is not likely that any new content would be added in the
20 minutes before the backups run. I also do a full cold backup of the
database and content storage areas on the weekend.</font>
<br>
<br><font size=2 face="Courier New">I still need to look at using Oracle RMAN
and Solaris fssnap or Veritas snapshot (in Veritas Volume Manager software).
</font>
<br>
<br><font size=2 face="Courier New">I was also told that Documentum has a built
in utility for copying/exporting the data (metadata and content) to a flat
file. This is apairantly what CYA has built onto the create their I have
not researched this yet.</font>
<br>
<br><font size=2 face="Courier New">Message: 8<br>
Subject: RE: [Veritas-bu] Backing up Documentum DocBases<br>
Date: Fri, 8 Aug 2003 16:01:10 -0700<br>
From: "Kennedy, Jeffrey" <jkennedy AT qualcomm DOT com><br>
To: <markjessup AT northwesternmutual DOT com>, <veritas-bu AT
mailman.eng.auburn DOT edu><br>
<br>
I would be extremely interested to hear as well. The app admins here<br>
are going to spend money on CYA, a Documentum specific backup software.<br>
Not exactly an enterprise solution IMO.<br>
<br>
~JK<br>
<br>
> -----Original Message-----<br>
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-<br>
> admin AT mailman.eng.auburn DOT edu] On Behalf Of<br>
> markjessup AT northwesternmutual DOT com<br>
> Sent: Friday, August 08, 2003 11:44 AM<br>
> To: veritas-bu AT mailman.eng.auburn DOT edu<br>
> Subject: [Veritas-bu] Backing up Documentum DocBases<br>
> <br>
> Just curious if others have experience backing up Documentum Docbases<br>
> and if so, how do you do it and with what tools (Netbackup only).<br>
> Documentum is a document management base which uses a docbase which<br>
> consists of a standard database such as Oracle, SQL, or UDB which<br>
holds<br>
> metadata but then also has an associated storage area that holds all<br>
of<br>
> the documents. The content storage area could be a huge amount
of</font>
<br><font size=2 face="Courier New">small<br>
> files totally GBs or TBs of storage. The key is that when you
backup<br>
> this app, you need to backup both the database and the content at the<br>
> same time to keep them in sync. So I am curious how people are
doing<br>
> this today. Are you using just Netbackup, Documentum specific
tools<br>
> such as CYA Hot Backup for Documentum, or hardware/software snapshots,<br>
> etc. Any information you could provide would be greatly
appreciated.<br>
> Thanks!<br>
> <br>
> <br>
> <br>
> Mark Jessup<br>
> IS Manager, Enterprise Storage and Output Management<br>
> Northwestern Mutual<br>
> (414) 665-3968<br>
> markjessup AT northwesternmutual DOT com<br>
> </font><font size=2 face="sans-serif"><br>
<br>
Richard Mickle<br>
UNIX Systems and Storage Administrator<br>
Response Marketing Services<br>
A Division of Moore Wallace North America, Inc.<br>
E-Mail: Richard.Mickle AT rms.moorewallace DOT
com<br>
Phone: 920-339-1695<br>
Cell Phone: 920-366-1987<br>
Fax: 920-339-1807<br>
</font>
--=_alternative 0075C5C186256D7F_=--
|
