|
OK, I think I got it.
He would definitely need to do lots of scenario testing before replacing his current method of using Windows for IFS document storage.
Especially due to the object permissions and backup/recovery potential issues.
I still vote for leaving the IFS objects on the Windows server being backed up with backup exec, however it's not my shop.
FWIW: One way to speed up overall small file backup on a Windows server as well is to create a Virtual Hard Drive (VHD) similar to the iASP.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Wed, 26 Sep 2018 13:41:25 -0500
from: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
subject: RE: Large volume file move
It would be one object, however as I pointed out the advantage of backing
that up as one object is all but eliminated with Asynchronous Bring.
The other disadvantage would be in order to back up the UDFS, you would have
to bring down the iASP for the duration of the save. Not terribly useful.
I addressed speed of backup in an earlier post where you get a primary
backup, then only add incremental backups of new objects appended to the
same tape.
On a monthly or quarterly basis resave the entire iASP and start over to
maintain audit controls .
--
Jim Oberholtzer
Agile Technology Architects
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.