Sheridan Posted June 16, 2014 Posted June 16, 2014 I've just started using BA 7.4.4 on a new Server 2012, which backs up to both a local RDX drive and an Openfiler NAS box. This is working well so far apart from one error that crops up on both backup jobs: BA712 Destination does not support copying of NTFS attributes or user does not have sufficient privileges The RDX drive is formatted as NTFS and the Openfiler NAS seems to hold NTFS permissions OK as well so I don't know why this is happening. The BA forums don't say much as they simply recommend checking the backup device is NTFS formatted (which is definitely is in the case of the RDX drive) Without NTFS permissions BA will be useless on this server as its role is going to be a data server for staff, but I'm not making it live until I can backup it up properly. Is anyone else using BA with RDX drives or NAS boxes having this problem? If its not fixable I'll have to buy another bit of software
Michael Posted June 16, 2014 Posted June 16, 2014 Presumably you've setup a share on the RDX drive and set the NTFS permissions accordingly? Whatever account you used to configure BA itself?
Sheridan Posted June 16, 2014 Author Posted June 16, 2014 BA uses a domain admin account and the RDX drive has fullt NTFS permission - everyone can write to it!
Michael Posted June 16, 2014 Posted June 16, 2014 Have you specified an IP or UNC as the backup path in BA? You could also try forcing NTFS permissions by replicating to all child objects.
Sheridan Posted June 16, 2014 Author Posted June 16, 2014 The RDX uses a local drive mapping, and the NAS path is UNC. Weirdly, I was backing the server up to the RDX for weeks with no error and as soon as I made it a DC this started to occur. I only added the NAS backup after the promotion so I'm not sure whether its just broken the installation completely or something else is going on.
Michael Posted June 16, 2014 Posted June 16, 2014 That's a possibility. You could export your settings, uninstall/re-install BA and restore your settings if needed.
Sheridan Posted June 16, 2014 Author Posted June 16, 2014 Uninstalled and reinstalled -same error to both RDX (freshly formatted at NTFS) and the NAS box. Got me baffled now. I need to preserve permissions on the backup or its no good. Theres no way I'd want to use backup exec anymore so I'll have to search for an alternative.
Michael Posted June 16, 2014 Posted June 16, 2014 Try using an earlier version of BA. I still use the latest version 6 of BA with no issues - your key should still be compatible with it!
Sheridan Posted June 16, 2014 Author Posted June 16, 2014 I'm trying that now, except the key will no longer activate as I've used it several times on the same server! Argh!
Jobos Posted June 16, 2014 Posted June 16, 2014 BA has problems copying permissions as I have found myself. I use a Buffalo NAS and have to keep the copy permissions option in BA turned off because the Buffalo is running Linux.
Sheridan Posted June 17, 2014 Author Posted June 17, 2014 Looks like BA's support is as good as Backup Execs! Log a call and they send you to a KB link, which you've already read. Why do support never read the emails and simply scan for a keyword? Time for a rethink - anyone using a GOOD backup software that can manage the basics like NTFS permissions, NAS boxes etc and is reasonably priced?
KK20 Posted July 1, 2014 Posted July 1, 2014 I had this issue way back with BA 6 it simply wouldn't preserve NTFS permissions on the openfiler box. In the end I used the openfiler box as an iSCSI target and made that available on my Hyper-V host. Formatted the resultant drive as an NTFS drive and all was hunky dory.
fiza Posted March 31, 2015 Posted March 31, 2015 Looks like BA's support is as good as Backup Execs! Log a call and they send you to a KB link, which you've already read. Why do support never read the emails and simply scan for a keyword? Time for a rethink - anyone using a GOOD backup software that can manage the basics like NTFS permissions, NAS boxes etc and is reasonably priced? Old thread I know but I wondered what you did in the end? I need to backup a file server to an ISCSI attached QNAP NAS box. I want to maintain the permissions so I can restore from it if the worst happened. I was looking at BA until I saw this thread.
KK20 Posted March 31, 2015 Posted March 31, 2015 (edited) using my openfiler with iSCSI worked fine for me. We no longer use BA though, we moved to BackupChain due to BA not allowing concurrent backup jobs (even to different targets/sources). I have had no issues with backupchain and have used it in a host and file recovery situation without issue. That being said I also used BA in a recovery (not bare metal) without issue. Edited March 31, 2015 by KK20
smithson83 Posted March 31, 2015 Posted March 31, 2015 @KK20 Do you run concurrent jobs on VM's? I would be very keep to look into this SW if you could (for example) run a back up of a set Hyper-V VMs to a NAS and HDD's simultaneously. I currently use BA, and the fact you cannot run two jobs (even different source/destinations) at the same time.
KK20 Posted March 31, 2015 Posted March 31, 2015 (edited) yes. I backup 3 guest VMs simultaneously to 2 different NAS boxes. This is the reason I went with backupchain over backup assist. You can also limit transfer speed and CPU cores to individual jobs (deduplication used up a lot of RAM and cores if you don't limit!). edit: these are clustered BC is cluster aware. It is a little awkward initially setting up the jobs as you cannot duplicated natively between hosts, you need to create the job on each host (unless you don't care and only want certain hosts to do the backing up....) it does work though, I have no issues with moving VMs between hosts and letting BC run normally. Edited March 31, 2015 by KK20 1
smithson83 Posted March 31, 2015 Posted March 31, 2015 @KK20 I may be giving this a try in the not to distant future TYVM
KK20 Posted March 31, 2015 Posted March 31, 2015 (edited) BC has a slightly different way of backing up than BA, rather than having rotating backups you choose retention and file copies. This might not be for everyone as depending on your dataset you might have very large backups. For example, you could retain 10 copies of every file and it will do that (deduplicated), however if you have a very fluid dataset then 10 copies might not be enough etc. You can also specify time retention and purging if you so wish. It all depends on what you want out of a backup, my specific needs were for disaster recovery and a low priority of accidental deletion, for me this works. speedwise, there are 12 jobs in total, there are 3 running simultaneously. The big jobs are 1.2Tb (last night started at 21:30, finished at 02.10). 773Gb started at 21:45 finished at 23:51 and 825gb started at 22:00 and finished at 01:24. The others are fairly negligible in size, ranging from 10gb to 50gb ish. Hard to calculate the speed from all this but I estimate about 100MBs which is what I would expect from the openfiler NAS boxes (circa 50MBs each, the have normal SATA drives in RAID 6). The iscsi link to the NAS is 1Gb non shared "dumb" switch. Source SAN is a dell 3200 running in HBA mode not iSCSI so there is plenty of overhead left on that. Weak link is the backup drives not the software (the software WILL eat all available RAM when backing up, I don't use dynamic RAM for my guests so I cannot say how fast it gives it back if needed by VMs) EDIT: One thing BA did do that BC doesn't is granular exchange mailbox backup. This was quite a useful add-on and if you want that then you might think about leaving BA on the mail VM to do so (or script a mailbox backup). BC is a sledgehammer "restore database to a separate area and extract the mailbox you require", harsh if you need a single mailbox restoring! Edited March 31, 2015 by KK20 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now