• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

entire server bacups

P

prophoto

Guest
entire server backups

Message I receive when attempting to perform "entire server" backup:

[root@ bin]# ./pleskbackup all /root/pleskbackup/20070725_servername

Runtime error: Unable to write to output file: No space left on device at /usr/local/psa/PMM/agents/shared/Storage/Splitter.pm line 84.


gzip: stdout: Broken pipe
backup_sign: Error writing dump to file
System error 32: Broken pipe

The script outputs a file in the directory specified, but how do I know if the backup file was corrupted? Is there something else I am missing?

Prophoto
Fedora Core 4
Plesk 8.2
 
Seems like the partition you were writing to ran out of space. I bet the file that was created is pretty useless.
 
I checked the disk space on the server 1 and it does not seem to be the issue.

I tried to run a backup on server 2. This is the error I am receiving there:

Runtime error: Can't use an undefined value as a symbol reference at /usr/local/psa/PMM/agents/shared/Storage/Splitter.pm line 75.


gzip: stdout: Broken pipe
14:43:02 ERROR Failed to create MIME message
 
You must log in or register to reply here.

Similar threads

J.Wick
Input Allow Backup Scope Selection: Subdomain Document Root vs. Parent Directory
Replies
1
Views
5K
Sebahat.hadzhi
Sebahat.hadzhi
P
Issue Backup warning, due to root perms of .ssh/ directory. Backup "was created and can be restored, although some minor issues occurred."
Replies
1
Views
2K
scsa20
scsa20
asalas
Issue [.NET Core] Misleading error: Could not load file or assembly 'Microsoft.IdentityModel.Protocols, Version=7.1.2.0'
Replies
4
Views
4K
asalas
asalas
Azurel
Question Could someone share their "ss -tulpn" output from AlmaLinux 9?
Replies
6
Views
2K
Azurel
Azurel
B
Issue Backup Manager (and migrator) not working after failed inplace upgrade
Replies
6
Views
17K
Kaspar@Plesk
Kaspar@Plesk
Back
Top