Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Sybase 11.4.5 - User Guide

Restoring a database to a new location (relocation)

Restoring a database to a new location lets you restore a database with its original name and configuration, but to a new location. Verify that the following requirements are met:

NetVault Backup installed: At a minimum, the Client version of NetVault Backup must be installed on the target machine. Also, the Plug‑in for SAP ASE must be installed and licensed for use.
Added as a Client to the NetVault Backup Server: The new SAP ASE Server target machine must be added to the NetVault Backup Server as a NetVault Backup Client. This requirement is controlled from the Manage Clients page. For details on this procedure, see the Quest NetVault Backup Administrator’s Guide.
1
On the target SAP ASE Server, create a database that has the same name and configuration as the original.
2
In the Navigation pane, click Create Restore Job, select Plug‑in for SAP ASE from the Plugin Type list, select the applicable saveset, click Next, and select the database that you want to restore.
3
On the Create Selection Set page, click Edit Plugin Options, and configure the following parameters on the Options tab:
In the Default Target Server field, enter the name of the new SAP ASE Server.
In the Account field, enter the account name that corresponds to newly set SAP ASE Server, that is, an account name that allows access to the installation of SAP ASE on the target machine.
In the Password field, enter the password associated with this account.
IMPORTANT: Entries in the Password field are case-sensitive.

The Account and Password values given must be associated with the new target SAP ASE Server for this operation to function properly. Verify that the values entered for these two fields correspond to the applicable target SAP ASE Server.
4
To save the settings, click Ok, and then click Next.
5
In Job Name, specify a name for the job if you do not want to use the default setting.
6
In the Target Client list, select the applicable target SAP ASE Server.
7
Use the Schedule, Source Options, and Advanced Options lists to configure any additional required options.
8
Click Save or Save & Submit, whichever is applicable.

Troubleshooting

This topic describes some common errors and their solutions. In those cases where an error occurs and is not described in this table, obtain the SAP ASE error number from the NetVault Backup Logs, and then see the relevant SAP ASE documentation for the resolution.

NetVault Backup 10.x service (netvault-pgsql) does not start on Windows

Check the Windows Event Viewer for the following message: PDT FATAL: lock file “postmaster.pid” already exists.

NetVault Backup 10.x uses a PostgreSQL database. If the PostgreSQL database does not start, NetVault Backup cannot start. To correct this issue, delete the “postmaster.pid” file from the location referenced in the log and restart the NetVault Backup Server. For more information, see https://support.quest.com/netvault-backup/kb/122475.

Backup failed

Unable to open API library for device.

Verify that the “libsybhook” file has been copied from the “NetVault\lib” directory to the appropriate SAP ASE directory. For more information, see Backing up data.

Backup failed

(Linux/UNIX-based SAP ASE Server)

Either of the following:

Warning <DateAndTime> Data Plug-in AS3SMP Did not receive message back from libsybhook before grace time expired
Error <DateAndTime> Data Plug-in AS3SMP Sybase Message: ‘Error encountered by Backup Server. Please refer to Backup Server messages for details.’

The first time that the plug-in is used, NetVault Backup automatically generates a necessary symbolic link between the instance of SAP ASE and the NetVault Backup Server, that is, “$SYBASE/ASE-<version#>/lib/libsybhook.<so/a/sl>” to “$NV_HOME/lib//libsybhook.<so/a/sl>.” If one of these errors is displayed, it indicates that this symbolic link has been modified or removed. This link should be left alone and not modified. However, it can be re-established by issuing the following command from a terminal session prompt on the SAP ASE Server:

ln -s /&lt;netvault_home&gt;/lib/libsybhook.
<so/sl> $SYBASE_HOME/ASE-<version#>/lib/libsybhook.<so/sl>

Ensure that the proper version is used to call out the installation directory for SAP ASE, for example, “15_0” for 15.0 or 15.5. Also ensure that the proper file extension is used for your OS, for example, “.so” or “.sl.”

Backup failed

…The attempt to connect to the server failed.

Verify that the password for the database server has not been changed between the time that the backup job was scheduled and the time that the job ran. To resolve this issue, redefine the job.

Backup Completed with warnings

After this status is displayed for a backup, check the NetVault Backup log entries for the job to see if they display one or both of the following messages:

These messages indicate that the selected data was backed up, but the job’s index information was not properly added by NetVault Backup to its database. Without this index information, the data cannot be properly restored.

Method 1:

Access the Manage Devices page in the NetVault Backup WebUI and scan the media targeted by the job. NetVault Backup stores index information for backup jobs in two locations: in the NetVault Database and on the media targeted by the backup. Performing this scan adds the index information to the NetVault Database. To verify that the information was added, open the Create Restore Job — Choose Saveset page and locate the specific job. If you can browse it and set up a restore job, the scan process has corrected the problem.

Method 2:

If the previous method failed, run the backup job again.

An incremental or differential backup of a database failed.

Syslogs does not exist in its own segment in database <database> with segmap <x> with logical start page number of ‘0’. You cannot use DUMP TRANSACTION in this case. Use DUMP DATABASE instead.

The database device was configured so that the data and logs reside together and must be backed up as a unit. For more information, see the SAP ASE documentation.

Restore “Completed with Warnings”

…The attempt to connect to the server failed.

A password was not specified on the Options tab of the Create Restore Job — Choose Saveset page. Enter the correct password for the account and resubmit the job.

For more information, see Restoring data.

Restore “Completed with Warnings”

…Net-Lib protocol driver call to connect two endpoints failed.

The database server selected for restore was offline. Ensure that the database server is online.

For more information, see Restoring data.

Database restore “Completed with Warnings”

Attempt to locate entry in sysdatabases for database <name> by name failed – no entry found under that name. Make sure that name is entered properly.

The database selected for restore does not exist on the target SAP ASE Server. Using SAP ASE-native utilities, re-create the database with specifications that are the same as or greater than the original, before attempting the restore. For instructions on re-creating a database, see the SAP ASE documentation.

Incremental restore “Completed with Warnings”

Specified ‘dump device’ is out of sequence.

An Incremental Backup sequence is being recovered out of order. Previous Incremental Backups must be recovered in order before attempting to recover the selected Incremental.

For more information, see Restoring Incremental and Differential Backups.

Master Database restore “Completed with Warnings”

Any of the following:

You can ignore these messages. This result is expected behavior and the restore has completed successfully. These messages only indicate that the connection between the plug-in and the SAP ASE Server was dropped due to the successful restore of the master database; that is, any client connections to the SAP ASE Server are still valid.

Cannot open the database server to display the databases within it.

Failed to get list of databases – check login information. Also check that the locales.dat SAP ASE file contains a matching entry for the environment

Method 1:

Verify that the database server is online and that the correct password was entered on the NetVault Backup Selections page.

Method 2:

For example: export LC_MESSAGES=C
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione