Author: "Browning, David" <DBrown AT LSUHSC DOT EDU>
Date: Wed, 25 Jul 2007 10:50:02 -0500
I've been dealing with Networker for more than 9 years now, but have never had to deal with clone issues. With the recent addition of storage nodes and dedicated storage nodes, we now have the time t
Author: "Werth, Dave" <dave.werth AT GARMIN DOT COM>
Date: Wed, 25 Jul 2007 09:42:17 -0700
We've been running automatic cloning for a number of years and in my experience the few times I've done manual cloning the run times are similar to the automatic cloning. But all of the cloning is ta
Author: Curtis Preston <cpreston AT GLASSHOUSE DOT COM>
Date: Wed, 25 Jul 2007 14:56:18 -0400
I'm guessing you're multiplexing your Exchange backups with other backups. Automatic cloning is cloning only the Exchange backup, where as volume cloning is cloning everything on that volume. So when
Author: "Werth, Dave" <dave.werth AT GARMIN DOT COM>
Date: Wed, 25 Jul 2007 13:29:04 -0700
Curtis, You're right, our automatic clones make a copy of the just completed backup and preserve the multiplexing of the backup. I've set up the different backups so they won't generally overlap with
Author: "Wood, R A (Bob)" <WoodR AT CHEVRON DOT COM>
Date: Wed, 25 Jul 2007 23:15:20 +0100
staging) is a desirable thing. Networker is good at backing up but not so hot when it comes to smart scheduling (i.e. don't start staging if cloning is going or some other job is running, etc.) Besi