Another suggestion
Another suggestion
note: this screen shot was created as an example. Normally the clock shows hours of waited time, not 10 seconds !
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: Another suggestion
nothing is being backed up at that point, it's waiting for drive writing to stop up to the max wait time of 10 min for phylock to start. PHYLock is used if VSS is not enabled or fails to say its available to be used. If it's beyond roughly 10 min, you' have to send a full dump to support to see why .. You can use something like https://learn.microsoft.com/en-us/sysin ... s/procdump
Re: Another suggestion
I understand all that, but I would like to see some information that is meaningful on your Preforming the backup window.
Knowing what was going on, other than phylock was running, might help me find the problem. Yes/No ?
Knowing what was going on, other than phylock was running, might help me find the problem. Yes/No ?
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: Another suggestion
PHYLock is not running yet either, it's waiting. As mentioned, if it goes beyond max wait time, do a full dump on the process and send it to support to check out what it may be.
Re: Another suggestion
You are running phylock against some disk/partition for some purpose.. You know some information about the disk : drive letter, ntsig,guid, image command that caused this action...etc. Why not put something on that screen to tell me what drive/partition phylock is accessing.
Your message says: Phylock is waiting for drive writing to stop. Tell me what the drive is. I don't need to know how it works.
Your message says: Phylock is waiting for drive writing to stop. Tell me what the drive is. I don't need to know how it works.
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: Another suggestion
The drive being backed up.
Re: Another suggestion
My backup processes run in the background. It invokes image with the appropriate parameters. Many partitions are backed up on different days and different intervals. As these are run in the morning am hours, nobody is there to look at the screens, except at 8:am when the screen is showing PHYLOC waiting.
WHEN I SEE THE SCREEN I AM UNABLE TO TELL WHAT, WHERE AND WHO is having the problem. Do you understand what I am asking for?
WHEN I SEE THE SCREEN I AM UNABLE TO TELL WHAT, WHERE AND WHO is having the problem. Do you understand what I am asking for?
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: Another suggestion
currently you would need to see which completed to know one it's on (or if you enable the log to write direct, it would be in the .log, but then you can't have it emailed).
Re: Another suggestion
I guess it is not possible for you to put any additional logical relevant information on your status screen. Just come out an say it.
Thank you for your useless information, and your lack of understanding.
This is the first time that I have been completely dissatisfied with Terabyte support in more than 8 years.
No follow up comments are needed. I can program around your information failure.
Thank you for your useless information, and your lack of understanding.
This is the first time that I have been completely dissatisfied with Terabyte support in more than 8 years.
No follow up comments are needed. I can program around your information failure.
Re: Another suggestion
tas3086,
Is your source disk failing? Each error seems related to that disk.
Is your source disk failing? Each error seems related to that disk.