Thanks - but my question is, how does the database grow for archiving - does
it grow the same way as backups?
-----Original Message-----
From: Kleynerman, Arthur [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 13, 2000 9:29 AM
To: [EMAIL PROTECTED]
Subject: Re: Archiving and database growth
Terry,
I've had similar experience trying the "export node" command - only 1 node
can be exported to a single tape.
Arthur.
-----Original Message-----
From: Barth, Terry (MBS) [mailto:[EMAIL PROTECTED]]
Sent: Sunday, November 12, 2000 7:58 AM
To: [EMAIL PROTECTED]
Subject: Archiving and database growth
Hello fellow *SMrs:
I am beginning to implement the archiving feature, as the backupset just
wastes too much tape, as from what I have tested, only 1 node goes to 1
tape. <If I am wrong, please tell me>
Anyway, we have the need to store files for legal reasons for a large amount
of time - ex: 5 years, 7 years, etc. - Therefore, my only solution as to not
waste so many tapes, because I have 250 + servers that I am dealing with, I
was going to implement archiving.
Therefore, I was wondering if anyone knows the impact that archiving has on
the size of the database? I am concerned about the archiving feature
growing my database tremendously.
Thanks
Terry
