Unsolved
This post is more than 5 years old
23 Posts
0
858
August 28th, 2007 06:00
architecture question
We have a remote site that is slow to backup (one client machine 18+ hours).. I'm wondering if placing a "storage node" instance up there with enough disk space could be a valid solution rather than installing yet another legato server. I'd associate the remote storage node to a server we have local down here.
Is this a valid idea or is that not how the idea of a storage node works?
I know this is not a new problem as many have had this issue in the past I'm sure.
Is this a valid idea or is that not how the idea of a storage node works?
I know this is not a new problem as many have had this issue in the past I'm sure.
No Events found!



ble1
4 Operator
•
14.3K Posts
0
August 28th, 2007 06:00
kfoote
23 Posts
0
August 28th, 2007 06:00
This does not really seem like a viable solution if it would work. The backup would be in the same location as the data. Thus not providing a solution of off-siteed-ness
We are going to look into consolidation or synthetic full backup for this client. This seems more promissing..
ble1
4 Operator
•
14.3K Posts
0
August 28th, 2007 06:00
vsemaska
194 Posts
0
August 28th, 2007 07:00
Vic
kfoote
23 Posts
0
August 28th, 2007 07:00
I still think consolidation is probably the way to go with our issue. This data goes to disk so adding another pool for the consolidation will not be that big of an issue.
ble1
4 Operator
•
14.3K Posts
0
August 28th, 2007 08:00
Using both is not recommended. Ever used 2 different compression algorithms one atop each other? Bad combination...
It really depends on data amount how to play with this further... how much data do you have on remote site?
kfoote
23 Posts
0
August 28th, 2007 08:00
The nwadmin guide is pretty lacking in technical details .. like usual.
Our thoughts on an initial schema for this.
Have a rolling consolidate on the back of our expire period say 4 weeks ago run incremental
each day there after and then always have a consolidate from today - 1.
Many questions arise:
- does consolidate throw away an incremental once a consolidate has been run?
- when a consolidate is run does it always go back to last full or does it go to a previous consolidated full.
- is it better to have a consolidate save as up to date as possible (ie: always have one for yesterday)
kfoote
23 Posts
0
August 28th, 2007 08:00
name totalsize level
d:\homedirs 12284637956 full
ble1
4 Operator
•
14.3K Posts
0
August 28th, 2007 11:00