Backup and Restore dialog

This dialog allows you to back up your Time database and all supplementary files to a file (*.tbk) or restore your database from a file.

Select whether to back up or restore the file. When you run the process, the Time file will be closed. The file will be reopened when the backup or restore is complete.

Backup

During a backup the files are copied to the location selected by the user and compressed into the .tbk file. The .tbk file is backed up to the location you specified in the Location Field.

Tip: For more information about backing up your files, see Backing up Time Files located on the CaseWare website.

Back up to

Enter the path to the directory where the backup should be saved. Click browse and navigate to it to enter the path automatically.

During the backup procedure, Time does the following:

    1. Checks all the paths to see if there is a connection to the computer. If there is a connection then it continues copying. If there isn’t a connection the application will try to create a connection.

    2. If the server is password protected, Time will prompt the user for the Password and ID of the server. It will notify the user if it was unable to connect to any computer due to firewalls. It will also notify the user if it was unable to create net share directories.

    3. Automatically creates a sub-folder in the directory you selected for the backup using the following naming convention:

      Backup of <file name> + date (e.g. Backup of Ctdemo (4-20-2010)). For example:

ClosedDid the Backup/Restore fail?

Types of error messages

Note: "%s" typically represents the name of a path (e.g. server name, source name, destination name, folder name, etc.).

Error message

Description

Solution

%s is not accessible. The reference account is currently locked out and may not be logged on to.

This error message may appear when typing a folder name in the "Backup to" field.

This error usually occurs when the source folder is in a workgroup, and the destination folder is in a domain or vice versa.

Ensure all computers are part of the same domain.

Unable to connect to %s. Please contact your network administrator.

This error may appear if the process is unable to connect to the server.

This error indicates that either the user has entered an incorrect ID or password OR the server doesn't exist.

Verify your ID and password with your Network Administrator.

You need rights to create a shared directory on %s computer.

Please contact your network administrator.

This error indicates the user was not able to create a shared directory.

Ensure you can share a directory from your SQL server machine. You may have to get permissions from your Network Administrator to create a directory on the SQL server machine. 

Copy %s to %s has failed. Check hard disk space. 

This error indicates that the user can't copy from the source to the destination (destination hard drive may be filled or the user doesn't have write access).

Ensure you have sufficient hard disk space on your destination hard drive. If you have sufficient space, ensure you have permission to perform copy operations to the destination location. 

File backup failed

This error appears when Time cannot perform the backup and the other errors are not the reasons. There could be a firewall between the machines that prevent the NETBIOS connection even though there is an ODBC connection.

You will need to contact your network administrator to resolve the issue.

Ensure you can create a directory on the machine running your SQL server. Try to share that directory and then, from a remote computer, try to copy a test file from that shared directory. If you cannot perform this task, contact your Network Administrator.  

Restore database failed. File may be corrupted or has been created with an incompatible SQL version.

This error appears when trying to restore a .tbk file that's been created with SQL Server 2008 to SQL Server 2005.

Verify the versions of both your SQL backup file and the SQL database you are performing the restore from. Ensure the SQL backup file version is not higher than the SQL database version.   

A solution for this problem is to use the "Copy database to another SQL server" function available in Time; restore the backup file using a database with the same version and use the Time function to copy the file to a lower version of that database. For more information, contact CaseWare Technical Support. 

If the versions of both the backup file and database are the same, it is possible the file may be corrupted. In this case, use an older copy of the backup file. 

%s could not be shared on the server. Access is denied. File backup failed.

Time allows you to make a backup of your Time file and save it to a location you specify. In order to process this function successfully, you must have sufficient rights for the SQL server and the logon property must use the Local System Account.

You can verify this on the SQL server machine:

  1. Click Control Panel | Administrative Tools | Services | SQL Server (MSSQLSERVER).
  2. Right-click SQL Server (MSSQLSEVER) and choose Properties.
  3. From the Log On tab, make sure the ”r;Local System account” option is selected. If not, change it to "Local System account”.

If the above procedure does not work then go to your SQL server machine and verify you can share any directory from Windows Explorer. In Windows Explorer, select any folder, right-click and select Properties. From the Sharing tab, select "Share...". If this does not work then contact your Network Administrator to enable your rights to share on that server.   

 

Restore

On the Microsoft SQL or SQL Express servers, the restore can be performed only when no one else is using the database.

When you restore a file, Time uses the backup file (.tbk) to:

  • Restore the supplementary files to the location you specified in the Restore supplementary files to field, and
  • Restores the database to the SQL Server.

Notes

  • If you are currently in a file and are performing a restore, Time will overwrite the current database. For more information on performing a restore, see "Restoring files in Time" on the CaseWare website.
  • If you are not currently in a Time file, Time will display the Connect to Database dialog, in which you will enter the information for the SQL Server you are restoring to. If the file exists on the server the program will ask you if you would like to overwrite the file.
  • You cannot have two databases with the same name on one SQL Server. If you need to review a backed up file, you need to open the file in another instance of SQL Server or on another machine (or server). For further assistance with creating an instance of SQL Server, see "Creating a named instance for SQL Server 2005" on the CaseWare website.
  • You cannot restore a Time file to a version of SQL Server that is lower than the version from which you started. For example, if you created the Time file using SQL Server 2008, then you cannot restore this file using SQL Server 2005. When restoring a Time file, ensure the SQL Server version is the same or higher than the original version used to create the file.

  • If Cloud Integration is enabled,

    • You must be Online to perform this operation. When you are Offline, this operation is disabled.

    • Restoring your Time file will remove items from the Cloud. See more...

 

Restore file

Enter the path to the directory where the backup was saved. Click browse and navigate to it to enter the path automatically.

Restore supplementary files to

Enter the path to the directory where the restored supplementary files should be saved. Click browse and navigate to it to enter the path automatically. The Restore procedure expands the backed up file as it saves it to this location.

Process

Click process to begin the backup or restoration.

Viewing a backup file

Before restoring a backup file and overwriting your existing file you may wish to review the backup file.

Microsoft SQL Server does not allow two databases with the same name to reside on the same SQL server. To view the backup file you can do one of the following:

  • Install SQL Server on another server and restore your backup file to the new server. For more information on viewing a backup file, see the section "Viewing a backup file" here on the CaseWare website.
  • Create another instance of SQL on your existing SQL Server. For further assistance with creating an instance of SQL Server, see "Creating a named instance for SQL Server 2005" on the CaseWare website.

Comments and suggestions about this article and our software are greatly appreciated. As a user of our products, you are in a unique position to provide ideas that have an impact on future releases of this and other products.

Before contacting Technical Support, please consult the online Help and any other documentation included with this package as your first source to solve the problem.

If you require additional assistance, you can contact CaseWare® Technical Support by contacting your nearest CaseWare distributor.

When you contact CaseWare® Technical Support, you should be at your computer and have your documentation at hand. Be prepared to provide the following information:

  1. Your Client Number.
  2. The product version number, found by clicking the Help menu and selecting About.
  3. The type of computer hardware you are using.
  4. The software version number of MS-Windows.
  5. The exact wording of any messages that appear on your screen.
  6. A description of what happened and what you were doing when the problem occurred.
  7. A description of how you tried to solve the problem.

CaseWare Support

NORTH AMERICA

Email: support@caseware.com

Phone: 416-867-9504

GLOBAL

Find your local distributor

Copyright ©2017 CaseWare International Inc

| Visit us: www.caseware.com | Share your feedback with Google Moderator |


Follow us     



Legal