Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Web UI Cloud Administrator's Guide
  3. Troubleshooting protection and recovery of cloud assets
  4. Troubleshoot PaaS workload protection and recovery issues
  5. Troubleshooting Amazon Redshift issues
NetBackup™ Web UI Cloud Administrator's Guide

Troubleshooting Amazon Redshift issues

Restore fails for Amazon Redshift, if the query string is larger than 100 KB

Explanation:

This is a known limitation of AWS. The maximum query statement size is 100 KB. See the AWS documentation for the details:

https://docs.aws.amazon.com/redshift/latest/mgmt/data-api.html

After a successful Redshift database restore, if the number of stored procedures, views, and functions are not the same as the source database.

Workaround:

Do the following:

  1. Mount the Instant Access (IA) path using the following API:

    netbackup/recovery/workloads/cloud/paas/instant-access-mounts

  2. Navigate to the mount path in the media server.
  3. Ensure that the mount path directory hierarchy is as follows:

    ClusterDirectory/DatabaseDirectory/DatabaseDirectory/SchemaDirectory/TableDirectory

  4. In the SchemaDirectory, locate the files StoredProcedures.json, Views.json, and Functions.json. Each file contains one or more SQL statements which you can run in Amazon Redshift Query Editor-2.

    Manually run these SQL statements.

botocore.exceptions.ClientError: An error occurred (InvalidSignatureException) when calling the ListDatabases operation

Explanation:

If the system time where you run the AWS Redshift APIs is not correct, you get this error. This message appears in the logs:

Signature expired: 20230226T181919Z is now earlier than 20230226T181921Z (20230226T182421Z - 5 min.)"

Workaround:

Run the ntpdate command to fix the system time.

Backup or restore jobs fail with the "NoCredentialsError: Unable to locate credentials" error.

Explanation:

This error appears when the region is not specified. You can see the following error in the dbagentsutil logs. You can find the dbagentsutil logs at the following location:

/usr/openv/netbackup/logs/

Workaround:

Do the following:

  1. Download AWS CLI on the media server where the dbagent is running.
  2. Run the command:

    aws configure

  3. Enter the region name for EC2 when prompted. Do not specify the values for the other parameters.
Backup and restore stuck for Redshift databases

Explanation:

This error appears when the NetBackup Snapshot Manager that runs the discovery does not have access to the Redshift cluster. You can see the following error in the flexsnap logs:

Connect timeout on endpoint URL: "https://redshift.us-east-2.amazonaws.com/

Workaround:

Without access permission, the Snapshot Manager requires the inbound rules to be configured for the snapshot manager in the security group of the 'VPC endpoint of the Redshift service'.

On the AWS portal, select a cluster. Click Properties > click Network and security settings > click the virtual private cloud object > click Endpoints. Search for "redshift-endpoint" in the search field > click the VPC endpoint ID > click the Security Groups tab. Click the Security Group ID > click Edit Inbound rules, and add the following for media servers.

Type : HTTPS

Protocol : TCP

Port range : 443

Source : 10.177.77.210/32

* Here, the source refers to the media server instance.

Run discovery from NetBackup web UI again.

Feedback

Was this page helpful?
Previous

Troubleshoot PaaS workload protection and recovery issues

Next

Troubleshooting Azure Postgres issues

Feedback

Was this page helpful?