tsm:blackeagle:06sep11
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| tsm:blackeagle:06sep11 [2011/09/19 20:13] – [Mac Drives] hmeij | tsm:blackeagle:06sep11 [2011/09/22 17:58] (current) – [Filespace] hmeij | ||
|---|---|---|---|
| Line 82: | Line 82: | ||
| It appears most servers are simply stuffed into the first schedule listed. | It appears most servers are simply stuffed into the first schedule listed. | ||
| + | |||
| + | |||
| + | UPDATE 09/20/2011: | ||
| + | * SCHED1216 has been extended to run till 18:00 hours (did not change the schedule name ...) | ||
| + | * SCHED0912 has been created | ||
| + | * Database backup and maintenance window is now 6am - 9am (reclamation might happen but migration is stopped) | ||
| ^ SCHED1216 node count = 550 ^ | ^ SCHED1216 node count = 550 ^ | ||
| Line 200: | Line 206: | ||
| * Exclude external drives / | * Exclude external drives / | ||
| * Exclude / | * Exclude / | ||
| + | |||
| + | ANSWER | ||
| + | http:// | ||
| + | |||
| + | explains nicely what Jim was talking about excluding drives via GUI and also points out you can do it via client dsm.opt settings. | ||
| + | |||
| + | so if we adopt a convention to force / to mount at some unique mountpoint, which it already does, we could do, evaluate from bottom up | ||
| + | |||
| + | exclude / | ||
| + | include / | ||
| + | include.dir / | ||
| + | |||
| + | In the meantime i can set up global excludes for some of our problem cases whose mountpoint are unique and if they do not need to be backed up. | ||
| ===== Mac Drives ===== | ===== Mac Drives ===== | ||
| Line 400: | Line 419: | ||
| |*: | |*: | ||
| |*: | |*: | ||
| + | |*: | ||
| exclude | exclude | ||
| Line 418: | Line 438: | ||
| |/ | |/ | ||
| |/ | |/ | ||
| + | |/ | ||
| * Filters have been applied. | * Filters have been applied. | ||
tsm/blackeagle/06sep11.1316463236.txt.gz · Last modified: by hmeij
