Best Practices
-
I think, beyond that, you are getting into near HA needs.
-
Could you set it up with a DFS namespace? Or is this not file share data and only database data?
-
@coliver said in Best Practices:
Could you set it up with a DFS namespace? Or is this not file share data and only database data?
He said DB
-
@JaredBusch said in Best Practices:
@coliver said in Best Practices:
Could you set it up with a DFS namespace? Or is this not file share data and only database data?
He said DB
Right, critical data is DB
-
@JaredBusch said in Best Practices:
@coliver said in Best Practices:
Could you set it up with a DFS namespace? Or is this not file share data and only database data?
He said DB
If that's the case then doing @JaredBusch original suggestion would make the most sense.
-
I'm with @JaredBusch this is what DNS aliases are for.
-
Prior to the changes, update your DNS TTL to be extremely short.
That way there will truly be little downtime for any properly configured system.
-
Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?
-
@s.hackleman said in Best Practices:
Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?
That wold be the better thing, yes.
-
@s.hackleman said in Best Practices:
Could I make a DNS alias called HistoryServer Then point it to both History1? Then point all apps to HistoryServer. When ever an upgrade comes due, I can just update the DNS alias in one place?
Yes, but if you can do that, you could just rename, too. This is the better way to go, and ideally should be done from the start.
