Troubleshooting Your Platinum Backup

From Catalyst
Revision as of 08:40, 19 September 2012 by Chris Morrison (talk | contribs) (See also)
Jump to: navigation, search

Summary

There maybe occasions whereby your backup may come up with error messages on completion. This article explains what these errors mean and gives tips on how to fix them.

Error Messages

Unable to Copy

There are occasions whereby the backup process would not be able to copy the backup file to the required device.

Example of Error

Starting backup...
Backup completed with the following log:
---------
Zip log opened Tue Apr 12 15:21:29 2011
command line arguments:
--filesync --logfile-path C:\DOCUME~1\Rich\LOCALS~1\Temp\nsq20.tmp\SXBackup.log 
--display-counts --ignore-case --recurse-paths --exclude SXCo*\SX*.D?? 

@ SXBackup\SXBackup.zip SXUtils\*.INI SXCo*

Total 1747 entries (planned 130M bytes, actual 130M bytes)
Done Tue Apr 12 15:22:34 2011
---------
Copying backup...
Copy to C:\sx
Backup file successfully saved to C:\sx\SXBackup.zip
Backup file COULD NOT BE successfully saved to X:\SXBackup.zip
Backup has completed with warnings

Reason for Error

The problem is due to the Drive letter of your backup device changing. This can happen for a number of reasons

  • You have replaced your Backup Device and it is now taking another drive letter.
  • The backup device is not being picked up by the PC it is plugged into.
  • The Backup device you are using is taking the same drive letter as something else.

Solution

To correct the issue you will need to change the backup drive letter to match the one in the line on the backup screen that says "Backup file COULD NOT BE successfully saved to X:\SXBackup.zip".

For help on how to do this please see This knowledge base article.

Permission Denied

A "Permission Denied" Message on the "zipping" process means the system believes that the backup file is in use in some way.

Example of Error

Starting backup...
Backup completed with the following log:
---------
Zip log opened Tue Apr 12 15:21:29 2011
command line arguments:
--filesync --logfile-path C:\DOCUME~1\Rich\LOCALS~1\Temp\nsq20.tmp\SXBackup.log 
--display-counts --ignore-case --recurse-paths --exclude SXCo*\SX*.D?? 

@ SXBackup\SXBackup.zip SXUtils\*.INI SXCo*
zip warning: Permission denied
zip warning: could not open for reading: sxco1/GR314801.TMP
zip warning: Permission denied
zip warning: could not open for reading: sxco1/GR314802.TMP
zip warning: Permission denied
zip warning: could not open for reading: sxco1/GR984801.TMP
zip warning: Permission denied
zip warning: could not open for reading: sxco1/GR984802.TMP
zip warning: Permission denied
zip warning: could not open for reading: sxco1/GR984803.TMP
zip warning: Not all files were readable
files/entries read:  1742 (130M bytes)  skipped:  5 (15K bytes)
Total 1747 entries (planned 130M bytes, actual 130M bytes)
Done Tue Apr 12 15:22:34 2011
---------
Copying backup...
Copy to C:\sx
Backup file successfully saved to C:\sx\SXBackup.zip
Backup has completed with warnings

Reason for Error

This can be caused by several things

  • 1. Someone is still logged into Platinum when the backup goes through (Often caused by Platinum being Minimized to the Start bar and forgotten about)
  • 2. Someone PC has crashed and this has locked the file on their PC. This can be solved by rebooting that PC.
  • 3. The system has crashed to such a degree that the files are locked on the server rather than the terminal PC itself.

Issues 2 and 3 would should show up as users on the "User Monitor Screen" in Platinum as users not on today's date. If this is happening regularly then it maybe worth investigating what the crashes are to try and get them fixed.

Solution

If you have followed the steps above (i.e. got all users out of Platinum) and the error is still occurring this is usually caused by files being locked on the central Platinum server. Should you encounter this problem make a note or take a screenshot of your screen and Contact your Platinum dealer or our support team on 0116 230 1500 or by using our website support contact page.

You should find if these steps are done in the order above this should result in a successful backup with no errors.

See also


Feedback
Thank you for using our Knowledge Base, we value your feedback. Did you find this article useful? 'Yes' or 'No'
Keywords AND Misspellings
BACKUP, BACK UP, BACKUP, SXBACKUP, ERRORS, TROUBLESHOOTING, TROUBLESHOOT