![]() ![]() Yes, the communication between server and client is good We use that script for many many clients, I don't think that is the issue. Server Group: (same as specified for policy) Volume Pool: (same as policy volume pool) Residence: (specific storage unit not required) Residence is Storage Lifecycle Policy: noĮxchange 2010 Preferred Server: (none defined)Ĭlient/HW/OS/Pri: testwater01-bkup Solaris Solaris10 0 0 0 0 ? ![]() I read the the technote below this seems to not apply to our situationĪ client backup receives a Status 200 message "scheduler found no backups due to run" when multiple backups of the same type are scheduled on the same day, for the same policy, with calendar-based scheduling.Ĭollect TIR info: yes, with move detection I have done numerous clients and they have run without issue. FUND EZ BACKUP SCHEDULER NOT RUNNING CODEI setup the same policy again yesterday and last night the backup received the same STATUS CODE 200. ![]() FUND EZ BACKUP SCHEDULER NOT RUNNING FULLWe are updating are clients to a calendar base schedule, I updated a Solaris client policy the other day and the FULL backup failed with a status code 200 "scheduler found no backups due to run. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |