RecoveryOne
ADSM.ORG Senior Member
- Joined
- Mar 15, 2017
- Messages
- 347
- Reaction score
- 81
- Points
- 0
Was wondering if anyone has any insight as to forcing a systemstate to backup from the client options set.
Most of my Windows servers are using a pre-defined clopt from the server and in the local dsm.opt have a few adjustments on a server by server basis. In the past, we weren't doing systemstate... Many of the systems dsm.opt have a statement of "domain ALL-LOCAL -systemstate".
What I was hoping to do is force the systemstate to backup without forcing ALL-LOCAL to backup. As such I have to domain statements at the top of the server side optionset:
I added sequence 1 the other day, came back and queried the filespaces on a few nodes, and even ran q systemstate from a few clients as well. Nothing.
If it can be helped I really don't want to go about and touch every dsm.opt file on every server!
Thanks!
Most of my Windows servers are using a pre-defined clopt from the server and in the local dsm.opt have a few adjustments on a server by server basis. In the past, we weren't doing systemstate... Many of the systems dsm.opt have a statement of "domain ALL-LOCAL -systemstate".
What I was hoping to do is force the systemstate to backup without forcing ALL-LOCAL to backup. As such I have to domain statements at the top of the server side optionset:
Code:
Option Sequenc- Use Optio- Option Value
e number n Set
Value
(FORCE)
------------------------- -------- ---------- ---------------------------------
DOMAIN 0 No ALL-LOCAL
DOMAIN 1 Yes systemstate
If it can be helped I really don't want to go about and touch every dsm.opt file on every server!
Thanks!