error

ImageManager Retry Button

2

This is separate from my suggestion here:
https://www.storagecraft.com/support/feature-request/replication-auto-retry

Replication should be able to aggressively retry its operations if there is an error or failure and only alert if it determines that it can not continue. Minor hiccups will occur when you are transferring over a WAN connection, I want ImageManager to be a little more resilient towards this reality. If you agree with this follow the link above and vote on my other idea!

 

Replace generic "An error occurred during send operation" with more specific error message(s)

3

Reference the generic failure type notification of: "An error ocurred during send operation: <Image name.spi>"

This type of error notification message is too generic. In a recent support ticket it was found that this error was sent due to a time out error in the ShadowStream transfer. See excerpt from SST log for the given job:

28-Oct-2015 00:38:59 send error: list timeout exceeded

28-Oct-2015 00:39:01 SmtpClient message sent

Replace generic "An error occurred during send operation" with more specific error message(s)

7

Reference the generic failure type notification of: 

An error ocurred during send operation: <Image name.spi>

 

This type of error notification message is too generic. In a recent support ticket it was found that this error was sent due to a time out error in the ShadowStream transfer. See excerpt from SST log for the given job:

28-Oct-2015 00:38:59 send error: list timeout exceeded

28-Oct-2015 00:39:01 SmtpClient message sent

Add ShadowControl alert for ImageManager unable to access a backup folder

1

If ImageManager can't access a backup folder (due to a password change etc), it can't control the images or replicate images to an offsite location via FTP, but there is NO error raised in ShadowControl and so this problem goes unnoticed.

I feel this needs to be fixed in the next release as we have now seen this problem twice and rely on ShadowControl to report any errors within its backup system.

Verification Fails (but Backup Successful)

 I have completed several full  backups of my Drive (E:) and they complete successfully. I can also Explore the backups.

 However, when I try to verify any of the backups, I always get errors (see below).

Are the backups corrupted? Any suggestions for how to create a backup that can be verified successfully..? 

 p.s. v3.5.1

=== Errors when attempting Verification=====

XP unbootable after restoring to C drive (hal.dll missing or corrupt; not solved via knowledge base)

I'm experiencing the same exact problem described in the Knowledge base here:

"Error Message: Cannot Find \Windows\System32\hal.dll"
http://support.storagecraft.com/kb/article/72

and in this forum post:

"Problems with C-drive restore: hal.dll"
http://support.storagecraft.com/forum/problems-c-drive-restore-haldll#co...

 My situation is somewhat different, however, because:

Error (file not found on server) downloading the ISO image

Having just registered ShadowProtect Desktop, I have tried downloading the ISO image for the rescue disc. On starting the download, however, I receive the following error:

http://www.tranglos.com/img/iso-dl-error.png

(Inserting the image directly in the post doesn't seem to work for me.)The text of the message is: "The file was not found on the server! This build of StorageCraft may be out of date. Press Resume on the main window to retry if you think this is a temporary problem"

lsass Shadow Copy Freeze Started/Stopped Windows SBS 2003

I have a Windows SBS 2003 with no SQL services enabled. Though they were installed at one time. I applied Microsoft's http://support.microsoft.com/kb/830575 with no luck to fixing the issue. Shadow Copy runs successfully with no issue on its own, but errors with ShadowProtect starts its job. Please advise.

 Thanks,

Mikel Reber

Auth settings needs updated when connecting to client machines

It seems that for no apparent reason the authorization settings stored for the client nodes is changing.  In a couple cases the domain name is simply dropped.  In other cases the password needs updated in order to successfully connect to the client machines.The clients have all been successfully connected to through the server management console. 

RPC server is not available

 Hello everybody,

 

I've got 2 servers : one with the ShadowProtect.exe GUI, and another one with the Backup Agent. I'd like to connect to the agent and I created a new node (I'm sure of my credentials). Anyway, a message appears, saying 'error while connecting to the server. RPC server is not available'.

Syndicate content

Terms and Conditions of Use - Privacy Policy - Cookies