'Auto Saved' files unrecoverable?
Hey All, I ran into an issue with a customer and came to the conclusion that NetBackup just will not recover "auto saved" files and those that were open. However, customer is asking if it backed up, it should be recoverable, which is a valid point. I could not find documentation to prove this and am hopping on here to see whether or not you can validate. Here is why: customer came with an exit status 185, error log attached. Backups past 7 days are not recoverable. we changed net buffer size and created a touch file for restore size to smaller blocks from the linux media to the win client we addedCLIENT_NAME = <master FQDN> in the master bp.conf validated the backup in catalog after above steps, we restored the requested files and they failed with the same status. However, we were able to restore a spreadsheet from 2-weeks prior and verified it was from the same backup image of the two files. Both files mentioned had "(Auto Saved)" in the file name and backed up a sister file with a '~' as a prefix. The fact we ran a file level restore from the same image and same directory, proved nothing was wrong with the backup. But am I correct in thinking these files are just pointer records and it's the admins' duty to exclude them from backup?
Need help on how to script an "alternate location" backup for a specific server (VM) weekly
Hello, this is my first post, I do browse the forums everyweek though. ;) Here's my problem, I do this very manual "restore" to an alternate location for a server that needs a second backup copy every single week, (with different host (VM), different display name, etc). I was wondering if it was possible to script/schedule this sort of backup to happen weekly. Right now it is very time consuming and laborous to do this every week and was wondering if any shortcuts were available. Let me know if its possible to script something like that! Thanks, etn
How to Back up Linux VMs on Hyper-V
Backing up VMs through Hyper-V is using either VSS or WMI, and neither is working for Linux VMs. So, it seems to turn out there is no way to back up Linux VMs over Hyper-V. However, on the NetBackup Hyper-V backup document, it talks about backing up Linux VMs in saved mode or non-consistant way. I don't know why it could work at all. No matter what kind option I choose when creating a policy for backing up Linux VM, it always gets snapshot Error 156 which is very normal. Why does not Veritas simply claim that it is imporssbile to back up Linux VMs over Hyper-V? Anyway, what's the best practice to back up Linux VMs on Hyper-V? Thanks in advance, Ross