I have had som issues with MSSQL full backups the last 4-5 weeks, it seems only be a problem on full MSSQL backups and it seems that mostly its the larger databases that fails.
If one server (or more) fails, they could work if you try again, or not,...
I need some advice about securing sharepoint 2010/2013 farms located at remote sites with pretty slow links between them and the netbackup servers.
Today we have a central sharepoint 2010 solution and the problem for some of our remote sites are...
(netbackup 126.96.36.199 master/media/client)
When moving the data from a win 2008 file server to a new win 2012 file server i get ALOT of theese messages:
"Warning bpbrm(pid=2210) from client XXX: WRN - unable to set short name on restore FILE..... - ...
When testing moving data from 1 file server (win 2008 r2) to a new fileserver (win 2012) i became litle worried about the job size and file count.
the backup: 1297956 files, filesize 1928072185
the restore of the above backup: 1290340 files, file...
I have a case at symantec about this but im wondering if anyone else has/had this problem.
We are running Netbackup Enterprise server 188.8.131.52 and the file server win2008R2.
The backups of DFSR are going ok, but i cannot restore the files to its ori...
Thanks for the replies.
I logged a case to symantec this monday and have sent tons of logs theese past days.
They also suspects network issues but the network and firewall guys have not found anything wrong eighter.
Thanks for the answer RLeon!
i will check a little bit more on "Client-Direct Restore" and see if that could be something to conssider.
Also, im a little bit interested, and have thought about the solution with a "local" media server at the site.
thanks for reply,
due to the fact that it was almost 2 milion files I moved Icannot actually verify that all has been restored, thats why i checked the filecount and size.
Yes, im using 2012 client
We are using NTFS on both servers.
I just got of the phone with symantec support and they said that its a bug in the code that will be resolved in 184.108.40.206 under ET 3136691 (im not sure what the ET means) but im pasting the tar log file in the case you want to se it anyway ;) thx for t...