If you run BackupPC_tarCreate or BackupPC_zipCreate there shouldn't be any file size limits.
If you download a tar or zip archive from the CGI interface, the browser might impose some limit, but I'm not sure. Craig On Mon, Jun 24, 2019 at 4:57 AM Philip Parsons (Velindre - Medical Physics) <philip.pars...@wales.nhs.uk> wrote: > Hi Craig, > > > > Thanks for your reply. > > > > Is there a file size limit on the output zip or tar from BackupPC? > > > > It’s a bit odd that it’s able to create the folder it’s going to write to > and then just stops. > > > > Thanks, > > Phil > > > > *From:* Craig Barratt via BackupPC-users [mailto: > backuppc-users@lists.sourceforge.net] > *Sent:* 23 June 2019 19:58 > *To:* General list for user discussion, questions and support < > backuppc-users@lists.sourceforge.net> > *Cc:* Craig Barratt <cbarr...@users.sourceforge.net> > *Subject:* Re: [BackupPC-users] restore issue on backuppc 4.1.5 > > > > I'd recommend downloading a tar or zip file instead, and then use native > windows tools for extracting them in the place you wish. > > > Craig > > > > On Mon, Jun 10, 2019 at 3:24 AM Philip Parsons (Velindre - Medical > Physics) <philip.pars...@wales.nhs.uk> wrote: > > Hi Michael, > > > > Thanks for that. I’ve got that working. > > > > However, I appear to be back to a similar error as before. > > > > Running: /usr/bin/smbclient \\\\restoredestination\\D\$ -U account -E -d > 1 -c tarmode\ full -mSMB3 -Tx - > > Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h restoresource -n > 513 -s sharename -t /foldername > > Xfer PIDs are now 143159,143160 > > WARNING: The "syslog" option is deprecated > > [ skipped 1 lines ] > > tar:316 tarmode is now full, system, hidden, noreset, quiet > > tar:1597 Can't mkdir foldername: NT_STATUS_OBJECT_NAME_COLLISION > > readOutput: sysread returns 0 and got EOF (exit ok = , ) > > XferErr Non-zero exit status from smbclient > > restore failed: BackupPC_tarCreate failed > > > > It appears to create foldername in the share, but then stops. > > > > Thanks again for all your help. > > > > Thanks, > > Phil > > > > > > *From:* Michael Stowe [mailto:michael.st...@member.mensa.org] > *Sent:* 04 June 2019 20:29 > *To:* Philip Parsons (Velindre - Medical Physics) < > philip.pars...@wales.nhs.uk> > *Cc:* General list for user discussion, questions and support < > backuppc-users@lists.sourceforge.net> > *Subject:* Re: [BackupPC-users] restore issue on backuppc 4.1.5 > > > > On 2019-06-04 07:33, Philip Parsons (Velindre - Medical Physics) wrote: > > Thanks for the reply Michael. > > > > I’ve tried to restore to another share on another server and am getting > NT_STATUS_BAD_NETWORK_NAME > > > > I don’t want to overwrite the existing data, I just want to be able to > download data to another share so that I can QA our backups. > > > > Running: /usr/bin/smbclient \\\\destinationserver\\share -U domainaccount > -E -d 1 -c tarmode\ full -mSMB3 -Tx - > > Running: /usr/local/BackupPC/bin/BackupPC_tarCreate -h sourceserver -n 510 > -s sourceshare -t /sourcefolder > > Xfer PIDs are now 104823,104824 > > WARNING: The "syslog" option is deprecated > > [ skipped 1 lines ] > > This backup will fail because: tree connect failed: > NT_STATUS_BAD_NETWORK_NAME > > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > [ skipped 1 lines ] > > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > readOutput: sysread returns 0 and got EOF (exit ok = , ) > > XferErr Non-zero exit status from smbclient > > restore failed: tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > > > > > thanks again for any advice! > > Phil > > Samba errors are maddeningly unspecific. In this case, the error > translates to "something about that share ain't working for me." It could > be anything from the share name being misspelled, or the wrong part of the > tree, or permission errors. > > At any rate, the simplest way to diagnose this is to start with what the > share names are: > > smbclient -L //destinationserver > > This should give you a list of valid shares -- if the sharename you tried > doesn't exactly match one of the shares in that list, viola, that is the > trouble. (N.B. I do mean *exactly.* There's no support for joining the > tree at a different point in the hierarchy.) > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ > > _______________________________________________ > BackupPC-users mailing list > BackupPC-users@lists.sourceforge.net > List: https://lists.sourceforge.net/lists/listinfo/backuppc-users > Wiki: http://backuppc.wiki.sourceforge.net > Project: http://backuppc.sourceforge.net/ >
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
