01-20-2014 07:55 AM
I am a new user to SSR13 (formerly a long time user of Backup Exec). I scheduled a backup to run last night, and it didn't run. It is now saying it will run tonight. Everything seems to be in order. I can't find any error messages anywhere.
Also - can you tell me what (if anything) I need to do to ensure backups are suitable for a disaster recovery restore? It is unclear to me as to whether or not these backups are image backups that could do a full restore, or whether or not there might be issues due to open files at the time of the backupi.
01-20-2014 08:30 AM
Without reviewing the logs, it will be difficult to comment on why the scheduled backup did not run last night.
And yes, SSR does 'image' backups - it will backup everything on the volume(s) that you have selected for backup. The whole idea of SSR is to have the ability to do a full restore of a machine in the event of disaster. Product details can be found here:
http://www.symantec.com/system-recovery-server-edition
Hope that helps.
01-20-2014 09:18 AM
01-20-2014 10:54 AM
Ok, found the log. Here's the error:
Error EC8F17B7: Cannot create recovery points for job. Drive Backup of Win7 (C:\)
Error E4F3000B: PreSnap failed on volume . (UMI:V-281-3215-6071)
I found this error listed in another post and they said a reboot fixed it. I tried rebooting and rescheduling the job to run "now", and it seems to be working. I had rebooted after installing the product, but it seemed to want another reboot.
01-20-2014 12:03 PM
Ok, my backup ran for a while and failed with a different error:
Error E7D1001F: Unable to write to file.
Error EBAB03F1: Following Operating System error occured while performing requested operation: 'The requested operation could not be completed due to a file system limitation." (UMI:V-281-3215-6071).
Any ideas? There is plenty of space on the destination drive. I watched what it was doing during the backup, and it did successfully create the backup file on the destination drive, and was writing to it for a while, but after a few hours it terminated with this error.
I am coming from Acronis, and Acronis is able to back up this computer to the same destination drive with no problems. (There are other things I don't like about Acronis though, which is why I'm switching to SSR). Acronis is also much faster - this image backs up in about 45 minutes on Acronis, on SSR it was saying it would take 3 hours and died after maybe 2 hours. Speed is nice but not critical to me however - I'm going to be using SSR for nightly backups.
01-20-2014 06:03 PM
Are the backups going on a network location ? If yes , have to tried a copy paste or local backup ?
SSR backs up depending on the data getting backed up , and accordingly it takes time to backup the data , if it is a 1TB data , it will probably take 2 hours for full backup , depending on wheather it is backing up to local destination or netowork destination.
It says : "'The requested operation could not be completed due to a file system limitation."
What OS is it ?
I found Microsoft link on research : http://social.technet.microsoft.com/Forums/windowsserver/en-US/e0d55018-cf06-43ca-8e20-dd2bb8494c96/...
However , go to C:\Program Files\Symantec\SSR\Utility\ double click on partinfo.exe and it will generate a txt file.
Open partinfo.txt and check if gives any Warning messages.
Hope this Helps!!
01-20-2014 10:54 PM
01-21-2014 03:28 AM
Which volumes are you backing up?
If you are backing up C, D, E etc (for example) in the same job, can you try backing up one at a time (as a test)? This will tell us if there is an issue with one or more specific volumes.
01-21-2014 04:35 AM
01-21-2014 07:07 AM
Can you please attach logs (http://www.symantec.com/docs/TECH54539) to this thread and I will take a look for you.
01-22-2014 11:21 AM
Ok, I got it working. The destination drive had compression turned on (in Windows). When I turned it off, it worked.
I can live with this, but I still think it's a bug. Although the backup files are already compressed and compression doesn't really help, there might be other files on the drive that you do want compressed. Plus, it's an obscure error that took me two days to fix. Also - Acronis was able to back up fine to the same drive.
Now that I can do a backup, I tried to do a restore. That didn't work either. I'll open a new issue on the forum.
Thanks for your help.
01-23-2014 01:09 AM
Ok, I got it working. The destination drive had compression turned on (in Windows). When I turned it off, it worked.
I can live with this, but I still think it's a bug.
For what it's worth, I tend to agree with you. Let me test this here to see if I see same results.
01-23-2014 05:56 AM
So I could not reproduce this here. I backed up to another local NTFS volume that had compression enabled and the backup worked fine.
Is there anything else about this volume that is different? I assume it's NTFS..?
01-23-2014 05:59 AM
01-23-2014 06:01 AM
01-25-2014 08:04 AM
Chris - did you make any progress with this?
01-27-2014 07:36 AM
Not really I'm afraid. As I said before, I could not reproduce this here.
If you can easily reproduce this issue again, I would recommend that you open a support case so that this can be investigated further.
01-27-2014 08:18 AM
Ok, thanks. I did open a support ticket, but frankly those people are difficult to deal with. The ticket is open, but we are not making progress. Once I got past all the "I would be very happy to help you with this" type of talk, they basically told me that it wasn't a bug, it was a feature - that it won't back up to compressed drives by design, since the backups are already compressed and the drive couldn't compress it any further.
Now we have moved on to the "reached the end of something" issue, but I'm not too hopeful I will get any resolution on that either. What a wacky error message though!
01-27-2014 08:26 AM
Can you provide the case number for the backup issue? I will look into this for you.
Do you have a new case number for the restore issue?
01-27-2014 10:39 AM